publisher / zone in EZmobValidVisit flags the bad {pub_id} / {zone}; add them to your EZmob campaign blacklist.
EZmob is a self-serve, multi-format network (push, pop, native, banner) reaching a broad publisher base across mobile and desktop. It exposes a {pub_id} (publisher), a {zone} (the publisher zone within it), {campaign}, {banner} and a {click_id} on every click — and the publisher/zone is the unit you blacklist in the campaign. ValidVisit reads those tokens the moment a click lands, then weighs it against 100+ independent data points — the network path it came in on, the device behind it and how the visitor actually behaves — and folds them into one 0–100 quality score, so real people pass and automated traffic stands out. The result is a clear read on which publishers and zones are carrying non-human clicks.
https://yoursite.com/landing?utm_source=ezmob&utm_medium=push&vv_campaign_id={campaign}&vv_publisher_id={pub_id}&vv_placement_id={zone}&vv_ad_id={banner}&vv_click_id={click_id}EZmob's breadth across formats and a long publisher tail means invalid traffic concentrates rather than spreads. On the pop/onclick side, automated page-loaders fire events out of hosting or proxy infrastructure, clustered in specific {pub_id}/{zone} values. On the push side, subscriber-zone quality varies — incentivised or bot-inflated feeds click in unnaturally regular bursts.
What makes both cases easy to separate is the scoring itself: every click is judged on dozens of network, device and behavioural signals at once, rolled into a single 0–100 score, so a placement that looks fine on volume can still rank near the bottom on quality. A server-farm origin, a connection profile that doesn't match the browser it claims to be, or a client that loads the page but never behaves like a person all drag the score down — and because {pub_id} and {zone} ride on every click, each low score attributes back to the individual source. A bad publisher or zone stays separable from the rest of a campaign.
Rank active {pub_id} values by quality and by the share of clicks in the suspicious/bad tier. Publishers above your baseline are blacklist candidates.
Where a publisher is mostly clean but one {zone} is bad, the zone breakdown lets you cut the placement without losing the publisher.
Pop and push clicks routed through cloud or proxy infrastructure rarely convert. ValidVisit ties each finding back to the {pub_id}/{zone} so you blacklist the offending sources cleanly.
A spike in bottom-tier scores within a single publisher or zone points to automation — the combined signal set is far harder to fake than a user-agent string.
Each EZmob macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | EZmob macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {campaign} | campaign_id | campaign |
| Publisher ID | {pub_id} | publisher_id | publisher |
| Zone ID | {zone} | placement_id | placement |
| Ad / Banner ID | {banner} | ad_id | ad |
| Click ID | {click_id} | click_id | click |
{campaign}{pub_id}{zone}{banner}{click_id}EZmobitself 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 EZmob tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — EZmob traffic scored 0–100 per sub-source, worst first.
See your own EZmob sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{pub_id}Publisher id — the source you blacklist in the campaign.Bot / invalid-traffic score broken down by:
{zone}Publisher zone id (placement within a publisher).Per-click id: EZmob 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.
Add ValidVisit's script to your landing page and append EZmob's macros — {pub_id}, {zone}, {campaign}, {banner} and {click_id} — to your destination URL. The pixel captures them on arrival and stores a scored verdict per click, segmented by publisher and zone, with nothing on the click path.
Yes. Because {pub_id} and {zone} are on every click, ValidVisit ranks your sources by quality and surfaces which ones are dragging scores down, and you blacklist the offenders in your EZmob campaign. ValidVisit reports the evidence; the block is applied in your account.
Yes — push, pop, native and banner clicks all run through the same scoring, with push adding subscriber-timing into the mix. Every click gets a transparent 0–100 score built from 100+ data points and attributed to the publisher and zone behind it.
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