<b>Segmenting ad layout by traffic source</b>

<b>Segmenting ad layout by traffic source</b>

What it does: serves a denser, more aggressive layout to low-intent social/search-display traffic and a lighter one to loyal/direct visitors.

Setup effort: 4/5 — needs source detection (referrer/UTM) wired into your slot logic or A/B tool.

RPM lift seen: drive-by social traffic tolerates density it'll never return from anyway; loyal traffic you protect. Source-tuned layouts commonly add +8 to +15% blended RPM without nuking retention.

Pros
— Squeeze the bounce-prone, protect the loyal
— One of the few levers that improves RPM AND long-term LTV

Cons
— Real engineering; easy to misclassify and over-monetize loyalists
— Referrer data is leaky (dark social, app webviews)

Verdict: high effort, but the logic (aggressive for drive-by, light for direct) is sound and rarely done. Lift: ★★★★☆ — Risk: ★★★☆☆
Best for: sites with a real loyal/direct base. Skip if 90%+ of traffic is one cold source — nothing to segment.