Amazon Halo Sales vs. Promoted Sales: Which Revenue Is Your PPC Actually Driving?

Meta Title: Amazon Halo Sales vs. Promoted Sales: What Your PPC Is Really Driving | Adorbix

Meta Description: Learn the difference between Amazon halo sales and promoted sales, how Unified Reporting changes PPC analysis, and which revenue your ads are actually driving.

Primary Keyword: Amazon Halo Sales vs Promoted Sales

Secondary Keywords: Amazon halo sales, Amazon promoted sales, Amazon PPC attribution, Amazon Unified Reporting, Amazon PPC sales, Amazon advertising attribution, Amazon ROAS, Amazon ACoS, Amazon Ads reporting 2026

Amazon Halo Sales vs. Promoted Sales: Which Revenue Is Your PPC Actually Driving?

‍

Your Amazon campaign reports $10,000 in attributed sales.

Sounds straightforward.

But what exactly did the customer buy?

Did your ad generate $10,000 in sales of the ASIN you actually advertised?

Or did someone click that ad, browse your catalog, and purchase a different qualifying product?

Those two outcomes can now be examined more clearly through Amazon Ads' updated reporting terminology:

‍

Promoted Sales

Revenue attributed to purchases of the product directly promoted by the ad.

‍

Halo Sales

Revenue attributed to qualifying products other than the directly promoted product, according to the applicable campaign's halo rules.

Amazon's 2026 Unified Reporting standardizes older terms such as “Other SKU” and “Brand Halo” under the “Halo” qualifier, while base conversion metrics can include both promoted and halo activity.

For sellers and advertisers, this creates a critical question:

‍

Is your PPC campaign selling the product you're advertising—or is it influencing broader catalog sales?

Neither result is automatically better.

But if you don't know the difference, you can easily misread your ACoS, ROAS, product performance, and budget allocation.

‍

What Are Amazon Promoted Sales?

‍

Promoted sales are the most direct form of ad-attributed revenue.

For Amazon seller reporting, Sales (promoted) represents attributed revenue where the purchased SKU is the same SKU that was advertised. Amazon's updated reporting documentation notes that this metric was previously known as 7 Day Advertised SKU Sales for sellers.

Imagine you advertise:

ASIN A — 32 oz Insulated Bottle

A customer clicks the Sponsored Products ad.

They purchase:

ASIN A — 32 oz Insulated Bottle

That revenue belongs in:

Sales (promoted)

This is the cleanest answer to:

“Did this ad sell the exact product we paid to advertise?”

‍

What Are Amazon Halo Sales?

‍

Now imagine the same customer clicks your ad for:

ASIN A — 32 oz Insulated Bottle

but after reaching Amazon, purchases:

ASIN B — 20 oz Bottle

or another product that qualifies under that campaign's halo rules.

That revenue may be reported as:

Sales (halo)

For seller reporting, Amazon defines Sales (halo), formerly 7 Day Other SKU Sales, as attributed product sales where the purchased SKU differs from the advertised SKU.

In Unified Reporting, Amazon describes halo products more broadly as highly relevant non-promoted products defined by the individual campaign's expansion rules.

That's important because:

Halo revenue is still ad-influenced revenue.

But it isn't necessarily revenue from the product your campaign was directly designed to sell.

‍

Promoted Sales vs. Halo Sales: Simple Example

‍

Suppose your Amazon campaign spends:

$2,000

It generates:

Promoted Sales: $7,000
Halo Sales: $3,000

Total attributed sales:

$10,000

Your campaign appears to produce:

ROAS = $10,000 ÷ $2,000 = 5.0

and:

ACoS = $2,000 ÷ $10,000 = 20%

Looks excellent.

But now isolate the directly advertised product:

Promoted-only ROAS = $7,000 ÷ $2,000 = 3.5

Promoted-only advertising cost ratio ≈ 28.6%

That's a very different picture.

The campaign isn't necessarily bad.

It simply means 30% of its attributed revenue came from other qualifying products rather than the directly advertised product.

That distinction can completely change how you evaluate the campaign.

‍

Why Amazon's 2026 Unified Reporting Makes This More Important

‍

Amazon made Unified Reporting generally available in June 2026, consolidating reporting across multiple Amazon Ads products, accounts, countries, dimensions, and metrics. (Amazon Ads)

One major goal is standardized terminology.

Previously you might encounter labels such as:

