Is TwinRed traffic real?
How to check TwinRed traffic quality: every visit scored 0–100 and pinned to the banner / display sub-source that sent it — worst first, with the evidence to act on.
site / traffic source in TwinRedThe buyer opens Site Targeting, reviews the list of all eligible sites/traffic sources (TwinRed is transparent, all sources visible), and toggles each bad site to Block (or blocks all and allows only a whitelist) at campaign, placement, or account level.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and TwinRed supports OS, browser, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic shows up on TwinRed.
See which TwinRed publishers, placements and sub-sources send real clicks versus bots, attributed via TwinRed’s own tracking tokens and scored 0–100 per source.
Pinpoint the bot publishers & placements in TwinRed.
TwinRed itself isn't the problem — bots and invalid traffic concentrate in a handful of its sub-sources: the publisher, site or zone, and the placement or widget within it. So we roll the score up by those TwinRed tokens, not by creative (which says nothing about whether a click was human).
TwinRed traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- SSP ID
{sspId}
Bot / invalid-traffic score broken down by:
- Source Site
{sourceSite}
Per-click id: TwinRed passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every visit.
Compare bot & invalid-traffic breakdown across every ad network →See your own TwinRed sub-sources scored this way.
How ValidVisit attributes TwinRed traffic
Each TwinRed macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
https://yoursite.com/landing?utm_source=twinred&utm_medium=banner&vv_click_id={transactionId}&vv_campaign_id={campaignId}&vv_campaign_name={campaignName}&vv_publisher_id={sspId}&vv_placement_id={sourceSite}&vv_ad_id={adId}| Token | TwinRed macro | Maps to | Identifies |
|---|---|---|---|
| Transaction ID | {transactionId} | click_id | click |
| Campaign ID | {campaignId} | campaign_id | campaign |
| Campaign Name | {campaignName} | campaign_name | campaign |
| SSP ID | {sspId} | publisher_id | publisher |
| Source Site | {sourceSite} | placement_id | placement |
| Ad ID | {adId} | ad_id | ad |
- TwinRed macro
{transactionId}- Maps to
- click_id
- Identifies
- click
- TwinRed macro
{campaignId}- Maps to
- campaign_id
- Identifies
- campaign
- TwinRed macro
{campaignName}- Maps to
- campaign_name
- Identifies
- campaign
- TwinRed macro
{sspId}- Maps to
- publisher_id
- Identifies
- publisher
- TwinRed macro
{sourceSite}- Maps to
- placement_id
- Identifies
- placement
- TwinRed macro
{adId}- Maps to
- ad_id
- Identifies
- ad
How the detection works.
Data points → one score
Every visit is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Many angles, combined
Each data point is combined rather than checked in isolation, so a genuine human almost never trips enough of them to be flagged — and bots that beat one rarely beat the rest.
Proprietary, not a black box
The detection model is ours and stays that way. What you get is a clear verdict on every visit — not a single brittle rule you can game, and not an unexplained number you can't act on.
Pinned to the source
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
TwinRed traffic quality, answered.
How does ValidVisit detect invalid TwinRed traffic?+
Every TwinRed click is weighed against 100+ independent data points spanning the network it came from, the device behind it and how the visitor behaves — combined into a single 0–100 quality score so real humans pass and bots stand out.
Can I see which TwinRed publishers send bots?+
Yes. Using TwinRed's own tracking tokens, ValidVisit attributes each scored click to the publisher, placement and sub-source, so invalid traffic is pinned to the exact sub-source — which you can then exclude manually in TwinRed.
Does it require a funnel hop on my TwinRed links?+
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your TwinRed destination URLs.
Detect fraud on other banner / display networks
Catch the fake clicks on TwinRed.
See which campaigns and publishers send real, converting traffic vs bots — every visit scored 0–100.
Free trial at launch · just your email
One script · raw IP never stored · GDPR legitimate-interest basis