Switch a domain to a direct redirect, with A/B

For some traffic — NSFW X/Twitter links, for example — the landing page is unwanted friction: you just want the visitor sent straight to the offer. Direct-redirect mode turns a domain from "serve the landing SPA" into "307 straight to the matched segment's primary button," with an optional A/B split so you can measure the difference before switching over completely.

Turning it on

Enable direct-redirect on the domain. Once on, the domain stops serving its landing page and instead:

1. Resolves the visitor's segment exactly like the landing would (by country/device rules).
2. 307-redirects them straight to that segment's primary button — the same URL the last button in the segment would open.

Turning it off restores the landing page exactly as it served before, with no republish needed — the redirect target is read from whatever is already published, so flipping the switch takes effect immediately either way.

Running it as an A/B test instead of a hard cutover

Pass a percentage (1–99) alongside enabling the mode, and that share of visitors gets the direct redirect (arm B) while the rest keep seeing the landing page (arm A). The split is sticky per visitor (hashed by subnet, no cookie needed), so a given visitor stays in the same arm across repeat visits. Omit the percentage and every visitor goes direct (100%, the pre-A/B behavior).

Both arms log clicks with the same request signals (device, UTM, referrer), tagged with which arm served them, so you can compare conversion between "landing page first" and "straight to OnlyFans" using the same clicks report you'd use for anything else.

Turning direct-redirect off resets the split back to 0%, so a later re-enable starts clean at 100% direct rather than resuming whatever split you'd left it at.

Safety carve-outs that still apply

Direct-redirect mode doesn't bypass the protections a landing page has:

• A visitor inside an in-app browser (Instagram, Facebook, TikTok, Telegram) still gets the landing page, not the redirect — those embedded webviews block a raw redirect, and the landing's own client-side escape is what gets them out.
• A bot or a datacenter/cloud IP still gets a quiet empty response, never the redirect and never counted toward either arm.
• A segment configured to block still blocks, before the A/B split is even considered.

What's next

Reading the A/B result once it's run? See Check a campaign's clicks for fraud for how to filter and total the clicks report.