• Advertised SKU sales
• Other SKU sales
• Brand Halo
• Total sales
• Total purchases

Unified Reporting increasingly standardizes these around:

‍

Promoted

and

Halo

Amazon also warns advertisers—particularly Amazon DSP users—that some base metrics now have broader definitions than their legacy equivalents. For promoted-only analysis, advertisers should deliberately choose metrics containing the promoted qualifier.

That's why this isn't simply a terminology update.

It changes how you should read the numbers.

‍

Base “Sales” and “Purchases” Can Include More Than the Promoted Product

‍

This is one of the easiest places to make a reporting mistake.

Amazon's Unified Reporting framework uses base conversion metrics for the broader result.

For example:

Purchases

can include attributed purchases across both promoted and qualifying halo products.

Whereas:

Purchases (promoted)

isolates purchases of directly promoted products.

And:

Purchases (halo)

isolates qualifying non-promoted-product purchases.

The same logic applies across other standardized conversion metrics.

If your dashboard only pulls the base number, you may be analyzing broader advertising impact without realizing it.

‍

Why Halo Sales Are Not “Fake Sales”

‍

This is another common mistake.

Some advertisers see halo revenue and think:

“That doesn't count. We weren't advertising that SKU.”

That's too simplistic.

Consider a shopper who sees an ad for your flagship product.

They enter your brand ecosystem.

Then they discover that another product fits their needs better.

The ad still influenced the sale.

Halo reporting helps show that broader impact.

Amazon Attribution similarly uses brand-halo measurement to show advertising impact on products beyond the directly promoted product. (Amazon Ads)

The better question is:

Was that halo sale commercially valuable enough to justify the advertising spend?

‍

When Halo Sales Are a Positive Signal

‍

Halo revenue can be especially valuable when you have a broad catalog.

For example:

1. Your products naturally cross-sell

You advertise shampoo.

The shopper purchases the matching conditioner.

That's potentially useful halo activity.

‍

2. Customers enter through flagship products

Your most popular product may function as a traffic gateway into the rest of the brand.

‍

3. Higher-margin ASINs receive halo conversions

You pay to advertise Product A but generate profitable sales on Product B.

That can improve overall campaign economics.

‍

4. New shoppers discover the broader catalog

Halo sales can indicate that advertising is doing more than closing one ASIN-level transaction.

For brand-growth campaigns, this can be strategically valuable.

‍

When Too Much Halo Revenue Can Be a Warning Sign

High halo revenue isn't always positive.

Imagine you're advertising an ASIN because you need to:

• Launch it
• Move inventory
• Improve its sales velocity
• Validate demand
• Build customer traction

But most campaign revenue comes from other products.

The account-level sales may look strong.

The advertised ASIN may still be struggling.

Warning signs include:

High total attributed sales

but

Low promoted sales

and

Poor advertised-ASIN conversion

This can make a weak ASIN appear healthier than it actually is.

‍

The Halo Dependency Problem

Consider two campaigns.

‍

Campaign A

Promoted Sales: $9,000
Halo Sales: $1,000

Halo share:

10%

Campaign B

Promoted Sales: $3,000
Halo Sales: $7,000

Halo share:

70%

Both report:

$10,000 total attributed sales.

But they are doing completely different jobs.

Campaign A

Primarily sells the product being advertised.

Campaign B

Primarily acts as a gateway into other qualifying products.

Neither is automatically wrong.

But you should never evaluate them identically.

‍

A New Metric Sellers Should Track: Halo Sales Share

‍

Amazon provides the underlying reporting fields, and sellers can turn them into an additional management metric:

Halo Sales Share = Halo Sales ÷ Total Attributed Sales × 100

For example:

Halo Sales = $3,000

Total Sales = $10,000

Halo Sales Share:

30%

This can help answer:

How dependent is this campaign's reported performance on sales of products other than the promoted ASIN?

This isn't an official Amazon KPI; it's a useful internal analysis metric.

‍

Also Track Promoted Sales Share

‍

The inverse is equally valuable:

Promoted Sales Share = Promoted Sales ÷ Total Attributed Sales × 100

If:

Promoted Sales = $7,000

Total Sales = $10,000

Promoted Sales Share:

70%

Together, the two metrics provide a simple revenue mix:

70% Promoted

30% Halo

That is much more informative than saying:

“Campaign generated $10,000.”

‍

Why This Matters for Product Launches

‍

Suppose you're launching a new ASIN.

You run aggressive PPC.

