Compliance

Traffic routing vs compliant personalization: where the line is

By the ROAS365 team·7 min read

Showing different visitors different content is one of the most common things on the web — every personalized homepage does it. So why is some of it standard practice and some of it against ad-platform policy? The distinction is not "different content" versus "same content"; it is about intent and consistency. This article draws the line between compliant same-URL personalization and setups that policies target, so you can tell which side a given approach sits on.

TL;DR
  • Personalizing content for different visitors under the same URL — region, device, returning vs new — is standard and allowed.
  • What policies target is showing automated checks a materially different page than real users see, to obscure the campaign's true destination.
  • The practical tests are intent (are you hiding the offer from checks?) and consistency (do both audiences see the same core proposition?).
  • If your two surfaces really share the same core offer, you may only need personalization, not a two-surface split.

Same-URL personalization is standard

Serving a visitor in Tokyo a different hero image than a visitor in Berlin, or showing a returning customer a different call to action, is ordinary personalization. It happens under one URL, every visitor can in principle reach the same content, and there is no attempt to hide the page's real purpose from anyone. Ad platforms explicitly allow this — it is how modern landing pages work. The methodology for testing variants under one URL is its own topic; see same-URL A/B testing.

What ad-platform policies actually target

Policies target the case where automated checks are shown a materially different page than real users, specifically to obscure where the campaign really sends people. The signal platforms care about is the mismatch itself — a review sees one proposition, the user sees another. It is the divergence and the intent to conceal, not personalization per se, that policies name. The concrete behaviors that cross this line are enumerated in the red-line checklist, and the detection side is covered in how platforms detect these setups.

Two practical tests

When you are unsure which side an approach sits on, two questions usually settle it. First, intent: are you varying content to serve visitors better, or specifically to keep checks from seeing the real offer? Second, consistency: do both audiences encounter the same core proposition, just tailored — or two fundamentally different value propositions? If the answers are "serve better" and "same core," you are in personalization territory. If they are "hide from checks" and "different offer," you are in the territory policies target.

What this means for how you build

The useful consequence is that many goals people reach for a two-surface split can be met with personalization instead — and personalization carries less policy risk. If your real page and safe page would actually share the same core offer, a same-URL personalized page may be all you need, structured as described in the two-surface structure guide. Reserve a genuine two-surface setup for cases where the surfaces genuinely differ, and read the analytics to keep the split honest — see reading the analytics.

FAQ

Is showing different content to different visitors against the rules?
Not by itself. Same-URL personalization by region, device or history is standard and allowed. Policies target showing checks a materially different page to hide the real offer.
What is the single clearest difference?
Intent and consistency: personalization serves the same core proposition better; the targeted case hides a different proposition from checks.
Can personalization replace a two-surface setup?
Often, yes — when the surfaces would share the same core offer. Reserve two-surface setups for cases where the surfaces genuinely differ.
← Back to all articles