Which AdMaven zones send bot traffic?
Judge every AdMaven pop and push visit by sub_source_id. Surface the exact sites and widgets to add to your campaign block list — you make the cut.
source ID / sub-source ID in AdMavenPaste comma-separated Source IDs or Sub Source IDs (or import a CSV) into the campaign’s blacklist or the account-wide Global Blocked List, which applies to all current and future campaigns on Save Changes.
How bot traffic slips in through AdMaven zones.
AdMaven is a self-serve network selling pop, push (Classic Push and In-Page Push), interstitial and content locker traffic. Pop is bought on CPM or Smart CPA, push and content locker on CPC. Its traffic comes either from AdMaven’s direct sources or from third-party partners, and AdMaven identifies both with two IDs: {:source_id} for the source and {:sub_source_id} for the sub-source beneath it, written as SourceId_SubSourceId. ValidVisit captures {:source_id}, {:sub_source_id} and {:campaign_id} on arrival, with {:click_id} for conversion matching, and judges every visit Valid or Invalid with its evidence, so the IDs you block are chosen from the visits themselves.
A pop opens your page as a side effect of a visit to the publisher’s page, not from a click on your ad, so the format does nothing to filter automated page-loads. What gets through gathers in particular sub-sources rather than spreading evenly across the campaign. AdMaven’s own Global Blacklist guide puts suspicious or bot traffic first among its reasons to block a source, and warns against blocking on a single-day snapshot or before checking that the source isn’t converting in specific campaigns.
Conversion data answers that second question but is slow on the first: a sub-source needs volume before a run of zero conversions means anything, and zero conversions cannot tell automated visits from real people who did not buy. The verdict on each visit is there as traffic arrives, attributed through {:sub_source_id}, so a bad sub-source stands out before it has spent much of your budget.
What to watch on AdMaven
Rank active {:sub_source_id} values by invalid share. Sub-sources well above your campaign baseline are candidates for the campaign’s blacklist or the account’s Global Blocked List.
On AdMaven’s direct traffic a source stands alone, so its sub-source reads as the source ID plus _-1 (123456_-1). There the source is the finest unit you can judge or block; on third-party traffic the sub-source is the partner’s subid or zone.
Push campaigns choose between Direct Exclusive and Third-Party IDs traffic, and set Proxy Traffic to All, Proxy only or Non-proxy. Run each choice as its own campaign so {:campaign_id} keeps them apart, and compare their invalid shares before widening.
What AdMaven lets you judge by.
Invalid share broken down by:
- Sub-source / Site ID
{:sub_source_id}Sub-level source segmentation (site / widget / publisher) — the unit you add to the campaign block list.
Per-click id: AdMaven passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in AdMaven’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own AdMaven sub-sources judged this way.
How ValidVisit attributes AdMaven traffic
Each AdMaven 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=admaven&utm_medium=pop&vv_campaign_id={:campaign_id}&vv_source={:source_id}&vv_publisher_id={:sub_source_id}&vv_click_id={:click_id}&vv_creative_id={:creative_id}| Token | AdMaven macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {:campaign_id} | campaign_id | campaign |
| Source ID | {:source_id} | source | source |
| Sub-source / Site ID | {:sub_source_id} | publisher_id | publisher |
| Click ID | {:click_id} | click_id | click |
| Creative ID | {:creative_id} | creative_id | creative |
- AdMaven macro
{:campaign_id}- Maps to
- campaign_id
- Identifies
- campaign
- AdMaven macro
{:source_id}- Maps to
- source
- Identifies
- source
- AdMaven macro
{:sub_source_id}- Maps to
- publisher_id
- Identifies
- publisher
- AdMaven macro
{:click_id}- Maps to
- click_id
- Identifies
- click
- AdMaven macro
{:creative_id}- Maps to
- creative_id
- Identifies
- creative
Macros checked against AdMaven’s own documentation on 2026-10-02. AdMaven docs
The verdict works the same way on every network. ValidVisit never changes your AdMaven account: you make the exclusion there yourself. How the verdict works →
AdMaven traffic quality, answered.
Can I block an AdMaven sub-source across all my campaigns at once?
Yes. Besides each campaign’s own source and sub-source blacklist, AdMaven has an account-wide Global Blocked List under the profile icon that applies to all current and future campaigns. It takes comma-separated Source IDs, full Sub Source IDs such as 12345_ag9, and IP addresses or ranges, or a CSV import, and applies as soon as you click Save Changes.
Which AdMaven macros should I put in my URL?
{:click_id} identifies the click and is what conversions match on; AdMaven’s conversion test needs it. {:sub_source_id} is the unit you block, {:source_id} its parent, and {:campaign_id} and {:creative_id} add campaign and creative detail. AdMaven’s full macro list writes every macro with the colon, as here; two of its setup guides show the same names without it.
Does Smart CPA make this unnecessary?
Smart CPA optimizes toward your CPA goal and deprioritizes traffic with low or zero conversions. It acts on conversions, so it moves after traffic has spent and cannot say whether a non-converting source sent invalid visits or real people who did not buy. The verdict on each visit shows which.
Detect fraud on other pop / pop-under networks
Adsterra
Bidvertiser
ClickAdilla
Clickadu
ExoClick
HilltopAdsWeighing a blocker for pop / pop-under traffic? How ValidVisit compares to PureGuard, Adscore and Tracker bot filtering.
Find the bots in your AdMaven 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