Bots get the safe page. Real buyers get the offer.
Automated traffic and visitors outside your targeting are routed to a safe default page; real users who match your audience reach your offer page. Routing is driven by a 3-layer antibot plus the targeting-rules engine, and SSL is issued automatically for every domain.
How traffic filtering works on TDS
Set the safe page and the offer
Create a template and define two destinations per link: the safe default page (one of 50+ templates or your own) and the offer page with click macros.
The antibot evaluates every visitor
A 3-layer pipeline scores each click: rule filter (IP/UA lists, referer allowlist) → ~40-signal fingerprint engine → ensemble scorer. Thresholds: ≥ 0.7 is a bot, ≥ 0.5 gets a CAPTCHA, below 0.5 passes.
Bots and off-target traffic get the safe page
Automated traffic and visitors that fall outside your targeting rules (geo, device, ISP, referer) are routed to the safe page, so your offer page is only served to the audience it was built for.
Real users reach the offer
Visitors who pass the antibot and match your rules are redirected to your offer. SSL is issued automatically per domain — no manual certificates.
Why it matters
- 50+ safe-page templates ready to use
- auto-SSL on any domain — no manual certificates
- Routing driven by a 3-layer antibot (~40 signals, 0.5 / 0.7 thresholds)
- Target by geo, device, ISP and referer
FAQ
How does it decide who sees the safe page?
Do I need my own server for this?
Can I use my own safe pages?
Open an account.
Decide in three days.
Full access to the Standard plan. No card required. Setup help on Telegram in 15 minutes.