TrueVisit vs RedTrack
RedTrack is a click tracker with a bot blacklist built into its redirect path. TrueVisit is a verification layer that classifies every visit and stores why. Running both is the normal setup, not a choice between them.
Last updated
They are not alternatives
RedTrack is your source of truth for clicks, conversions, cost, and attribution across ad platforms. It routes traffic and reconciles spend. TrueVisit does none of that and is not trying to.
TrueVisit answers a narrower question: of the traffic that arrived, how much was a person, which zone or sub ID sent the rest, and what evidence backs that verdict when you take it to a network.
What each one is for
| Question | RedTrack | TrueVisit |
|---|---|---|
| How many clicks and conversions did I get | Yes | No |
| What did I spend and earn per campaign | Yes | No |
| Route a click through a redirect | Yes | No |
| How much of that traffic was a real person | Partially, through the bot blacklist | Yes, as the core product |
| Every verdict stored with a reason | Not the product focus | Yes |
| Did an AI crawler read my landing page | No | Yes |
What the bot blacklist does
RedTrack's anti-fraud toolbox filters traffic two ways: a soft filter that removes known good bots from reports while still letting them through, and a bot blacklist that blocks bad bots outright by IP or user agent. The blacklist only works with the redirect tracking option, per RedTrack's own help documentation. Checked August 26, 2026.
RedTrack's own documentation is explicit that this is not complete: a bot trap is not a 100 percent reliable method of detection, and some advanced bots pass through it. Most custom rules still need to be built by hand from the IP and user agent reports.
Where the two differ
| RedTrack bot blacklist | TrueVisit | |
|---|---|---|
| Verdict classes | Blacklisted or not | Human, suspected bot, confirmed bot |
| Reason stored per visit | Not a stored field | Yes, plain English plus a reason code |
| Names the specific bot | No | Yes, where known |
| Sees AI crawlers such as GPTBot | No, redirect based | Yes, through server-side collection |
| Blacklist export for ad networks | Manual IP or UA rules | Per field, plus an evidence CSV |
| Publisher invalid traffic risk score | No | GIVT and SIVT split, with an early warning |
| Entry price | From $69 per month, 2 million events | From $5 per month |
What RedTrack does better
- It blocks in real time at the redirect. A blacklisted bot never reaches the landing page and is not counted toward the event limit, at the moment the click happens. TrueVisit reports on a visit that already reached the page and cannot stop it from arriving.
- One platform for tracking, attribution, ad spend sync, and reporting across many networks at once.
- Postback protection with a secret key and IP whitelisting, guarding the conversion side of fraud that TrueVisit does not touch.
How they fit together
- Keep RedTrack as the source of truth for clicks, attribution, and revenue.
- Put the TrueVisit tag on your landing pages, passing the same click ID and sub ID parameters you already pass to RedTrack.
- When TrueVisit shows a zone or sub ID with a low quality score, block it at the traffic source, the same way you would act on a RedTrack blacklist hit.
TrueVisit captures the common sub ID, zone, and click ID parameter names automatically, so in most setups this needs no extra tagging work.