Which TwinRed sites send bot traffic?
Judge every TwinRed visit by {sspId} and {sourceSite}. Identify the sources inflating display, pop and push spend before you set your site targeting.
site / traffic source in TwinRedThe buyer opens the campaign’s Traffic Sources tab, reviews the eligible sources (TwinRed is transparent, all sources visible), and blacklists each bad source or whole SSP so it shows under Excluded (or switches to Whitelist Sources and allows only a whitelist), at campaign or account level.
How bot traffic slips in through TwinRed sites.
TwinRed is a self-serve ad network and ad exchange selling popunder, interstitial, banner, video and push inventory, and it exposes its supply chain unusually openly: it calls itself a transparent network in which advertisers can see all its traffic sources, and says it shows the exact source domains. Its token list includes {sspId}, {sourceSite} and {transactionId}, named for the supply-side platform, the source site and the transaction, so a quality problem can be pinned to a source rather than to the campaign. TwinRed describes a popunder as opening in a new browser window behind the current one, so the visit reaches your page without anyone having chosen your ad — the verdict attributed to {sourceSite} tells you whether those visits are valid, and that decides whether a source belongs on a blacklist or deserves a lower bid.
TwinRed says its traffic comes from two kinds of supply: direct publishers who have joined its network, and external ad exchanges and supply-side platforms connected through RTB and XML, which it uses to add volume. One campaign can draw on both at once, and TwinRed’s own advice is to start with a run-of-network campaign that tests all the sources, then optimise on the first results.
That makes the unit you judge by matter. An invalid share read per {sspId} shows which supply partner a problem comes through; the same share read per {sourceSite} shows whether it is the whole partner or a few sites inside it. Judging at the site level first keeps you from blacklisting an entire supply source over a problem confined to part of it.
What to watch on TwinRed
{sourceSite} within one {sspId}Group your report by {sspId}, then break each partner down by {sourceSite}. If a partner’s overall invalid share looks tolerable but its invalid visits concentrate in a few sites, that argues for blacklisting those sources rather than dropping the partner; TwinRed’s Traffic Sources tab can exclude either a single source or a whole SSP.
TwinRed’s formats reach visitors in different ways: a popunder opens behind the current window, an interstitial is a full-page ad between page loads, a banner sits within the page content. Its token list includes {format}; pass it, or keep formats in separate campaigns, and compare a source’s invalid share against other sources in the same format.
Because TwinRed shows every eligible source, you can whitelist only the sources that are judged valid instead of blacklisting the rest. When quality concentrates in a few {sourceSite} values, that is fewer decisions than blocking the long tail.
What TwinRed lets you judge by.
Invalid share broken down by:
- SSP ID
{sspId}
Invalid share broken down by:
- Source Site
{sourceSite}
Per-click id: TwinRed passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in TwinRed’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own TwinRed sub-sources judged this way.
How ValidVisit attributes TwinRed traffic
Each TwinRed macro maps to a normalized parameter, so every judged visit 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
Macros checked against TwinRed’s own documentation on 2026-10-02. TwinRed docs
The verdict works the same way on every network. ValidVisit never changes your TwinRed account: you make the exclusion there yourself. How the verdict works →
TwinRed traffic quality, answered.
Where do I block a site or source in TwinRed?
On the campaign’s Traffic Sources tab. Its Sources list groups supply into Direct and RTB, can be searched by SSP, Source ID or Source Name, and switches between Whitelist Sources and Blacklist Sources; a source or a whole SSP you blacklist appears under Excluded, and a Domains sub-tab sits beside it. TwinRed’s help centre says traffic sources can be allowed or blocked at campaign level and at account level. An older help article shows the same control as Campaign Site Targeting, with an account-wide Advertiser Site Targeting.
Which TwinRed tokens give the most useful segmentation in ValidVisit?
The pairing of {sspId} and {sourceSite}: by their names the first carries the supply-side platform and the second the source site, and it is usually the narrower of the two that isolates a problem worth acting on. {transactionId} is the per-visit identifier ValidVisit attributes on. {campaignId} and {adId}, the IDs of the campaign and the ad, show whether a weak pattern runs across a source or belongs to one ad. TwinRed’s public help page lists the tokens without describing them (the descriptions sit behind the “i” icon in creative setup), and the list also carries {source}, {sourceName} and {domain}, which line up by name with the Source ID, Source Name and Domains controls on the Traffic Sources tab.
Which targeting controls does TwinRed offer?
Country, region and city; carrier; device (desktop, mobile, tablet); operating system, including OS version ranges; browser; IP ranges, which can be targeted or excluded; content category; and days of the week. Site whitelists and blacklists and retargeting through TwinRed’s pixel sit alongside these. Language targeting is not documented.
Detect fraud on other banner / display networks
BIGO Ads
7Search PPC
ExoClick
PlugRush
TrafficHunt
AppLovinWeighing a blocker for banner / display traffic? How ValidVisit compares to Adscore, TrafficGuard and Opticks.
Find the bots in your TwinRed spend.
See which publishers and placements send real buyers vs bots — every visit judged Valid or Invalid, worst first.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored