Campaign routing software for approved destinations
Campaign routing software decides which approved landing experience a valid visitor reaches — a localized page, a device-appropriate layout, or one arm of an A/B test. In Cloak4U, routing is strictly compliant: every target is real, approved content for genuine visitors, and the tool never switches content between reviewers and users. This guide explains geo routing, device routing, A/B testing, weighted distribution, and localization, and draws a firm line around what routing must never be used for.
cloak4u-campaign-routing-variants.pngWhat is campaign routing software?
Routing is the step that runs after traffic quality is assessed. Once a visitor has been judged valid — not a bot, proxy, or repeat offender — routing chooses the most relevant approved version of your destination. A visitor in Germany might see the German page; a visitor on a phone might see the mobile layout; a visitor in a test might see variant B. Each of these is a genuine, approved experience, not a decoy.
Filtering and routing are separate stages for a reason. Invalid traffic is handled by traffic quality filters and click fraud protection before routing ever runs, so routing only ever operates on real visitors heading to real content.
Marketers reach for routing because a single, static landing page rarely serves every audience well. A German visitor and a Brazilian visitor want different languages and currencies; a phone user and a desktop user want different layouts; a growth team wants to test a new headline against the current one. Routing solves all three without maintaining separate campaigns for each case — you point the ad at one entry point and let routing pick the right approved experience. The important discipline is that this convenience is used to improve relevance for real people, never to change what an ad reviewer sees.
Compliant routing, defined
Compliant routing means the decision about which page to show depends only on characteristics of a genuine visitor — their country, device, or a random test assignment — and every possible destination is content you would happily show anyone, including an ad reviewer. It explicitly does not mean detecting reviewers or bots and showing them something different from what real users see.
| Aspect | Compliant routing (Cloak4U) | Deceptive cloaking (out of scope) |
|---|---|---|
| Basis for routing | Geo, device, or A/B test assignment | Whether the visitor looks like a reviewer |
| All variants | Real, approved content | A decoy hides the real page |
| Reviewer experience | Same approved content as users | A different, sanitized page |
| Invalid traffic | Blocked or challenged | Sent to a safe decoy |
| Policy stance | Consistent with platform rules | Violates platform rules |
Geo routing
Geo routing sends valid visitors to the version of your offer that matches their location: local language, local currency, region-specific pricing, or the correct legal disclosures for their market. This improves relevance and conversion for real customers, and because each regional page is approved content, a reviewer landing on any of them sees a legitimate experience. Geo routing pairs naturally with the Timezone and geo signals described on the filters page, but here the goal is relevance, not blocking.
Geo routing also has a compliance-positive use: honoring regional requirements. Some offers must display different disclosures, pricing, or age gates depending on jurisdiction, and some are simply not available in certain markets. Routing lets you show each visitor the legally correct version of your page — and, where an offer is not available, a genuine “not available in your region” page rather than a broken experience. That is the opposite of hiding content: it is making sure every visitor sees the correct, approved content for where they actually are.
Device routing
Device routing directs visitors to the layout best suited to their hardware — a mobile-optimized page for phones, a fuller layout for desktops. The offer and message stay the same; only the presentation adapts. This is standard responsive-marketing practice and is fully compatible with platform policy, because every device variant carries the same approved content.
Device routing is worth doing because performance expectations differ sharply by hardware. Mobile visitors are more sensitive to page weight and tap-target size; desktop visitors have room for richer layouts and more detail. Serving each the appropriate rendering of the same offer tends to lift conversion for both without any change to the underlying message. As with geo routing, always keep a sensible fallback so an unrecognized device still lands on a working, approved page rather than nothing.
A/B testing and weighted distribution
A/B testing splits valid traffic between two or more approved variants so you can measure which performs better. Weighted distribution lets you control the split — for example a 90/10 ramp when testing a risky new design, or an even 50/50 for a clean comparison. The assignment is essentially random per visitor and has nothing to do with whether the visitor looks like a reviewer.
- Even split: 50/50 for a straightforward comparison of two approved pages.
- Ramp: start a new variant at a small share and increase it as confidence grows.
- Champion / challenger: keep most traffic on the proven page while a challenger earns its share.
Because all arms of the test are approved content, A/B testing in Cloak4U is about optimizing real experiences, not disguising anything. Results flow into the campaign analytics dashboard so you can compare variants on genuine, filtered traffic.
Testing on filtered traffic is what makes the results worth trusting. If invalid clicks were included in the split, a variant could look like a winner simply because it happened to receive more bot traffic that never had a chance of converting either way. By running filters first, Cloak4U ensures each variant is judged on the behavior of real visitors, so the winner you promote is genuinely the better page rather than an artifact of noise. This is a concrete example of why the filtering-then-routing order matters beyond compliance — it also protects the integrity of your experiments.
cloak4u-weighted-ab-distribution.pngLocalization
Localization is geo routing taken further: translating copy, adapting imagery, formatting dates and currency, and honoring regional expectations. Done well, it raises conversion for real visitors while keeping every localized page consistent with the ad that referred them. The rule is unchanged — each localized page must be a genuine, approved rendering of the same offer, acceptable to show any visitor including a reviewer.
A practical tip for localization is to keep a canonical “source of truth” version of the offer and treat each localized page as a faithful translation of it. When the offer changes — a new price, a new claim, a new disclosure — update every localized variant together so they never drift apart. Drift is where compliance problems creep in: if one locale quietly carries a claim the others do not, you have effectively created inconsistent content. Keeping variants in sync keeps the whole set honest and review-ready.
A useful self-test before adding any variant is to ask a single question: “Would I be comfortable showing this exact page to a Google or Meta reviewer, knowing real users see it too?” If the answer is yes for every variant, your routing is compliant by construction. If the answer is no for any variant — if a page exists specifically because you would not want it shown to real users, or specifically to be shown to reviewers instead of users — then it is not a routing variant at all, and it has no place in the system. This test keeps the line bright and easy to apply, even as your set of variants grows.
Limitations and risks
Geo and device detection are inferred from signals like IP and user-agent and can be wrong — a traveler, a VPN user, or an unusual device can be misrouted. Keep a sensible default variant so nobody hits a dead end. More importantly, routing is only compliant if you keep it compliant: never create a variant intended to be shown to reviewers but not users, and never wire routing to suspected-reviewer detection. Cloak4U does not guarantee perfect geo or device accuracy, and it does not support reviewer-versus-user content switching by design.
Conclusion
Campaign routing lets you send real visitors to the most relevant approved version of your offer — by geography, device, or experiment — without ever compromising on compliance. Filtering removes invalid traffic first; routing then optimizes the experience for the genuine visitors who remain, with every destination being content you would show anyone. Open the dashboard to set up your first routed campaign.