Screen traffic on your own domain before the real page opens.
Smart Links let you place KillBot at the link layer, so campaign clicks, redirect domains, tracking domains, affiliate flows, and subdomains can be screened before visitors reach the final destination.
- Screen campaign clicks before the destination loads
- Use your own routing or tracking domain
- Send clean traffic forward and risky traffic to a safe URL
- Pair with Protected Pages when the final destination needs its own rules
- CampaignCleanAllowed
- TrackerProxy / VPNRedirected
- RedirectDatacenterRedirected
- SubdomainKnown botBlocked
When to use Smart Links.
Campaign links
Use Smart Links when paid or organic traffic first lands on a campaign URL before the real destination.
Redirect domains
Screen traffic on routing domains before sending visitors to the final page.
Tracking domains
Add a decision layer where tracking or click paths already exist.
Affiliate or partner flows
Control link-level routing before visitors reach offers or protected pages.
What the Smart Link layer does before the page opens.
-
Step 1
Campaign click arrives
A click from an ad, social post, email, or partner reaches the campaign URL.
-
Step 2
Smart Link receives the click
The routing domain handles the request before the destination is touched.
-
Step 3
KillBot evaluates IP, ASN, browser, category, and policy
Network, infrastructure, and behavior signals are scored together.
-
Step 4
Traffic is allowed forward, redirected, blocked, or rate-limited
The outcome lands in the Traffic Log with reason and decision.
Best first Smart Link route.
| Route type | Best when | Recommended action |
|---|---|---|
| Tracking domain | Campaign traffic already passes through this domain. | Add Smart Link screening first. |
| Redirect domain | The domain decides where visitors should go. | Use redirect-first handling for risky traffic. |
| Subdomain | You want cleaner link-layer control without changing the main site. | Use a Smart Link subdomain. |
| Affiliate flow | Traffic should be reviewed before the real offer opens. | Pair Smart Link with Traffic Log review. |
How Smart Links work with Protected Pages.
Smart Link only
Use when the routing domain is the main checkpoint. Best for campaign and redirect traffic.
Protected Page only
Use when visitors land directly on the final page. Best for forms, signup pages, and sensitive routes.
Smart Link + Protected Page
Use when both the click path and final destination need separate policies. Best for layered control.
Smart Link outcomes visible in Traffic Log.
Every click handled by a Smart Link is recorded with the same visit context as page-level decisions.
| Time | Smart Link | Country | Network | Category | Decision | Reason | Destination |
|---|---|---|---|---|---|---|---|
| 10:24 | go.ex/summer | US | Comcast | No match | Allowed | Clean | example.com/summer |
| 10:18 | trk.ex/aff | GB | FireHOL Proxy | Proxy | Redirected | Proxy feed | example.com/safe |
| 10:05 | go.ex/redir | DE | Datacenter | Datacenter | Redirected | Hosting | example.com/safe |
| 09:52 | sub.ex/cmp | FR | Apple | Search bot | Blocked | Bot category | — |
Common questions.
What is a Smart Link?
A Smart Link is a routing URL on your own domain that runs KillBot's decision pipeline before sending the visitor to a real destination. It's the link-layer counterpart to Protected Pages.
Do Smart Links replace Protected Pages?
No. They complement each other. Use Smart Links when traffic should be screened on a routing domain first; use Protected Pages when visitors land directly on the real destination. Many teams use both.
Can I use my own domain?
Yes. Smart Links sit on routing, tracking, or subdomain URLs you control. A common pattern is a routing subdomain like go.example.com in front of campaign destinations.
Can risky clicks be redirected instead of blocked?
Yes. Redirect-first rollout is the default. Risky clicks land on a safe URL while the team confirms the pattern in the Traffic Log before moving to stricter blocking.
Are Smart Link decisions logged?
Every click is recorded in the Traffic Log with IP, country, ASN, category, reason, source Smart Link, decision, and destination outcome.
Start with one Smart Link, review the log, then widen the route.
Add one routing domain to KillBot, run risky traffic in redirect mode, and use Traffic Log proof before scaling across campaigns.