source in ZeroparkValidVisit's per-source rate is exactly what Zeropark's Sources blacklist (and auto-rules) consume.
Pop traffic scales easily — and that is precisely what makes source quality hard to audit. Zeropark aggregates domain-parked and pop-under placements across thousands of publisher zones worldwide, and most advertisers only see campaign-level CPA until something has already gone wrong. The absence of a human click gesture is what defines the pop channel's IVT exposure: any automated process that can open a URL can produce a billable pop event, which means the usual signal of a real user choosing to engage an ad simply does not exist here. Bot operators know this. Automated clients cycling through landing pages, residential proxy pools rotating per-event to mimic fresh visitors, and server-farm ranges dressed in consumer user-agent strings all show up in Zeropark pop inventory alongside genuine traffic from real users. ValidVisit attaches a lightweight scoring script to your landing page — no funnel hop, no change to the click path — and weighs every arriving click against 100+ independent data points spanning the network it came through, the device on the other end, and how the visitor actually behaves, folding them into a single 0–100 quality score so real people pass and automated traffic separates out. Each scored click is tagged with Zeropark's own tracking tokens, specifically Source ID ({source}) and Target ID ({target}), so your IVT reporting maps directly to the sub-sources you can act on inside the network's campaign controls.
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}Pop campaigns on Zeropark surface IVT through a few distinct mechanics that differ from display or native channels. The most straightforward pattern is a source zone ({source}) that delivers strong click volume at a competitive CPV bid but whose landing-page engagement collapses entirely — session durations in the low seconds, no scroll activity, no downstream pixel events. This happens when the client fetching the pop URL is not really driving a browser the way a person would. The behavioral side of ValidVisit's scoring is particularly telling here: genuine pop traffic loads the page and interacts with it, while a source zone built on bare URL fetching produces clicks that score poorly on the page-behavior data points at a rate well above your campaign baseline, and that discrepancy is visible in the zone-level breakdown.
A second pattern is network-origin concentration behind a specific Target ID ({target}). A single target placement within an otherwise acceptable source can route entirely through ranges tied to cloud hosting providers or proxy services. Because Zeropark resolves Target IDs at the individual pop-placement level, this is the granularity where that infrastructure clustering most often hides — it disappears in source-level aggregates, but the network-origin data points in each click's score pull it back into view.
Third, because each pop event already looks like a fresh visit by design, IP rotation through residential proxies is unusually easy to operate on pop inventory. The addresses appear clean; the geo matches your targeting. Even so, the way these clients connect and behave rarely matches a real visitor across the full set of signals ValidVisit weighs, so they tend to land low on the quality score even when the IP itself resolves to a residential range — a read that complements rather than duplicates what Zeropark's own filters can see.
Finally, Zeropark's keyword-targeted pop format means that competitors or arbitrageurs can automate specific search terms to repeatedly trigger branded pop inventory. The keyword token ({keyword}) in ValidVisit's reporting lets you correlate quality-score patterns with particular keyword targets, making this pattern visible rather than buried in aggregate campaign metrics.
Sort your ValidVisit dashboard by Source ID and compare each zone's average click score against your overall campaign baseline. A source delivering a disproportionate share of low-scoring clicks warrants scrutiny regardless of its volume — Zeropark's campaign controls let you exclude specific source IDs once you have identified them.
Target IDs represent individual pop placements within a source. ValidVisit tags each scored click with the Target ID so you can identify placements that consistently arrive through cloud-hosting or proxy infrastructure. A source zone may appear acceptable in aggregate while one or two of its target placements are routing almost exclusively through non-residential networks — the target-level view exposes what source-level averages conceal.
Part of every click's 0–100 score reflects how the visitor actually engages the landing page once it loads. On legitimate pop traffic that side of the score holds up. A source zone where clicks consistently score poorly on the page-behavior data points is a strong signal that traffic is arriving from clients fetching URLs without genuinely driving a browser — a characteristic pattern of automated pop generation.
For keyword-targeted pop campaigns, filter your ValidVisit reports by keyword and compare quality-score distributions between branded and generic terms. Branded keyword targets that show materially lower average click scores than generic ones may indicate automated triggering of your pop inventory by competitors or arbitrageurs.
Each Zeropark macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| 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 |
{cid}{campaign_id}{campaign_name}{source}{target}{creative_number}{keyword}Zeroparkitself isn’t the problem — bots and invalid traffic concentrate in a handful of its sub-sources: the publisher, site or zone, and the placement or widget within it. So we roll the score up by those Zeropark tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — Zeropark traffic scored 0–100 per sub-source, worst first.
See your own Zeropark sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{source}Sends a source ID. A source is a large traffic source containing multiple targets (publisher-level identifier).Bot / invalid-traffic score broken down by:
{target}Sends a target ID. The actual sub-placement of your ad within a source.Per-click id: Zeropark passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every click.
Compare bot & invalid-traffic breakdown across every ad network →Every click is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Each data point is combined rather than checked in isolation, so a genuine human almost never trips enough of them to be flagged — and bots that beat one rarely beat the rest.
The detection model is ours and stays that way. What you get is a clear verdict on every click — not a single brittle rule you can game, and not an unexplained number you can't act on.
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
ValidVisit scores and reports — it does not push exclusions to the network automatically. What it gives you is the Source ID ({source}) and Target ID ({target}) values for every low-scoring click, organized in the dashboard so you can identify which sub-sources are problematic. You then take those IDs into Zeropark's campaign interface and apply the exclusions yourself. This keeps you in control of bidding decisions and avoids the false positives that come with fully automated blocking. Automated exclusion via API is on the product roadmap but is not a current capability.
Zeropark's quality reporting reflects how traffic interacts with its own tracker — click delivery, deduplication, and basic fraud signals at the network level. ValidVisit scores how traffic interacts with your specific landing page, weighing 100+ data points the network's tracker never sees: where the click really originated, what device is behind it, and how the visitor behaves once your page loads, all rolled into a single 0–100 quality score per click. The result is a sub-source quality picture calibrated to your offer and destination, not to Zeropark's inventory in aggregate.
Yes. ValidVisit's script runs on whatever landing page URL the click reaches — it does not depend on which pop mechanic delivered the visit. Domain-parked and pop-under units both pass Source ID ({source}) and Target ID ({target}) in the Zeropark click URL, so the sub-source breakdown works identically across Zeropark's full inventory mix.
See which campaigns and publishers send real, converting traffic vs bots — every click scored 0–100.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis