Pop / Pop-underPushNativeBanner / Display

Pop / Pop-under channel · judged Valid or Invalid

Which PlugRush subsources send bot traffic?

Q: Which PlugRush tokens should I put in my URL?

{$click_id} identifies the click and is what conversions match on. {$source_id} is the Subsource, the unit you blacklist, and {$source_referrer} its parent Source. {$campaign_id} and {$creative_id} add campaign and creative detail. PlugRush also offers {$domain_id}, the publisher’s registered domain, but that is the older Websites-tab level it now steers buyers away from in favour of Sources.

PlugRush traffic quality by Subsource: every push, pop, native and banner visit judged Valid or Invalid, so you know which S IDs to blacklist.

Not ready? Estimate your invalid clicks →

validvisit · plugrush cut-list

Exclude the bad subsource (S ID) in PlugRush

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.

Where: BUY TRAFFIC → Filter Traffic (blacklists and whitelists, each assigned to one or more campaigns; bulk add under the list editor’s Import Entries tab); also from the campaign’s Sources tab, and Automated Rules can apply an Exclusion to the Sources or Subsources breakdown

Controls in PlugRush’s campaign settings

✓ IP lists✓ OS✓ Browser✓ Language✓ Device✓ Connection

PlugRush macros mapped to report columns

2026-10-02

macros checked against PlugRush’s own docs

no-hop

one script, nothing added to the click path

Valid / Invalid

a verdict on every visit

01 / SIGNAL

How bot traffic slips in through PlugRush subsources.

PlugRush is a self-serve traffic network selling push notification, popunder, banner and native traffic, mainstream and adult, on desktop and mobile, bought on CPC bids. Its optimization model is built around Sources and Subsources: a Source (an R ID, passed by {$source_referrer}) is the referring domain, and a Subsource (an S ID, passed by {$source_id}) pinpoints traffic down to the adzone in most cases. PlugRush calls the Subsource the most precise way to track and blacklist. ValidVisit captures {$source_id}, {$source_referrer}, {$campaign_id} and {$creative_id} on arrival, with {$click_id} for conversion matching, and judges every visit Valid or Invalid with its evidence, so the Subsources you blacklist are chosen from the visits themselves.

PlugRush states that its system filters bots, scanners and other automated traffic on the fly, so what reaches your landing page has already passed the network’s own checks. What gets past them is rarely spread evenly: it gathers inside particular Subsources, sometimes a single adzone under a Source that is otherwise fine. PlugRush itself warns that blacklisting whole Sources by R ID can cut traffic that performs. Because {$source_id} rides on every click, ValidVisit attributes each visit’s verdict to its Subsource, so one bad S ID separates cleanly from the rest of its Source.

Conversion data alone is slow to show this on a new campaign, because a Subsource needs volume before a run of zero conversions means anything. The verdict on each visit is there as the traffic arrives, so a Subsource sending invalid visits stands out before it has spent its way into a conversion-based rule.

What to watch on PlugRush

Subsource ({$source_id}) invalid share

Rank active S IDs by invalid share. Subsources well above your campaign baseline are candidates for the blacklist you assign under Filter Traffic.

Source vs Subsource

Compare a Source’s ({$source_referrer}) invalid share with its Subsources’. If the invalid visits sit in one or two S IDs, blacklist those and keep the Source.

Before you unlimit

A limited campaign caps each Source at 5% and each Subsource at 1% of its traffic until you select “Receive unlimited traffic for selected”. Check a Subsource’s invalid share before you unlimit it: conversions show what worked, the verdict shows what the rest of its traffic was.

02 / VERDICTS

What PlugRush lets you judge by.

Publisher / site / zone

Invalid share broken down by:

Source (R ID) {$source_referrer}The Source: the referring domain the traffic came from.

Placement / widget

Invalid share broken down by:

Subsource (S ID) {$source_id}The Subsource, usually the adzone: the unit PlugRush recommends you blacklist.

Per-click id: PlugRush passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in PlugRush’s own reports.

Compare bot & invalid-traffic breakdown across every ad network →

See your own PlugRush sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes PlugRush traffic

Each PlugRush macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.

validvisit · tracking url

Tracking URL for PlugRush, ready for ValidVisit

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}

All PlugRush tracking tokens →

Token	PlugRush macro	Maps to	Identifies
Click ID	`{$click_id}`	click_id	click
Campaign ID	`{$campaign_id}`	campaign_id	campaign
Source (R ID)	`{$source_referrer}`	publisher_id	publisher
Subsource (S ID)	`{$source_id}`	placement_id	placement
Creative ID	`{$creative_id}`	creative_id	creative

Click ID

PlugRush macro: {$click_id}
Maps to: click_id
Identifies: click

Campaign ID

PlugRush macro: {$campaign_id}
Maps to: campaign_id
Identifies: campaign

Source (R ID)

PlugRush macro: {$source_referrer}
Maps to: publisher_id
Identifies: publisher

Subsource (S ID)

PlugRush macro: {$source_id}
Maps to: placement_id
Identifies: placement

Creative ID

PlugRush macro: {$creative_id}
Maps to: creative_id
Identifies: creative

Macros checked against PlugRush’s own documentation on 2026-10-02. PlugRush docs

The verdict works the same way on every network. ValidVisit never changes your PlugRush account: you make the exclusion there yourself. How the verdict works →

FAQ

PlugRush traffic quality, answered.

How do I blacklist a Subsource in PlugRush?

Under BUY TRAFFIC > Filter Traffic, create a blacklist and assign it to the campaign, then add the S IDs in the list editor, or bulk-import them new-line or comma separated under its Import Entries tab. Lists live apart from campaigns, so one list can apply to as many campaigns as you want, and a list can also hold IPs or IP ranges.

Can PlugRush blacklist Subsources automatically?

Yes. Automated Rules (the Rules button in the campaigns overview) can apply an Exclusion action to the Subsources breakdown, judged on the past 7 days of campaign stats. Rules need conversion tracking and act on conversions and traffic, so they move after a Subsource has spent; the verdict shows whether a non-converting Subsource was sending invalid visits or just visitors who did not buy.

Which PlugRush tokens should I put in my URL?

{$click_id} identifies the click and is what conversions match on. {$source_id} is the Subsource, the unit you blacklist, and {$source_referrer} its parent Source. {$campaign_id} and {$creative_id} add campaign and creative detail. PlugRush also offers {$domain_id}, the publisher’s registered domain, but that is the older Websites-tab level it now steers buyers away from in favour of Sources.