Key Takeaways
- Amazon’s Campaign Manager does not show halo revenue — sales generated when a customer clicks an ad for one ASIN and purchases a different one.
- The Sponsored Products Purchased Product Report is a free, manually pulled report that reveals this hidden revenue inside every Amazon advertising account.
- Blended ACOS — ad spend divided by direct sales plus halo sales — gives a more accurate picture of campaign efficiency than standard ACOS alone.
- Campaigns that appear to be wasting money by direct ACOS are often the most efficient acquisition drivers in an account when halo revenue is included.
- Gateway ASINs drive purchases of other products rather than converting on their own listing — pausing them removes downstream revenue that Campaign Manager never flags as a loss.
- Cross-category halo mapping reveals commercial connections between separate product lines that campaign structure cannot show, and budget cuts in one line can quietly damage sales in another.
What Is Amazon Hiding From Sellers?
Amazon’s Campaign Manager does not show all the revenue your ads generate. In a standard account audit last month, a supplement brand had $78,400 in revenue sitting in a report column most sellers never open — 58 days of real sales, real customers, real purchases driven by their advertising — completely absent from Campaign Manager. This is not a tracking error. It is not a platform glitch. It is a structural gap in how Amazon attributes revenue, and it affects bid decisions, budget decisions, and pause decisions across every account running Sponsored Products ads.
Most sellers never find this number. The report that contains it is not in the Campaign Manager dashboard. It is not in standard bulk exports. Amazon does not surface it by default, and nothing in the platform alerts you to the fact that it exists. You have to know to look for it, know where to find it, and know how to use it once you pull it.
This article covers all three. What the attribution gap is, why it exists, where the data lives, how to pull it in under 15 minutes, and how to use it to make better decisions about which campaigns to protect and which ones to scale. The revenue is already there. The report is free. What changes is whether you are working with the full number or half of it.
How Does Amazon’s Standard Attribution Model Work?
Amazon’s standard attribution model credits a sale to a campaign when a customer clicks an ad and purchases the advertised ASIN within the attribution window. The logic is clean and the data is accurate for that specific transaction: one click, one product, one sale, one credit. Campaign Manager displays this clearly and the numbers are reliable for what they measure.
The model breaks down when the customer’s behavior deviates from the assumed path. Customers on Amazon do not always behave linearly. They search, click an ad, land on a listing, scroll through the product family, notice a larger size or a related item, and buy something different from what the ad showed them. That is a completely ordinary purchase decision. It happens in physical retail constantly. On Amazon, it creates an accounting problem.
Consider a customer who searches for collagen protein powder, sees a Sponsored Products ad for a 30-serving starter pouch, clicks it, lands on that listing, sees the 90-serving bulk option in the product family section, decides they want the better value, and buys the larger size. Here is what Campaign Manager records. The campaign running on the 30-day listing shows a click, the associated spend, and zero attributed sales. The 90-day listing records a sale it did not advertise for. The 30-day campaign looks like it is burning budget with no return. The 90-day campaign looks more efficient than it actually is, because a sale landed there that it did not earn through its own advertising. The customer — who only found the brand because of that 30-day ad — is invisible in both records.
That is the gap. Amazon knows this purchase happened. The data exists. Campaign Manager simply does not show it in the default view, and most sellers never discover that it is being tracked elsewhere.
What Is a Halo Purchase and Why Does It Matter?
A halo purchase is a sale that occurs when a customer clicks an ad for one ASIN and buys a different ASIN in the same account. Amazon tracks these within a seven-day window after the ad click. The halo sale is real revenue the advertising campaign drove — the customer would not have found the brand without the ad — but the credit goes nowhere in Campaign Manager. It does not appear in ACOS calculations. It does not show up in attributed sales. It is simply absent.
This matters because the decisions sellers make about campaigns rely on ACOS as the primary efficiency signal. If ACOS is too high, a campaign gets paused or its bids get cut. If ACOS is acceptable, the campaign continues. If ACOS is strong, the campaign gets scaled. Every one of those decisions assumes that the attributed sales figure in Campaign Manager represents the full revenue impact of that campaign. For campaigns with significant halo revenue, that assumption is wrong.
In some campaigns, halo revenue exceeds direct attributed sales. A campaign running at 108% direct ACOS — which every bid management system and every analyst would flag for action — might be running at 27% blended ACOS once halo revenue is included. Pausing that campaign does not save budget. It removes $905 in revenue per reporting cycle that Campaign Manager would never flag as a loss, because it was never credited there to begin with.
The halo effect is particularly strong in accounts with product families: multiple sizes of the same product, product bundles, or complementary items that customers naturally consider together. The starter product, the mid-tier product, and the premium product form a commercial unit in the customer’s mind even when they are separate campaigns in Campaign Manager. The advertising data reflects this imperfectly. The Purchased Product Report reflects it accurately.
Where Does This Revenue Data Live in Your Account?
Amazon stores halo purchase data in a report called the Sponsored Products Purchased Product Report. Every Amazon advertising account has access to this report. It is free. It requires no additional tools, no third-party software, and no special account permissions. The only requirement is knowing where to find it.
The report is accessed through Campaign Manager under the Reports tab. The path is: Campaign Manager, then Reports, then Create Report, then Sponsored Products, then set the Report Type to Purchased Product. Set the date range — 30 to 90 days gives a reliable sample — and export the file. It downloads as a spreadsheet and is ready immediately.
The report shows each advertised ASIN, the purchased ASIN (the product the customer actually bought), and the revenue generated by that cross-ASIN purchase. It does not include spend data — spend lives in the standard advertising report. To calculate blended ACOS, both reports are needed. Pull the standard advertising report for the same date range, match campaigns by name, add the halo sales figure to the direct sales figure for each campaign, and divide spend by the combined total. The setup takes about 15 minutes the first time. After that it is a monthly pull that takes closer to five.
One important note on scope: the Purchased Product Report covers a seven-day attribution window after the ad click. The actual halo impact across a full customer lifetime is likely higher. What the report shows is a conservative, directly attributable number — not an estimate, not a model, not an inference. Every sale in that file is a real transaction linked to a real ad click.
What Is a Gateway ASIN and How Do You Identify One?
A Gateway ASIN is a product whose primary commercial function is bringing customers into the brand rather than converting on its own listing. Gateway ASINs tend to share a specific profile: high search volume, a lower price point relative to the product family, and an accessible entry-level positioning that attracts first-time buyers. Their direct ACOS looks poor because the sales they generate are credited to other ASINs. Their blended ACOS looks different.
Identifying Gateway ASINs requires the Purchased Product Report. Pull the report, aggregate halo revenue by advertised ASIN, and sort by total halo generated. ASINs that consistently appear at the top of that list — generating significant revenue for other products while their own direct attributed sales look weak — are Gateway ASINs. They are doing acquisition work, not conversion work, and standard ACOS cannot distinguish between the two.
The supplement brand example makes this concrete. The 30-serving starter pouch was the brand’s most advertised ASIN. High search volume, accessible price point, clear search intent match. In Campaign Manager, the campaigns running on it showed ACOS in the 60-80% range against a 30% target. The obvious decision, looking at those numbers alone, is to pull budget or pause entirely.
The Purchased Product Report showed $47,200 in halo revenue generated by those campaigns over 58 days. Customers clicking the starter pouch ads were upsizing. The 60-serving standard received $19,800 in halo-driven sales from those campaigns. The 90-serving bulk received $14,100. Those two ASINs picked up over $33,000 in combined sales that their own campaigns did not generate and did not pay for. The starter pouch campaigns were not failing at conversion — they were succeeding at acquisition. Standard ACOS could not show the difference.
Pausing those campaigns removes $47,200 in downstream revenue per equivalent period. The 60-serving and 90-serving campaigns keep running. Their ACOS holds steady for a while. The pipeline of new customers arriving through the starter pouch quietly stops. The impact does not appear in data for several weeks — and when the 60-serving and 90-serving performance begins to soften, the cause is no longer visible. The campaigns look fine. The problem is upstream, in a budget decision made based on an incomplete number.
How Do You Calculate Blended ACOS?
Blended ACOS adds halo revenue to the denominator in the standard ACOS formula. Standard ACOS divides ad spend by direct attributed sales only. Blended ACOS divides the same spend by the combined total of direct sales and halo sales from the Purchased Product Report.
Blended ACOS = Ad Spend divided by (Direct Sales + Halo Sales)
The mechanics are straightforward. The Purchased Product Report does not include spend data, so the two reports must be merged. Pull the standard advertising report and the Purchased Product Report for the same date range. Match campaigns by name across both files. For each campaign, add the halo sales figure to the direct sales figure. Divide spend by the combined total. That number is the blended ACOS.
Two campaign examples from the supplement account show what this changes in practice.
The first campaign was running at 108% direct ACOS. Direct attributed sales were $302. Halo sales from the same campaign were $905. Total revenue generated by the campaign: $1,207. Blended ACOS: 27%. That campaign was close to being paused. At 108% direct ACOS it looks like a budget drain. At 27% blended ACOS it is one of the most efficient campaigns in the account. Pausing it removes $905 per reporting cycle in revenue that Campaign Manager would never flag as a loss — because that revenue was never credited there to begin with.
The second campaign was running at 40% direct ACOS, which already looks reasonable. Direct sales were $1,814. Halo revenue from the same campaign was also $1,814. Total revenue generated: $3,628. Blended ACOS: 20%. Every dollar of direct revenue in that campaign is matched by an equal dollar of indirect revenue. The blended picture does not just look better — it changes the decision entirely. That is a campaign to scale, not hold.
The pattern across most accounts is that a small number of campaigns generate a disproportionate share of total halo revenue. Once blended ACOS is calculated for the full account, those campaigns become visible. They are almost always the ones that look weakest by standard ACOS. The Purchased Product Report does not change how good those campaigns are — it changes whether you can see it.
What Is Cross-Category Halo and How Do You Map It?
Cross-category halo occurs when ad clicks on one product line drive purchases in a completely separate product category. It is harder to detect than within-family halo because nothing in the campaign structure connects the two products. The Purchased Product Report is the only place that connection becomes visible.
In the supplement account, the collagen protein campaigns were generating sales of the brand’s joint support capsules. Different product line. Different campaigns with separate ACOS targets. Different search intent and different customer profile on paper. The Purchased Product Report showed $3,100 in joint support capsule revenue over 58 days, generated by customers who clicked collagen ads, browsed the brand store, and purchased the joint support product. Zero of that revenue appeared in Campaign Manager under the joint support campaigns. Zero appeared in the collagen campaigns either. It existed only in the Purchased Product Report.
Cross-category halo reveals something about how customers interact with brands on Amazon. They do not search for one product, buy it, and leave. Some do. But a meaningful segment discovers a brand through one product, browses the storefront, and makes a second decision in a different category. That second purchase is commercially connected to the first ad even when the product categories are entirely different. Campaign structure cannot show this. Blended ACOS for a single campaign cannot show this. Only the Purchased Product Report shows it.
The risk of ignoring cross-category halo is a specific kind of budget error. A brand reduces collagen spend because direct ACOS is soft. Joint support managers notice their sales declining and investigate their own campaigns — keywords, bids, listing quality. Nothing explains the drop because the cause is upstream, in a budget decision made in a different product line. The connection is invisible without the report.
To build a cross-category halo map, aggregate halo revenue by purchased ASIN across the full Purchased Product Report. Identify the destination ASINs — the products customers actually bought. Flag destination ASINs that belong to different categories from the advertised ASINs that drove them. The resulting list shows which advertised products are driving sales in other parts of the catalogue, and by how much. That map tells you which budget cuts will hurt somewhere you are not watching.
Which Campaigns Should You Protect Based on Blended ACOS?
Campaigns worth protecting share a specific profile in the blended ACOS analysis: poor direct ACOS, meaningful halo revenue, and destination ASINs that are either higher-margin products or products in separate categories. These campaigns are functioning as acquisition channels — introducing customers to the brand, not converting them on the first click — and standard ACOS cannot distinguish this from genuine inefficiency.
The decision framework works in four steps. First, pull the Purchased Product Report and the standard advertising report for the same 30-to-90-day period. Second, calculate blended ACOS for every campaign above a minimal spend threshold — campaigns with very low spend will have noisy halo data. Third, sort all campaigns by blended ACOS rather than direct ACOS. Fourth, review any campaign flagged for pause or budget reduction against its blended number before acting.
Campaigns where blended ACOS is within target but direct ACOS is well above target are Gateway ASIN campaigns. Flag them as protected. Do not pause them without understanding which ASINs are receiving their halo revenue and what that revenue is worth at the margin. Campaigns where both blended ACOS and direct ACOS are within target are scale candidates — the halo is an efficiency bonus on an already-efficient campaign. Campaigns where both numbers are above target are genuine underperformers. The Purchased Product Report does not rescue every campaign. It provides clarity on which ones are actually failing.
One structural note: campaigns that show strong halo generation tend to do so consistently, because the product’s position in the purchase journey does not change month to month. A Gateway ASIN is a Gateway ASIN because of its price point, search volume, and relationship to the rest of the product family — not because of a temporary data spike. Once identified, these campaigns can be managed with a different ACOS target that reflects their blended efficiency rather than their direct number alone.
How Often Should You Pull the Purchased Product Report?
Monthly is the right cadence for most accounts. The report captures a rolling seven-day attribution window per click, so a 30-day pull gives a complete picture of the month’s halo activity. Pulling it more frequently creates noise — individual halo events can be large enough to skew a short window. Pulling it less frequently means making budget decisions for weeks based on incomplete data.
The first pull will likely surface the largest surprises. Accounts that have never reviewed this data often find that their highest-volume campaigns — the ones running longest and spending the most — have accumulated halo revenue that has never been factored into any decision. That first reconciliation sometimes changes the strategic priority of the entire account.
After the first pull, the process is faster. The Purchased Product Report structure does not change. The column headers are the same every time. The join to the standard advertising report uses the same matching logic. Once set up, the monthly pull is a matter of replacing the date range, re-exporting both files, and refreshing the merged dataset. Fifteen minutes the first time. Five minutes every month after that.
For accounts running $50,000 or more per month in ad spend, the monthly pull is not optional. At that scale, the difference between standard ACOS and blended ACOS across even a small number of Gateway ASIN campaigns can represent tens of thousands of dollars per month in misattributed revenue. The decisions being made without this data are not small ones.
What Does This Mean for Your Amazon Advertising Strategy?
Standard ACOS is not wrong. It is an accurate measure of a specific, narrow thing: the revenue directly attributed to the advertised ASIN from a given campaign. The problem is using it as a complete measure of campaign efficiency when it is not designed to be one. For campaigns with significant halo revenue, relying on standard ACOS alone means using a partial number as if it were a full one. The resulting decisions reflect that partiality.
The Purchased Product Report changes the question from “is this campaign efficient at converting on its own ASIN?” to “is this campaign generating a positive return on spend when all the revenue it drives is included?” The second question is the one that matters for budget allocation. The first is useful for listing-level conversion analysis — a different problem with different data.
The broader implication is that product families need to be analyzed as commercial units, not as isolated campaign structures. The starter product, the mid-tier product, and the premium product are not independent revenue generators in the customer’s decision process. They are stages in a consideration journey that advertising can influence at any point. Campaign Manager shows the advertising layer of that journey. The Purchased Product Report shows the commercial layer underneath it. Both are needed to understand what is actually happening in an account.
The $78,400 in that last column was not a surprise to the customer who spent it. They found the brand, they browsed, they made a decision they felt good about, and they checked out. Amazon tracked every step. The only system that did not know about it was the one being used to decide where to put the budget next month. That is what changes when you pull this report.
