Creating a Sponsored Products Product Target campaign via bulk sheet

The campaign type that puts your ad on competitor pages

Keyword campaigns target what shoppers search. Product Target campaigns target what shoppers look at. Specifically, your ad shows up on the product detail pages of other ASINs you choose — usually competitors selling similar products — or across whole category pages on Amazon. It's the campaign type sellers reach for when they want their product visible to shoppers who are already considering an alternative, or when they want broad category-level exposure without specifying individual ASINs.

This article walks through building one via bulk sheet. The structure is similar to a Keyword campaign — Campaign, Ad Group, Product Ad, then targeting rows — but the targeting rows use a different syntax (the Product Targeting Expression column) and have very different strategic considerations. If you haven't read the anatomy article yet, start there. The template generator on this page is pre-set to SP — Product Target campaign; download it alongside reading.

When to use Product Target campaigns

Three primary scenarios:

• Conquesting specific competitors. You sell a 12-quart air fryer; you know the three best-selling competing 12-quart air fryers on Amazon and their ASINs. A Product Target campaign places your ad directly on each of those competitor product pages. Shoppers viewing them see your option alongside.
• Category-level discovery. Targeting Amazon's category pages (e.g., "Air Fryers" or "Small Kitchen Appliances") gives you exposure across the whole category. Useful when you don't know which specific ASINs convert but you know your category is right. Often paired with refinements (brand exclusions, price ranges) to narrow the targeting.
• Harvesting product placements from Auto campaigns. Your Auto campaign's "substitutes" and "complements" groups have been driving impressions on specific competitor ASINs. The Targeting Report shows you which ASINs converted. Move those into a Product Target campaign at exact ASIN targets, bid more aggressively, and you've turned auto-discovered placements into managed targeting — similar to the Auto-to-Keyword harvest pattern, but for product placements.

