Traffic, clicks & redirect
The click/impression event pipeline, live redirect, and cloaking — hiding the real destination from bots and ad reviewers.
Every visit on a domain — a button tap, a /r/<slug> smart-link hit, a /t/<code> post link, a
/go/<id> partner relay — lands one row in the same click log, and every redirect decision
(who sees the landing, who gets sent straight to OnlyFans, who gets cloaked away) is made from
that same request in real time. This subsystem is where you read that log and tune those
redirect decisions, without touching the links or the landing page themselves.
Tasks
- Check a campaign's clicks for fraud/authenticity — filter by domain/code/ad platform/fraud, read totals.
- Hide content buttons from bots and ad reviewers — tune the bot filter and traffic split for a domain.
- Switch a domain to a direct redirect, with A/B — skip the landing page, compare conversion against it.
- Count clicks from a specific Telegram channel post — Telegram doesn't report this itself.
- Hide a partner smart link's real address — relay the redirect instead of exposing it directly.
Running into a discrepancy in the numbers or a redirect that isn't behaving? See Troubleshooting. Looking for a specific endpoint? See API reference gaps.
What's next
Back to Link for the rest of the product.