Pop / Pop-underWhich Zeropark sources send bot traffic?
Zeropark traffic quality by source and target: every pop visit judged Valid or Invalid, so you know which sources to cut before they drain your budget.
source in ZeroparkIn the campaign’s Sources/Targets tab the buyer ticks the bad IDs (or pastes the list into the Search box), then Bulk actions → Pause; for a global block they paste target IDs into My Account → Blocked list.
How bot traffic slips in through Zeropark sources.
Pop traffic scales easily — and that is what makes source quality hard to audit. Zeropark is a self-serve platform for pop and domain traffic, bought per view (CPV) across a large pool of publisher sources, and most advertisers only see campaign-level CPA until something has already gone wrong. Pop has no click gesture: Zeropark’s pop ads are triggered automatically by its publishers’ websites or by toolbars and extensions, and your landing page opens with no click needed, so the usual signal of a person choosing to engage with an ad does not exist. Zeropark passes Source ID ({source}) and Target ID ({target}) in the click URL, so IVT findings map directly to the sub-sources you can act on inside the network’s campaign controls.
Zeropark is direct about the limits of filtering. It says no ad network can guarantee 100% bot-free traffic, and that it filters and monitors its inventory for fraudulent activity. Whatever gets past that filtering arrives through a source ({source}), and it shows up as a source whose visits are judged invalid at a rate well above your campaign baseline.
A second pattern hides behind a specific Target ID ({target}). Zeropark defines a source as a publisher feed holding all the traffic from one publisher, and a target as a specific URL or location within it; some sources have one target, others have thousands. One target within an otherwise acceptable source can carry most of that source’s invalid visits, which is exactly what disappears in source-level aggregates.
Finally, keyword campaigns. On pop traffic Zeropark’s keywords are tied to the content of the site serving the ad, or are simply that site’s URL. The {keyword} token lets you correlate Invalid verdicts with particular keyword targets instead of burying the pattern in campaign totals.
What to watch on Zeropark
{source}) invalid share versus campaign baselineSort by Source ID and compare each source’s invalid share against your overall campaign baseline. A source delivering a disproportionate share of invalid visits warrants scrutiny regardless of its volume. Pausing a source excludes every target under it from that campaign.
{target}) invalid share inside a sourceTargets are the individual sub-placements within a source. A source may look acceptable in aggregate while one or two of its targets carry most of its invalid visits — the target-level view exposes what source-level averages conceal. Pausing a single target stops only that target, so the rest of the source keeps running.
{keyword}) invalid share by keywordFor keyword campaigns, compare invalid shares between keywords. A keyword with a materially higher invalid share than the rest can be paused from the campaign details view or added as a negative keyword, without touching the sources behind it.
What Zeropark lets you judge by.
Invalid share broken down by:
- Source ID
{source}Sends a source ID. A source is a large traffic source containing multiple targets (publisher-level identifier).
Invalid share broken down by:
- Target ID
{target}Sends a target ID. The actual sub-placement of your ad within a source.
Per-click id: Zeropark passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in Zeropark’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own Zeropark sub-sources judged this way.
How ValidVisit attributes Zeropark traffic
Each Zeropark 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=zeropark&utm_medium=pop&vv_click_id={cid}&vv_campaign_id={campaign_id}&vv_campaign_name={campaign_name}&vv_publisher_id={source}&vv_placement_id={target}&vv_creative_id={creative_number}&vv_keyword={keyword}| Token | Zeropark macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {cid} | click_id | click |
| Campaign ID | {campaign_id} | campaign_id | campaign |
| Campaign Name | {campaign_name} | campaign_name | campaign |
| Source ID | {source} | publisher_id | publisher |
| Target ID | {target} | placement_id | placement |
| Creative Number | {creative_number} | creative_id | creative |
| Keyword | {keyword} | keyword | keyword |
- Zeropark macro
{cid}- Maps to
- click_id
- Identifies
- click
- Zeropark macro
{campaign_id}- Maps to
- campaign_id
- Identifies
- campaign
- Zeropark macro
{campaign_name}- Maps to
- campaign_name
- Identifies
- campaign
- Zeropark macro
{source}- Maps to
- publisher_id
- Identifies
- publisher
- Zeropark macro
{target}- Maps to
- placement_id
- Identifies
- placement
- Zeropark macro
{creative_number}- Maps to
- creative_id
- Identifies
- creative
- Zeropark macro
{keyword}- Maps to
- keyword
- Identifies
- keyword
Macros checked against Zeropark’s own documentation on 2026-10-02. Zeropark docs
The verdict works the same way on every network. ValidVisit never changes your Zeropark account: you make the exclusion there yourself. How the verdict works →
Zeropark traffic quality, answered.
How do I exclude a source or target in Zeropark?
In the campaign’s Sources tab (or Targets tab), tick the bad IDs — or paste the list into the Search box — then choose Bulk actions → Pause. To block targets across every campaign, paste the target IDs into My Account → Blocked list; Zeropark lets a user blacklist up to 1000 targets there. Sources cannot be blocked account-wide by the user, only through Zeropark’s support team.
Which Zeropark tokens should I pass?
{cid} is Zeropark’s click ID and is mandatory for tracking visits. {source} is a large traffic source containing multiple targets; {target} is the actual sub-placement of your ad within that source. {campaign_id}, {campaign_name}, {creative_number} and {keyword} (on keyword campaigns) complete the set.
Zeropark shows me source-level data in its own reporting. What does ValidVisit add?
Zeropark’s campaign tabs report what it measures on its own side — the traffic bought, the spend, the bids and, once you send them back, the conversions — per source, target and keyword. ValidVisit judges what happens on your landing page, which Zeropark’s tracker never sees, so the sub-source picture is calibrated to your offer and destination rather than to Zeropark’s inventory in aggregate.
Does ValidVisit work the same way on Zeropark domain-parked traffic as on pop-under placements?
Yes. The script runs on whatever landing page the click reaches, whichever format delivered the visit. Domain and pop campaigns both pass Source ID ({source}) and Target ID ({target}) in the Zeropark click URL, so the sub-source breakdown works identically across Zeropark’s inventory mix. Add {traffic_type}, which sends POPUP or DOMAIN, to split the two.
Detect fraud on other pop / pop-under networks
TwinRed
7Search PPC
DAO.AD
PropellerAds
RichAds
AdcashWeighing a blocker for pop / pop-under traffic? How ValidVisit compares to PureGuard, Adscore and Tracker bot filtering.
Find the bots in your Zeropark 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