Hide content buttons from bots and ad reviewers
Tune the per-domain bot filter, traffic split, and TikTok-bot cloak so moderation and scanner bots never see the real destination — without touching your links.
Ad platforms and app stores run automated reviewers and moderation bots against the links you submit. If one of them lands on your real funnel, it can flag or ban the placement. These settings hide the destination from a bot while a real visitor passes through completely unchanged — no link needs to be edited or replaced.
The TikTok-bot cloak (smart-link redirects)
Every /r/<slug> smart link ships with a cloak that catches TikTok's (and similar platforms')
moderation/scanner bots and 302s them back to your own landing page's root instead of onward to
OnlyFans. A human hitting the exact same URL passes through unchanged. The bot's click is still
logged — flagged is_bot = 1 — so it's auditable, but it's excluded from every funnel and fraud
count.
It has two switches:
- Per domain — the cloak checkbox in a domain's smart-link settings. On by default. Turning it off restores the pre-cloak behavior (a bare empty response to a detected bot) for that host only.
- Global kill switch — an emergency env-level override that disables the cloak for every host regardless of the per-domain setting. Reach for this only if the cloak itself is misbehaving fleet-wide; the per-domain checkbox is the one you want day to day.
The per-domain toggle takes effect within its normal cache window — you don't need to republish anything for it to apply.
Bot filter level and traffic split (visibility settings)
A domain's Visibility settings hold two more knobs, independent of the cloak above:
| Setting | Values | Effect |
|---|---|---|
| Bot filter level | off | basic | strict | How aggressively the landing page's own bot detection runs before rendering content. basic is today's default behavior. |
| Traffic split | on / off | On (default): visitors are routed to their matched segment as configured. Off: everyone gets served the single default segment, regardless of country/device rules. |
Both live on the same draft/publish record as a domain's escape-map settings, so a change here takes effect the same way the rest of that domain's visibility configuration does.
What this does not do
None of these settings touch your link inventory, your smart-link policy, or the landing page's content — they only decide who gets shown the real destination versus a safe fallback. To send everyone straight past the landing page instead, see Switch a domain to a direct redirect.
What's next
Want to verify the cloak is actually catching something? Check the fraud/is_bot signal in
Check a campaign's clicks for fraud.
Check a campaign's clicks for fraud
Filter the clicks report by domain, code, ad platform, or fraud-only, and read the totals row to spot inflated or bot-driven traffic.
Switch a domain to a direct redirect, with A/B
Send a domain's visitors straight to the matched segment's button with a 307, skipping the landing page — and A/B it against the landing before committing.