Product Target campaigns are less effective for branded defense (you can't target your own ASINs to defend your product page from competitors — Amazon blocks that pattern). For brand defense, use Sponsored Brands campaigns instead.

The five rows you'll create

A minimal Product Target campaign with one SKU and two targets:

1. Campaign row — the campaign itself.
2. Ad Group row — one ad group inside the campaign.
3. Product Ad row — links the SKU to the ad group.
4. Product Targeting row (ASIN) — the first target, an ASIN.
5. Product Targeting row (category) — the second target, a category.

You can mix ASIN and category targeting in the same ad group (as shown), or split them into separate ad groups for cleaner bid management. Most real campaigns have 5–50 ASIN targets or 1–5 category targets — duplicate the targeting row pattern for each.

Rows 1–3: the Campaign / Ad Group / Product Ad rows

These three rows are nearly identical to a Keyword campaign — Targeting Type is MANUAL (Product Target campaigns are a flavor of Manual targeting, just with product expressions instead of keywords). The Campaign row requires Campaign ID, Campaign Name, Start Date, State, Daily Budget, and Bidding Strategy. The Ad Group row requires Campaign ID, Ad Group ID, Ad Group Name, State, and Ad Group Default Bid. The Product Ad row requires Campaign ID, Ad Group ID, SKU, and State.

For all three rows, Operation is Create, and Targeting Type on the Campaign row is MANUAL. See the Keyword campaign article for the full row-by-row cell-level walkthrough — the structure is identical for the first three rows.

Row 4+: the Product Targeting rows

This is where Product Target campaigns diverge. The single most important cell is Product Targeting Expression, which uses a small custom syntax to describe what you want to target.

Each Product Targeting row needs:

• Campaign ID — match the Campaign row.
• Ad Group ID — match the Ad Group row.
• State — enabled or paused.
• Bid — optional. If blank, falls back to Ad Group Default Bid. Most campaigns specify per-target bids because different targets warrant different bids.
• Product Targeting Expression — the actual targeting syntax. See below.

Pre-filled: Product, Entity (Product Targeting), Operation (Create). Product Targeting ID is optional — Amazon generates one if you leave it blank.

The two main expression syntaxes

ASIN targeting places your ad on a specific product page. The syntax is exactly:

asin="B0XXXXXXXX"

Where B0XXXXXXXX is the 10-character Amazon Standard Identification Number of the product you want to target. Both the lowercase asin= prefix and the double quotes around the ASIN are required. Capitalization on the prefix matters: asin= works, ASIN= does not.

You can find ASINs in the URL of any Amazon product page (the segment after /dp/) or in your own Customer Search Term report (the rows for product-page placements).

Category targeting places your ad across an entire Amazon category. The syntax is:

category="123456"

Where 123456 is Amazon's numeric category ID. The challenge with category targeting is that Amazon doesn't publish a simple lookup for category IDs — the IDs are visible to Amazon's algorithm but obscured from sellers. Two practical ways to find them:

• Build a category target in the Seller Central UI first, then download the bulk sheet. The downloaded sheet shows the category ID in the expression. From then on, you can reuse it in bulk uploads.
• Use the Suggested Targets section of the Seller Central UI when creating a Product Target ad group. Amazon shows you category options with their internal IDs visible if you inspect the form data or use a browser extension.

Category targeting can also be refined with additional clauses. Some common patterns:

category="123456" brand="MyBrand"

Target the category, but only on products from a specific brand. Useful for narrowing to known competitor brands within a category.

category="123456" price-less-than="25.00"

Target the category, but only on products priced under $25. Useful for hitting budget shoppers.

category="123456" rating-greater-than-or-equal-to="4"

Target the category, but only on products rated 4 stars or better. Useful for piggybacking on quality competitors.

Refinements can be combined: category="123456" brand="MyBrand" price-less-than="50.00". Each refinement narrows the targeting further.

Download a template and fill it in

Use the template generator on this page — it's pre-set to SP — Product Target campaign. The template includes two example Product Targeting rows so you can see both ASIN and category syntax side by side. Replace each example expression with your actual targets, or duplicate the rows for more targets.

How to think about bids on Product Target campaigns

Product page placements behave differently from keyword search placements:

• Lower click-through rate. Shoppers on a product page are further along in the decision process; they click less often than from a fresh search results page. Expect CTRs in the 0.1–0.3% range for product page targets vs. 0.4–0.8% for keyword targets.
• Higher conversion rate per click. The clicks you do get tend to be high-intent — the shopper is comparison shopping rather than browsing. CVR can be 12–18% for well-matched ASIN targets vs. 8–12% for keyword traffic.
• Lower CPCs typically. Less competition on most ASIN pages than on hot search keywords. Bids of $0.40–$0.90 often win impressions on product pages where similar keyword targets would need $1.20+.

A typical starting bid strategy:

• ASIN targeting (specific competitors): bid 70–90% of your Auto campaign's substitutes-group CPC if you have that data. Otherwise, start in the $0.50–$0.80 range and adjust based on impressions.
• Category targeting: bid lower than ASIN targeting (broader audience, more variable). Often 50–70% of the ASIN target bid for the same campaign.
• Refined category targeting (with brand/price filters): can sometimes warrant a higher bid than unrefined category targeting because the audience is more qualified.

Common mistakes specific to Product Target campaigns

• Expression syntax typos. The most common upload error. asin=B0XXXXXXXX (no quotes) fails. ASIN="B0XXXXXXXX" (capitalized prefix) fails. asin="b0xxxxxxxx" (lowercase ASIN) usually fails. Copy-paste ASINs rather than retyping; they're case-sensitive and one character off means a different product.
• Targeting your own ASINs. Amazon silently blocks ads targeting your own products. The row uploads "successfully" but no impressions ever come. If a campaign goes weeks with zero impressions on one row, check if the target ASIN belongs to your account.
• Wrong category ID. Made-up or mistyped category IDs fail validation. Always derive them from a real Amazon category — never invent them. Same for brand= and price-less-than= values: brand names must match real brand strings; price values must be numeric.
• Mixing too many target types in one ad group. If you put 30 ASIN targets and 5 category targets in the same ad group, you can't tell from the report which type is driving performance. Separate them by ad group (or by campaign) for cleaner attribution.
• Forgetting that ASIN performance is volatile. A high-performing ASIN target can stop converting overnight if the competitor changes their product page, raises their price, or goes out of stock. Audit ASIN targets monthly and pause non-performers.

What happens after upload

Standard upload flow: Amazon validates, campaign appears in Seller Central within 5–30 minutes, spending starts immediately if enabled. Product Target campaigns are slower to reach steady-state than Keyword campaigns because product page impressions accumulate more slowly than search impressions — give it 14–21 days before drawing performance conclusions.

The data you'll want after two to three weeks:

• Per-target performance. Which ASINs converted at acceptable ACoS? Which spent money with no orders? Pause non-converters and re-evaluate after another period.
• ASIN vs category split. Often one outperforms the other dramatically. Whichever is winning, allocate more budget there in the next iteration.
• Targeting report for category targets. Category targets show you which specific ASINs your ad appeared on. Those individual ASINs are harvest candidates — promote the converters to explicit ASIN targets and pause the non-converters.

The harvest cycle for Product Target campaigns

The natural workflow is similar to the Auto-to-Keyword harvest, but with a product-targeting lens:

1. Start with a broad category target (or a few competitor ASINs you know).
2. After 2–3 weeks, check the Targeting Report to see which specific ASINs (under category targets) actually drove conversions.
3. Promote those converters to explicit ASIN targets at higher bids.
4. Pause or lower bids on non-converting ASINs.
5. Continue refining over multiple cycles.

Over six months of this cycle, a Product Target campaign converges on a set of 10–30 known-converting ASIN targets with bids tuned per target. That's the mature state — predictable performance, low ACoS, steady volume.

Next steps

Once you have a Product Target campaign running:

• Bid adjustments based on per-target performance — covered in the Bulk Bid Adjustments article.
• Negative product targets to exclude specific ASINs (the negative-keyword equivalent for product targeting). Useful when a category target keeps showing on a non-converting ASIN you want to exclude.
• Sponsored Display as a complement — SD has its own audience-based and category-based targeting that overlaps with SP Product Target. Covered in the SD article.

And the bigger picture: now that you've seen SP Auto, SP Keyword, and SP Product Target campaign creation, you have the three core building blocks. A typical full account has all three for every priority SKU, plus negatives, plus placement adjustments — easily 20–50 campaigns. That's where BulkSheet Pro takes over: feed it a SKU list, get all three campaign types built and validated in one upload, with optimization recommendations layered on top. Try it free →