PlugRush tracking tokens & macros
A tagged PlugRush destination URL looks like yoursite.com/landing?clickid={$click_id}&sub={$source_id}&src={$source_referrer}&camp={$campaign_id}&cr={$creative_id}. Five tokens cover the click, the Subsource, the Source, the campaign and the creative. PlugRush fills each one when the click happens, and ValidVisit reads them on arrival, so every visit across its push, popunder, banner and native traffic is attributed to the Subsource that sent it, then judged Valid or Invalid, with its evidence.
Cross-check any macro against the network’s official documentation. PlugRush official docs →
{$click_id} is the one to always include. PlugRush describes it as the click_id used for conversion tracking, and it's the value its server-to-server postback sends back, so a verdict and a conversion line up on the same click. {$source_id} is the Subsource, an S ID such as S234, which PlugRush says pinpoints traffic down to the adzone in most cases. {$source_referrer} is its parent Source, an R ID for the referring domain. {$campaign_id} keeps campaigns apart, and {$creative_id} names the push ad, native ad or banner that ran. Every PlugRush token is written with a dollar sign inside the braces, so copy them exactly as shown.
The Subsource is the token to build your reporting around. PlugRush recommends blacklisting at that level and warns that cutting whole Sources by R ID can remove traffic that performs, so ValidVisit's invalid share per S ID is what tells you which entries belong on the blacklist you assign under Filter Traffic. PlugRush's FAQ also lists {$domain_id}, the publisher's registered domain, which is the older Websites-tab level, and descriptive tokens such as {$browser}, {$os} and {$cc}. ValidVisit reads the visitor's browser, system and country from the visit itself, so those add nothing to the verdict. None of this changes your PlugRush campaign: ValidVisit judges and attributes, and the blacklist is yours to edit.
PlugRush macro → ValidVisit param
| Token | PlugRush macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {$click_id} | vv_click_id | abc123xyz |
| Campaign IDcampaign | {$campaign_id} | vv_campaign_id | 123456 |
| Source (R ID)publisher | {$source_referrer} | vv_publisher_id | R123 |
| Subsource (S ID)placement | {$source_id} | vv_placement_id | S234 |
| Creative IDcreative | {$creative_id} | vv_creative_id | 987 |
- PlugRush macro
{$click_id}- ValidVisit param
vv_click_id- Example
- abc123xyz
- PlugRush macro
{$campaign_id}- ValidVisit param
vv_campaign_id- Example
- 123456
- PlugRush macro
{$source_referrer}- ValidVisit param
vv_publisher_id- Example
- R123
- PlugRush macro
{$source_id}- ValidVisit param
vv_placement_id- Example
- S234
- PlugRush macro
{$creative_id}- ValidVisit param
vv_creative_id- Example
- 987
* required for PlugRush attribution.
Ready-to-use PlugRush tracking URL
https://yoursite.com/landing?utm_source=plugrush&utm_medium=pop&vv_click_id={$click_id}&vv_campaign_id={$campaign_id}&vv_publisher_id={$source_referrer}&vv_placement_id={$source_id}&vv_creative_id={$creative_id}Append these params to your landing-page URL — PlugRush fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which PlugRush sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the PlugRush tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What PlugRush tokens let you break bots down by
- Source (R ID) — The Source: the referring domain the traffic came from.
- Subsource (S ID) — The Subsource, usually the adzone: the unit PlugRush recommends you blacklist.
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
- Languagedocumented
Tokens last verified against PlugRush’s docs on 2026-10-02.
The buyer creates a blacklist under Filter Traffic, adds the bad Subsource S IDs (PlugRush recommends Subsources over whole R-ID Sources, which can cut traffic that performs), and assigns the list to the campaigns it should cover.
PlugRush tracking token FAQs
Which PlugRush token should I judge on?+
{$source_id}, the Subsource. It's the finest unit PlugRush passes and the one it recommends blacklisting. Add {$source_referrer} as well, so you can see when a whole Source runs invalid rather than one Subsource inside it.
Why include {$click_id}?+
It's the value PlugRush's postback sends back, so it's what ties a conversion to the click. ValidVisit stores the same value on the visit, which puts the verdict and the conversion side by side.
Where do the tokens go?+
In your campaign or creative URL, as query parameters on the landing page link, written exactly as shown with the braces and the dollar sign. PlugRush notes that the exact way to insert {$source_referrer} and {$source_id} depends on your tracking setup; for ValidVisit they are plain URL parameters read on arrival.
Tracking tokens for other pop / pop-under networks
Judge every PlugRush visit — and find the fake ones.
See which PlugRush 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