Campaign 10 Defense by product
19 purchases in catalog defense: how should you allocate coverage?
A catalog defense review needs a usable map: target ASIN, advertised ASIN, purpose, available results and proposed limit. That map turns a blended campaign result into decisions about specific shopping journeys. It also makes overlap easier to inspect without assuming that every overlap is waste.
In 30 seconds
Connect each target to a product, a purpose and an economic limit.
- What we see
- The catalog campaign records 19 purchases and 16.49% ACoS.
- What to check
- Map target ASINs to advertised products, goals and the cost and outcomes actually available.
- The next decision
- Propose limits for supported target–product links instead of copying the catalog average everywhere.
Observed campaign data from one advertising account. The steps below are proposals, not documented actions or measured improvements caused by Uptova.
Numbers & original evidence
- Ad spend
- €1,376.30
- Attributed ad sales
- €8,347.26
- Purchases
- 19
- ACoS
- 16.49%
View original capture
Swipe sideways to read. With a keyboard: focus the image region and use the left/right arrow keys.
Captured Enlarge original capture
The original interface is in English. The values and evidence have not been translated or recreated.
Our proposed action plan
Connect target and advertised ASIN
Use the targeting export and advertised-product report to produce a coverage map linking each target ASIN to the advertised ASIN or the verified group-level relationship. Record ownership and scope. Where reporting does not support a direct link, mark it unresolved rather than forcing a one-to-one connection.
Attach a goal and check overlap
Read the map alongside purchased-product reporting and the active campaign inventory. Produce a purpose and priority note for each verified link, distinguishing same-item presence, alternatives and cross-selling. List other coverage of the same context and explain what would remain available if one target were constrained.
Add available cost and results
Use matching target reports, product costs and stock records to produce the evidence section of the map: observed spend, sales, purchases, reporting period and margin before ads. Margin before ads is sales less the agreed product and selling costs before advertising; unavailable fields remain explicitly unavailable.
Propose a limit for each reviewed link
Combine the map, product objective and current bid settings to produce a scoped proposal with a reason, proposed allowance and review condition. Show target ASIN, advertised ASIN, goal and evidence together before approval. Keep unsupported links on the review list instead of copying 16.49% into every product’s policy.
The starting point
For September 19–25, the campaign reports €1,376.30 in spend, €8,347.26 in attributed sales and 19 purchases, giving 16.49% ACoS. This means €16.49 in ad cost per €100 in sales credited to the campaign. It describes paid outcomes, not a measured quantity of competitor sales prevented.
Catalog coverage can combine the same product promoted around its own page, alternatives within the range and complementary offers. These are roles to verify, not confirmed targeting rows in the screenshot. The capture has no target-level breakdown, so a useful map starts with the exports rather than invented product examples.
The strategic question
Read the map from left to right: which target ASIN is selected, which advertised ASIN can appear, what goal that link serves, what cost and results are available, and what limit is proposed. Missing data stays visible at its own link. A complete campaign total does not make every target outcome available.
This is more granular than simply defining a defensive campaign’s purpose. At catalog level, related products can have different costs, stock and priorities, while other campaigns may cover the same context. Overlap prompts a priority review; it does not by itself prove duplicate charges, waste or an opportunity to recover profit.
How we would judge the test
After an approved change, revisit the same target–product scope with matching attribution settings. Attribution is the report’s link between an ad interaction and a purchase. Review spend, purchases, purchased-product mix and coverage against the stated goal, alongside the product’s economic assumptions.
Add total product sales as separate context when available. If the seller wants to estimate extra demand or protection from competitors, that needs a comparison designed for the question. For routine management, the map should clearly show which limits stay, which change and which links still need evidence.
Prepare a credible before/after
For a future test: use matching windows and reporting settings, and document price, stock and listing changes.
- 01 · Preserve the baseline
- Save the verified target-ASIN to advertised-ASIN links, purposes and available cost and outcomes behind the 16.49% average.
- 02 · Document one change
- Record one approved coverage adjustment with its exact target scope, product objective, allowance and effective time.
- 03 · Measure on equal terms
- Review the same links and their observed outcomes, keeping additional-demand or competitor-protection claims separate from routine attribution.
When to act — and when to wait
Adjust the target–product links supported by the coverage map and economic inputs; leave unresolved links for review and do not treat a catalog-wide ratio as a ready-made product limit.
Before approving a change
- Target and advertised ASIN relationship verified
- Purpose and overlap recorded for each reviewed link
- Available results distinguished from missing data
- Proposed limit tied to product economics
The central lesson
The deliverable is a coverage map the seller can act on: what reaches whom, why it matters, what is known and how much to allow.
Evidence, methodology and further reading
The capture establishes no additional sales caused by defensive coverage and does not replace a product breakdown.
How to read these case studies
- The high-resolution originals were captured directly in an authenticated Amazon Ads session on October 21, 2026. Every capture shows exactly one campaign in Germany. The first ten analyses cover September 19–25; five additional cases also compare September 12–18, 2026. Both weeks contain the same weekdays.
- These campaigns are a deliberately selected sample from one advertising account, not a representative average. Data is not combined across sellers. Account names, campaign names and IDs have been removed by cropping; numbers, chart lines, scales and dates are unchanged.
- ACoS = ad spend ÷ attributed ad sales. The period ratio uses period totals, not the average of daily percentages. Attributed ad sales are neither total revenue nor profit; margins, returns, taxes and organic revenue are absent from these captures.
- The five before-and-after comparisons show observed time windows, not a controlled experiment or a documented Uptova intervention. Review ideas are recommendations, not documented interventions. Lower ACoS can accompany fewer purchases; a week establishes neither durable profitability nor incremental sales.
- The captures were retaken without the pointer after the chart animation finished, then cropped only. No chart was generatively retouched. Cost, sales and ACoS use separate scales, not a shared value scale; gaps in the ACoS line can represent days without a defined daily ratio.
- Reports can use different levels of detail and attribution windows. Queries, products and placements remain separate views unless their relationship is verified. The purchased-product report discussed in these review plans shows purchases of other products but no ad cost; it cannot supply ACoS per purchased product.