The Halo Effect of Display on Branded Search
The halo effect describes display or streaming advertising increasing branded search volume and efficiency, as shoppers exposed to the ad later search the brand name directly. It's a real, observable pattern in our own data, but it's also the easiest incrementality claim to overstate, because branded search volume moves for reasons that have nothing to do with any single campaign.
What this looks like in a real account
What the halo effect actually describes
The mechanism is straightforward: a shopper sees a DSP display or streaming ad, doesn't click, and later searches the brand name directly on Amazon — a touch that shows up entirely inside branded Sponsored Products reporting, with no visible link back to the display exposure that arguably started it. From the sponsored ads dashboard alone, that search looks like organic brand demand. It's only visible as a halo effect once you can see both the display exposure and the subsequent branded search together, which — as with most cross-channel questions on this site — means Amazon Marketing Cloud.
A real pattern from our own data
On one account we manage, organic order share rose from 13.5% before DSP spend began to 27.9% after it started, and was still climbing four weeks after every dollar of DSP spend had stopped — while branded-ads efficiency on the same account compressed from 48% to 37% TACOS and held there. Top-of-funnel video appears to have warmed an audience that then converted more efficiently across every channel, including ones DSP itself never touched. It's genuinely one of the strongest pieces of evidence we have that DSP should be measured against the whole account's performance rather than its own attributed sales alone — and it's one account, over one window, not a guaranteed pattern every brand should expect to replicate.
How the mechanism is supposed to work, and why it's plausible
Our own field observation across managed accounts is that DSP prospecting audiences typically run around two-thirds new-to-brand, and the visible downstream effect tends to show up first as growth in branded search volume — prospecting builds top-of-funnel awareness, branded search rises as a result, and existing sponsored ads campaigns get cheaper because more of the traffic hitting them already recognises the brand. The measurable second-order effect shows up in branded ACOS, not in the DSP report itself — which is exactly why a brand that only reads its DSP dashboard will systematically undervalue whatever halo effect its prospecting spend is actually producing.
Why this is the easiest incrementality claim to overstate
Branded search volume moves for a lot of reasons that have nothing to do with any specific display campaign — seasonality, a competitor's stockout, a press mention, an influencer post, a promotional email send. Attributing a branded search increase entirely to a concurrent DSP campaign, without isolating other plausible causes, is the single easiest mistake to make in this territory, because the timing correlation is genuinely persuasive on its own even when it's coincidental. The organic-lift example above is presented as one account's story specifically because it hasn't been independently reproduced across enough accounts to state as a general rule — it's a real, useful data point, not a benchmark.
The common mistake, including ours
The mistake is presenting a branded-search increase that coincides with a DSP campaign as proof of a halo effect without checking for other plausible causes first. We've made exactly this claim in a client update — pointing to a branded search uptick during a DSP flight as evidence the campaign was working — before checking whether a concurrent email send or a seasonal pattern could explain the same movement. It's a claim that flatters the channel being discussed, which is precisely the kind of claim that deserves the most scrutiny before it's repeated, not the least.
What to do if a geo-lift test finds no measurable halo effect
A null result on a halo-effect test is genuinely useful information, not a wasted exercise — it means, for this brand, this campaign and this window, display or streaming exposure isn't measurably moving branded search behaviour, and any prior story explaining a coincidental search increase deserves to be retired rather than repeated in the next report. Before concluding the halo effect simply doesn't exist for the brand, check test power the same way any incrementality test needs checking — a small or short test may simply lack the sample size to detect a real but modest effect, particularly for branded search volumes that are often smaller in absolute terms than total sales.
How to test for a genuine halo effect rather than assume one
The cleanest way to isolate a halo effect from coincidence is a geo-lift test measuring branded search volume specifically as the outcome metric, rather than sales — pause display or streaming spend in test markets, run normally in matched control markets, and compare branded search volume between the two over the test window. That controls for the seasonal and external factors a simple before-and-after comparison can't rule out, and it gives you a genuine causal read on whether the halo effect exists for your specific brand and campaign, rather than an inference from a single account's timing.
| Evidence type | What it shows | Confidence level |
|---|---|---|
| Timing correlation (search rose during a campaign) | A pattern worth investigating | Low on its own — many confounds possible |
| Our organic-lift account example (13.5% → 27.9%) | A real, documented case | Anecdotal — one account, one window |
| Field pattern (~2/3 NTB in prospecting, branded ACOS effect) | A repeated internal observation | Reported-internally — across our own accounts |
| Geo-lift test on branded search specifically | A causal, isolated measurement | Highest — designed to rule out confounds |
Which one you should actually pick
Any brand can test their own halo effect with a geo-lift design measuring branded search as the outcome — it needs patience and clean market matching, not a vendor. reMKTR treats halo-effect claims as a hypothesis to test rather than an assumption to repeat, having corrected our own premature version of the claim before, as part of the same discipline behind Full Circle's $500M+ in managed Amazon spend across 100+ brands.
Shortlist on the job, not the feature grid. Pull your search-term report for the last 90 days and total the spend against terms that produced no orders — 33.6% on the account above. Then ask each vendor on your list what they would do about it in week one, and see who answers with a process rather than a screenshot.
Common questions
Is the halo effect of display on branded search a proven, universal pattern?
The mechanism is plausible and we've observed it clearly on at least one account, but it hasn't been independently validated across enough accounts to state as a universal rule — treat any specific example, including ours, as a data point rather than a guarantee.
How do I check if my own branded search increase is a real halo effect?
Run a geo-lift test with branded search volume as the outcome metric, comparing markets with and without the display or streaming campaign — that isolates the effect from seasonal and external confounds a simple before-and-after read can't rule out.
Does DSP need to directly click-attribute a sale for the halo effect to matter?
No — that's the whole point of the effect. It shows up as improved branded search efficiency and volume, entirely outside DSP's own attributed sales report.
What else could explain a branded search increase besides a halo effect?
Seasonality, a competitor's stockout, press coverage, an influencer mention, an email send, or a promotion — all plausible causes worth ruling out before crediting a concurrent display campaign.
We show the method before the number.
Claim the free auditRead next
- Skai Pricing: Five Published Tiers, Read CloselyPricing · skai pricing
- Criteo vs Amazon DSP vs reMKTR: Which Demand You BuyHead to head · criteo vs
- Pacvue Pricing: No Public Number — What to AskPricing · pacvue pricing
- Skai vs Pacvue: Contracts, Not Feature GridsHead to head · skai vs pacvue