Amazon reports strong attributed sales.

But after separating the numbers:

Total Sales: $20,000

Promoted Sales: $5,000

Halo Sales: $15,000

Your campaign may be excellent at generating brand-level demand.

But your new ASIN itself may not yet be converting strongly.

That's critical information.

Without promoted-vs-halo analysis, you might:

• Increase inventory too aggressively
• Increase bids
• Scale the wrong keyword
• Assume product-market fit has been validated

Total campaign success and ASIN success are not always the same thing.

‍

Why This Matters for Low-Margin Products

‍

Imagine Product A has:

10% contribution margin

but Product B—the product generating most halo sales—has:

35% contribution margin.

A campaign that looks mediocre at the advertised-product level might actually create excellent brand-level economics.

Now reverse the situation:

Product A:

35% margin

Halo Product B:

8% margin

Suddenly those halo sales may be much less attractive.

Revenue source matters.

Profit source matters even more.

‍

Connect Halo Sales to ASIN-Level Profitability

‍

At Adorbix, we'd take the analysis beyond:

Promoted Sales vs. Halo Sales

and ask:

What profit did each revenue type generate?

For example:

Revenue TypeSalesContribution MarginEstimated ContributionPromoted$7,00030%$2,100Halo$3,00010%$300

Total attributed sales:

$10,000

But contribution before advertising:

$2,400

Ad spend:

$2,000

Approximate remaining contribution:

$400

That is a very different story from simply celebrating 5.0 ROAS.

‍

Halo Sales Can Reveal Cross-Selling Opportunities

‍

Halo reporting isn't just something to audit.

It can be a discovery tool.

Suppose customers repeatedly:

Click Product A → Buy Product B

That relationship may suggest:

• Better product targeting
• Sponsored Brands opportunities
• Brand Store cross-selling
• A+ comparison tables
• Bundles where permitted
• Product-navigation improvements
• Additional campaigns for Product B

Halo sales can show you how shoppers move through your catalog.

That can be extremely valuable customer-behavior data.

‍

Use the Purchased Product Report

‍

Amazon advertising reports can also help identify which products shoppers actually purchased after interacting with advertising.

For certain Sponsored Display reporting, for example, Amazon provides Purchased Product reports containing the advertised ASIN and purchased ASIN, along with brand-halo order and sales metrics.

This helps answer:

Which products are receiving the halo benefit?

Don't stop at:

“We have $4,000 in halo sales.”

Ask:

Which ASINs produced those $4,000?

That's where strategy begins.

‍

8 Questions to Ask About Halo Revenue

When reviewing a campaign, ask:

1. What percentage of attributed sales is promoted vs. halo?
2. Which ASINs generate the halo revenue?
3. Are those ASINs profitable?
4. Are halo products strategically important?
5. Would those sales likely occur without advertising?
6. Is the promoted ASIN itself converting well?
7. Can the cross-selling relationship be deliberately expanded?
8. Does halo activity justify the campaign's total advertising cost?

These questions tell you much more than total ROAS alone.

‍

Promoted Sales Matter More When the Campaign Has a Specific ASIN Goal

If your objective is:

Product launch

prioritize promoted-product performance.

If your objective is:

‍

Clear excess inventory

promoted sales matter heavily.

If your objective is:

‍

Validate a new variation

promoted conversion matters.

If your objective is:

‍

Rank and scale a specific ASIN

again, promoted-product data is essential.

Don't let successful halo sales hide failure against the actual campaign objective.

Halo Sales Matter More When the Goal Is Brand Growth

Now imagine the objective is:

Acquire new customers

Build brand awareness

Increase basket expansion

Cross-sell a portfolio

Drive shoppers into the Brand Store

In these cases, halo activity can be extremely valuable.

Amazon's broader measurement tools specifically include halo and new-to-brand metrics to help advertisers understand advertising influence beyond only the directly promoted item. (Amazon Ads)

The correct metric depends on the objective.

‍

Promoted vs. Halo Sales by Campaign Objective

Campaign ObjectiveMetric to Watch More CloselyNew ASIN launchPromoted SalesInventory clearancePromoted SalesKeyword validationPromoted SalesBrand awarenessTotal + Halo SalesCross-sellingHalo SalesCatalog growthHalo + PromotedProfitabilityContribution from bothBrand acquisitionNew-to-brand + Total Sales

This is why there shouldn't be one universal reporting framework for every campaign.

‍

