TwinRed tracking tokens & macros
TwinRed's macro set leans on SSP terminology — SSP ID, Source Site — and that matches how the network describes itself: a self-serve ad network that is also an ad exchange, selling popunder, interstitial, banner, video and push inventory from its own direct publishers and from external exchanges and supply-side platforms connected over RTB and XML. That structure means a single TwinRed campaign can draw on direct sites and RTB partners at once. Appending TwinRed's tokens lets ValidVisit attribute each visit down to the transaction, the SSP, and the source site, and judge it Valid or Invalid, with its evidence.
Cross-check any macro against the network’s official documentation. TwinRed official docs →
{transactionId} is the token ValidVisit requires and uses as the click ID — every visit needs it to be individually addressable. {campaignId} and {campaignName}, which TwinRed describes as the ID and the name of the campaign, tie that transaction back to the campaign it belongs to. The two tokens that matter most for cleanup are {sspId} and {sourceSite}. TwinRed's public help page lists its tokens without describing them (the descriptions sit behind the "i" icon in creative setup), so read these two by their names: the supply-side platform ID and the source site. The portal's Traffic Sources tab is organised the same way, with RTB supply listed SSP by SSP and individual sources beneath. {adId}, which TwinRed describes as the ID of the ad, rounds it out. All six are populated by TwinRed automatically once they're appended as query parameters on your landing page URL — there's no separate integration step required beyond adding them to the URL in the creative's Media field.
Because one campaign can run across direct sites and RTB partners together, {sspId} and {sourceSite} are what let you see whether invalid visits come through one supply partner, or through a few sites inside it. ValidVisit only ever detects, judges, and reports on what arrives — it has no connection into TwinRed's bidding or delivery pipeline and can't cut off a source itself. Acting on an Invalid verdict means going back into your TwinRed dashboard and blacklisting the specific source or SSP on the campaign's Traffic Sources tab, or whitelisting the sources that have been coming back valid.
TwinRed macro → ValidVisit param
| Token | TwinRed macro | ValidVisit param | Example |
|---|---|---|---|
| Transaction ID *click | {transactionId} | vv_click_id | abc123xyz |
| Campaign IDcampaign | {campaignId} | vv_campaign_id | 123456 |
| Campaign Namecampaign | {campaignName} | vv_campaign_name | 123456 |
| SSP IDpublisher | {sspId} | vv_publisher_id | pub_42 |
| Source Siteplacement | {sourceSite} | vv_placement_id | plc_7 |
| Ad IDad | {adId} | vv_ad_id | 456789 |
- TwinRed macro
{transactionId}- ValidVisit param
vv_click_id- Example
- abc123xyz
- TwinRed macro
{campaignId}- ValidVisit param
vv_campaign_id- Example
- 123456
- TwinRed macro
{campaignName}- ValidVisit param
vv_campaign_name- Example
- 123456
- TwinRed macro
{sspId}- ValidVisit param
vv_publisher_id- Example
- pub_42
- TwinRed macro
{sourceSite}- ValidVisit param
vv_placement_id- Example
- plc_7
- TwinRed macro
{adId}- ValidVisit param
vv_ad_id- Example
- 456789
* required for TwinRed attribution.
Ready-to-use TwinRed tracking URL
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}Append these params to your landing-page URL — TwinRed fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which TwinRed sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the TwinRed tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What TwinRed tokens let you break bots down by
- SSP ID
- Source Site
Carries a per-click id, stored with each visit so a verdict traces back to the click.
- IP exclusiondocumented
- Device targetingdocumented
- OS targetingdocumented
- Browser targetingdocumented
- Connection typedocumented
- Languagenot offered
Tokens last verified against TwinRed’s docs on 2026-10-02.
The 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.
TwinRed tracking token FAQs
What does {sspId} identify?+
By its name, the supply-side platform a visit came through. TwinRed's public token list doesn't describe it, but the network says it buys from external exchanges and SSPs as well as direct publishers, and its Traffic Sources tab lists RTB supply SSP by SSP, so {sspId} is the closest thing to a supply-partner dimension for this network.
Which token functions as the click ID on TwinRed?+
{transactionId}. ValidVisit requires it and uses it as the unique identifier for every visit, the same role a dedicated click-id macro plays on other networks.
Can I exclude a bad source without pausing the whole campaign?+
Yes, but it happens manually. ValidVisit flags which {sourceSite} or {sspId} is sending invalid traffic; you take that information into your TwinRed dashboard and blacklist the specific source or SSP on the campaign's Traffic Sources tab yourself.
Tracking tokens for other banner / display networks
Judge every TwinRed visit — and find the fake ones.
See which TwinRed publishers and placements send real buyers vs. bots.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored