About this video
Amazon DSP Ads Mobile Line Item - Step by Step 2025 - In this comprehensive guide, I'll walk you through creating a mobile-specific line item in Amazon DSP to maximize your advertising effectiveness on mobile devices.
Creating separate line items for mobile and desktop is essential for proper campaign management and performance analysis. This targeted approach allows you to see exactly how your ads perform across different devices and make data-driven optimizations.
## Mobile Line Item Setup Process
When creating a mobile line item in Amazon DSP, start by naming your line item appropriately - include "mobile" in the name to easily identify it. This is crucial for organization when you have multiple line items running simultaneously.
The most important step is in the device section - you must turn off the desktop option and select only mobile devices. You can even get more specific by creating separate line items for Android and iOS native apps if needed.
For inventory selection, choose "individual providers" if you want your ads to appear only on Amazon properties. Deselect options like IMDB, Twitch, or third-party exchanges if you're focusing solely on Amazon retail marketing. This ensures your budget is spent exactly where you want it.
## Advanced Audience Targeting
One powerful feature in Amazon DSP is the ability to both include and exclude specific audiences. For example, you can target users who viewed competitor products but exclude those who already purchased them. This precision targeting is accomplished by:
1. Adding your target audience (e.g., competitor product views) 2. Setting up an exclusion for purchasers 3. Using the "AND" operator to ensure proper audience filtering
This level of targeting precision helps you reach potential customers at the right stage of their buying journey.
## Budget and Delivery Settings
For budget allocation, consider splitting your order budget among different line items. Setting an even pacing delivery ensures your ads show consistently throughout the campaign period.
If you're promoting a limited-time deal, you might prefer "Pace Ahead" or "ASAP" options to maximize visibility during that window. For frequency capping, limiting ad exposure to around 5 times per day per user is often effective.
## Bidding Strategy
Using custom bidding with "Prioritized KPI Target" gives you more control over your campaign performance. Set your base bid (example: $5) and maximum CPM increase (up to 10) based on your campaign goals and budget constraints.
## Why Separate Mobile and Desktop?
Creating separate line items for mobile and desktop provides clear performance visibility. Mobile typically generates higher impression volumes due to traffic patterns, and having distinct line items lets you easily compare metrics like: - CPM differences between devices - Return on ad spend by device - Conversion rates across platforms
This data helps you make informed decisions about budget allocation and optimization strategies.
As an FBA seller, leveraging Amazon's demand side platform gives you access to premium ad placements both on and off Amazon. Working with an Amazon advertising agency can help FBA sellers navigate the complexities of Amazon DSP advertising while focusing on their core business operations.
## Timestamps: 00:00:00 - Introduction to creating mobile line items in DSP 00:00:33 - Naming your line item and selecting mobile-only 00:01:27 - Inventory selection process 00:03:47 - Audience targeting setup 00:05:40 - Excluding purchasers from your audience 00:06:53 - Setting delivery schedule and budget 00:07:49 - Bidding strategy configuration 00:08:53 - Benefits of separating mobile and desktop line items
For personalized assistance with your Amazon Advertising strategy, visit https://amazoniappc.com ------------------------------------------------------ Some product links are affiliate links, which means that if you make a purchase, we'll receive a small commission.
š” If you need a *Helium 10* tool, which we strongly recommend as the industry standard, you can use this link to signup and get 20% OFF for 6 months: https://i.helium10.com/K05Qo9
š” Use the *Amazon Reimbursements* program to return your money from Amazon for damaged and lost inventory. Any new seller that uses this referral link will get **$400 in free FBA reimbursements.** No promo code is necessary! Use this Getida Link: https://get.getida.com/i3t3sn8cj5x2
š” If you're still not using *PickFu* you should definitely start! For a 50% OFF on your first PICKFU poll use the coupon AMAZONIA or visit this link: https://www.pickfu.com/#_r_amazonia
š” Get *2 months* of Free Trial for *SellerBoard* using this link: https://sellerboard.com/?p=01820
Free offer
Get a Free Account Audit
Let our Amazon PPC experts review your account and show you exactly where you're leaving money on the table ā no strings attached.
Transcript
Frequently asked questions
What are the key differences when setting up a mobile line item in DSP compared to a desktop line item?
The primary structural difference is in the device selection: for a mobile line item, you must deselect desktop and select mobile only. If you leave desktop selected when creating a mobile line item, the device separation that gives you clean per-device performance data is lost. The rest of the setup process follows the same steps as desktop, including inventory selection, audience targeting, budget, pacing, and bidding. The practical outcome of having a dedicated mobile line item is that you can see metrics like CPM, ROAS, and conversion rate separately for mobile, which is particularly useful given that mobile typically generates a higher volume of impressions and often differs meaningfully in conversion rate compared to desktop.
How do you combine audience inclusion and exclusion logic within a DSP line item?
When adding audiences in the targeting section of a line item, you first add your target audience and set it to Include. You then add a second audience group and set it to Exclude. The operator between the two groups must be set to AND rather than OR. The AND operator means: reach people who are in the included audience AND are not in the excluded audience. The OR operator would mean: reach people who are in either audience, which would defeat the purpose of the exclusion. In the example from the video, the setup is: include competitor product views audience AND exclude competitor product purchases audience. This reaches shoppers who browsed a competitor's product but did not buy, which is the highest-value segment for a conquesting remarketing campaign.
Is it worth creating further sub-divided line items for Android versus iOS, or is a single mobile line item sufficient?
A single mobile line item that includes all mobile traffic is a perfectly reasonable starting point. Once that line item has accumulated enough data to show meaningful performance differences between operating systems or between mobile web and native app environments, creating further subdivisions becomes justified. For example, if iOS native app traffic consistently shows a higher conversion rate or lower CPM than Android mobile web, isolating each into its own line item gives you the ability to bid differently for each and allocate budget more precisely. For most campaigns at launch, starting with one mobile line item and one desktop line item is sufficient to get device-level insights without over-complicating the account structure before any data exists to guide further segmentation.
What does the practical outcome of separate mobile and desktop line items look like in reporting?
When you view an order that contains both a desktop and a mobile line item, you see each line item as a row with its own metrics. Mobile will typically show a significantly higher impression count than desktop, reflecting the traffic distribution of Amazon shoppers. You can then compare CPM, click-through rate, ROAS, and conversion rate between the two rows directly. If mobile is generating more impressions but converting at a lower rate, you can reduce the mobile budget or adjust the CPM cap downward while increasing desktop allocation without affecting the other line item. This side-by-side view is not available when both device types are blended into a single line item, where blended metrics obscure which device is driving results and which is consuming budget without a proportional return.