Don't Confuse Halo Sales With Organic Sales

This distinction is critical.

Organic Sale

A purchase that isn't attributed to an advertising interaction under the applicable ad-attribution methodology.

Halo Sale

A sale of a qualifying non-promoted product that Amazon attributes to an ad interaction.

Halo sales are advertising-attributed sales.

They aren't the same thing as organic sales.

If you're analyzing:

• TACoS
• Organic revenue
• Paid dependency
• Incrementality

keep that distinction clear.

‍

Halo Sales and TACoS Are Different Questions

TACoS asks:

How much advertising spend are we using relative to total Amazon sales?

Halo reporting asks:

Which products are generating the ad-attributed revenue?

Both are useful.

But they solve different problems.

For example:

You could have:

Low TACoS

and

High halo dependence

if your total organic sales are strong.

Or:

High TACoS

and

Low halo sales

if one promoted product depends heavily on PPC.

Don't collapse all Amazon metrics into one number.

The Adorbix Promoted vs. Halo Audit Framework

At Adorbix, we'd evaluate PPC attribution in five layers.

‍

01 — TOTAL IMPACT

Start with:

• Spend
• Total sales
• Purchases
• ROAS
• ACoS

‍

02 — PROMOTED IMPACT

Separate:

• Sales (promoted)
• Purchases (promoted)
• Units sold (promoted)
• Promoted ROAS where available

‍

03 — HALO IMPACT

Analyze:

• Sales (halo)
• Purchases (halo)
• Units sold (halo)
• Purchased ASINs

‍

04 — PROFITABILITY

Connect both revenue streams with:

• COGS
• FBA costs
• Amazon fees
• Contribution margin
• Returns

‍

05 — STRATEGY

Decide whether to:

Scale

Defend

Cross-sell

Restructure

Reduce

or

Stop

Revenue tells us what happened.

The revenue mix tells us why.

‍

How Adorbix Can Use Halo Data to Improve PPC

‍

1. Identify Hidden Winners

A low-advertised ASIN may generate substantial halo revenue.

That product may deserve its own campaign.

‍

2. Identify Gateway Products

Some products are excellent ad-entry points even when shoppers ultimately buy different products.

Those ASINs may have strategic value beyond their own ROAS.

‍

3. Improve Product Targeting

If shoppers consistently move from one ASIN to another, those relationships can inform product-targeting strategy.

‍

4. Improve A+ Content

Use comparison modules to make relevant catalog choices easier.

‍

5. Improve Brand Store Navigation

If halo behavior reveals predictable shopping paths, your Brand Store can reflect those paths.

‍

6. Reallocate PPC Budget

Campaigns producing weak promoted and weak halo sales deserve different treatment from campaigns producing modest promoted sales but highly profitable halo revenue.

‍

A 30-Day Halo Sales Audit

Week 1 — Measure

Pull:

• Total Sales
• Sales (promoted)
• Sales (halo)
• Purchases
• Purchases (promoted)
• Purchases (halo)
• Spend
• ROAS

Amazon's Unified Reporting explicitly supports promoted and halo qualified conversion metrics.

‍

Week 2 — Map

Identify:

Advertised ASIN → Purchased ASIN

Look for repeated relationships.

‍

Week 3 — Calculate Profit

Add:

• Product margin
• FBA
• Fees
• Returns
• Advertising cost

Determine whether halo revenue is profitable halo revenue.

‍

Week 4 — Optimize

Decide which relationships deserve:

• New campaigns
• Cross-selling
• A+ comparisons
• Product targeting
• More budget
• Less budget

‍

7 Reporting Mistakes to Avoid

‍

1. Treating Sales and Sales (promoted) as identical

They can represent different scopes.

‍

2. Assuming all halo sales are bad

Halo can represent valuable catalog expansion.

‍

3. Assuming all halo sales are good

Low-margin halo products can weaken economics.

‍

4. Judging product launches on total sales alone

Separate promoted-product performance.

‍

5. Calling halo sales organic sales

Halo is advertising-attributed.

‍

6. Ignoring purchased-ASIN data

You need to know which products actually received the halo conversion.

‍

7. Comparing legacy and Unified metrics without mapping definitions

Amazon's 2026 Unified Reporting standardizes terminology and can broaden the meaning of some base conversion metrics.

‍

Amazon Halo vs. Promoted Sales Checklist

Before scaling a campaign, ask:

