whatismmm

Halo effect

A halo effect is one channel's spend showing up as another channel's performance: a TV campaign runs, branded search volume rises, and paid search books the revenue. The cause sits in one budget line while the credit lands in another, and models that ignore this systematically reward the harvest channels.

The canonical chain: broad-reach media (TV, video, audio, out-of-home) creates demand and awareness; that demand expresses itself later as branded search queries, direct visits, and higher conversion rates on performance channels. Last-click measurement assigns all of it to the last touch, which is almost always a bottom-funnel channel. The brand channel that caused the demand looks expensive; the channel that harvested it looks brilliant.

Modern MMMs attack this in two ways. Some model cross-channel paths explicitly, letting TV spend enter the branded-search equation as an input.1 Others rely on the decomposition mechanics: if TV's adstocked spend co-varies with revenue beyond what search spend explains, TV gets its credit directly.2 Either way, the model needs variation to see the effect; if TV has run at a constant level for two years, its halo is statistically invisible and lands in base.

What happens if halo is ignored: the reallocation spiral. Measured naively, brand looks weak, so budget moves to performance. Branded demand then thins, performance channels get more expensive per conversion, total efficiency drops, and the response is usually another round of the same cut. Brands discover the bottom of this spiral empirically, about two quarters after the CFO stops asking questions.

Worked micro-example

TV runs a $300k burst. Branded search clicks rise 20% for six weeks, producing $180k extra revenue attributed to paid search at its usual 4.0 ROAS. If the halo path is modeled, TV's contribution gains $180k and search's falls by the same; the two channels' ROAS figures move in opposite directions on identical raw data. The decomposition, not the dashboards, is where that argument gets settled. Figures are illustrative.

Source ledger

Every numeric claim on this page resolves to one of these primary sources.

  1. [1]Google Meridian documentationhttps://developers.google.com/meridianretrieved 2026-08-02
  2. [2]Meta Robyn feature documentationhttps://facebookexperimental.github.io/Robyn/docs/featuresretrieved 2026-08-02