Which EZmob zones send real traffic?
Not all EZmob traffic is equal. ValidVisit scores every visit 0–100 and pins it to the exact zone that sent it — so you can tell real humans from bots and invalid clicks, worst zones first.
subID in EZmobThe buyer pastes the bad subIDs (or zones for display) into the campaign's SubID/zone blacklist manager and clicks "Add to Blacklist", or selects and blocks them straight from the Source report.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and EZmob supports OS version, browser version, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through EZmob zones.
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 the visit 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.
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 visit 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.
What to watch on EZmob
Rank active {pub_id} values by quality and by the share of visits 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.
Pinpoint the bot publishers & placements in EZmob.
EZmob itself 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).
Bought as one EZmob line, your spend is a single number. Scored per sub-source it runs from 86 down to 12 — the worst is nearly all bots. That’s the leak a blended average hides.
EZmob traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Publisher ID
{pub_id}Publisher id — the source you blacklist in the campaign.
Bot / invalid-traffic score broken down by:
- Zone ID
{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 visit.
Compare bot & invalid-traffic breakdown across every ad network →See your own EZmob sub-sources scored this way.
How ValidVisit attributes EZmob traffic
Each EZmob macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
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}| 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 |
- EZmob macro
{campaign}- Maps to
- campaign_id
- Identifies
- campaign
- EZmob macro
{pub_id}- Maps to
- publisher_id
- Identifies
- publisher
- EZmob macro
{zone}- Maps to
- placement_id
- Identifies
- placement
- EZmob macro
{banner}- Maps to
- ad_id
- Identifies
- ad
- EZmob macro
{click_id}- Maps to
- click_id
- Identifies
- click
How the detection works.
Data points → one score
Every visit is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Many angles, combined
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.
Proprietary, not a black box
The detection model is ours and stays that way. What you get is a clear verdict on every visit — not a single brittle rule you can game, and not an unexplained number you can't act on.
Pinned to the source
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
How ValidVisit helps you cut fraud and bad subIDs on EZmob.
Scoring and attribution are the means — the point is cutting the EZmob traffic that wastes your spend. Here's how ValidVisit gets you a list you can act on.
- Score
See what's actually landing
You buy EZmob clicks; what arrives are visits. ValidVisit scores each one 0–100 so real humans stand out from bots and invalid traffic — one script, no funnel hop, no fingerprinting.
- Attribute
Pin the fraud to its source
Every scored visit is tied to the exact EZmob subID and zone via the network's own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the subIDs off your buy
You get the worst offenders as a ready-to-use list plus postbacks to your tracker — so you can exclude them in EZmob and put your next dollar behind the traffic that converts.
EZmob traffic quality, answered.
How do I set up ValidVisit for EZmob?+
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 visit, segmented by publisher and zone, with nothing on the click path.
Can ValidVisit tell me which EZmob publishers to blacklist?+
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.
Does ValidVisit cover all of EZmob's formats?+
Yes — push, pop, native and banner visits all run through the same scoring, with push adding subscriber-timing into the mix. Every visit gets a transparent 0–100 score built from 100+ data points and attributed to the publisher and zone behind it.
Detect fraud on other push networks
Find the bots in your EZmob spend.
See which publishers and placements send real buyers vs bots — every visit scored 0–100, worst first.
Free trial at launch · just your email
One script · no cookies · no fingerprinting · raw IP never stored