• Do we know total attributed sales?
• Do we know promoted sales?
• Do we know halo sales?
• Have we calculated halo sales share?
• Have we identified halo ASINs?
• Are those products profitable?
• Is the promoted ASIN itself converting?
• Does the revenue mix match the campaign objective?
• Are we accidentally evaluating halo sales as promoted sales?
• Are our Unified Reporting metric mappings correct?
• Have we connected attribution data to contribution margin?
• Are there cross-selling opportunities?
• Should halo winners receive dedicated advertising?
• Are low-margin halo products inflating ROAS?
• Are we measuring total business impact—not just dashboard sales?

FAQ

‍

What are Amazon halo sales?

Halo sales are ad-attributed sales of qualifying products other than the directly promoted product, according to the campaign's applicable expansion rules. Amazon has standardized older terms such as “Other SKU” and “Brand Halo” under the Halo qualifier in Unified Reporting.

‍

What are promoted sales?

Promoted sales are attributed sales of the directly advertised product. For seller reporting, Sales (promoted) was formerly known as 7 Day Advertised SKU Sales.

‍

Does Amazon's total Sales metric include halo sales?

Under the standardized Unified Reporting framework, base conversion metrics can represent the broader conversion total, while promoted-only metrics use the promoted qualifier. Advertisers should verify the applicable metric definition for their ad product and account.

‍

Are halo sales bad?

No.

Halo sales can indicate useful cross-selling or broader catalog impact.

Their value depends on:

• Profit margin
• Campaign goal
• Product relationship
• Incrementality
• Overall business economics

‍

Are halo sales organic sales?

No.

Halo sales are attributed to an advertising interaction. Organic sales are not ad-attributed in that same sense.

‍

Should I optimize for promoted sales or halo sales?

It depends on the campaign objective.

For a product launch or inventory-clearance campaign, promoted sales may deserve greater emphasis.

For brand-growth or cross-selling campaigns, halo revenue can be strategically important.

‍

How can I see which products generate halo sales?

Use the relevant purchased-product or converted-product reporting dimensions where available to identify which ASINs shoppers bought after an ad interaction. Amazon reporting includes purchased-product data for supported campaign types.

‍

Why did my Amazon reporting terminology change?

Amazon's 2026 Unified Reporting standardizes metric names and definitions across Sponsored Ads and Amazon DSP. “Brand Halo” and “Other SKU” terminology is increasingly standardized as Halo.

‍

Can Adorbix help analyze halo sales?

Yes. Adorbix can connect promoted sales, halo sales, purchased-ASIN data, PPC spend, ACoS, ROAS, TACoS, and ASIN-level profitability to determine what your advertising is actually producing.

‍

Key Takeaways

• Promoted Sales measure attributed revenue from the product directly promoted by the ad.
• Halo Sales measure attributed revenue from qualifying non-promoted products.
• Amazon's 2026 Unified Reporting makes promoted-vs-halo distinctions more explicit and standardizes older Brand Halo/Other SKU terminology.
• Base conversion metrics can represent broader results, so advertisers should use promoted-qualified metrics when they need directly advertised-product performance.
• Strong total ROAS can sometimes hide weak promoted-product performance.
• High halo revenue can reveal valuable cross-selling and gateway products.
• Halo revenue should be connected to ASIN-level margins, not evaluated as revenue alone.
• Product launches should be evaluated with promoted-product performance separated from broader catalog sales.
• Purchased-product reporting can reveal which ASINs are receiving halo conversions.
• The best PPC analysis connects attribution → product → profit.

‍

Final Takeaway: Stop Asking Only “How Much Did PPC Sell?”

The better question is:

What did PPC actually sell?

Amazon advertising can influence more than the ASIN sitting inside the campaign.

A shopper can click one product and buy another.

That can be valuable.

It can reveal:

Cross-selling opportunities.

Gateway ASINs.

Hidden product winners.

Brand-level demand.

But it can also hide:

Weak promoted-product conversion.

Poor launch performance.

Low-margin revenue.

Misleading ROAS.

That's why Amazon's promoted-vs-halo reporting matters.

At Adorbix, we don't stop at:

“Campaign ROAS is 5.0.”

We ask:

Which products generated that revenue?

Which sales were promoted versus halo?

How much margin did each produce?

And where should the next advertising dollar go?

Because the goal isn't simply to attribute more revenue to PPC.

It's to understand which revenue your PPC is actually creating—and whether that revenue deserves to be scaled.

‍