ValidVisit judges every EZmob visit Valid or Invalid and pins it to the subID that sent it, worst first.
subID in EZmobThe buyer adds the bad subIDs to the campaign’s SubID blocklist with "Add to Blocklist" or switches them off, and can lower bids per subID instead.
EZmob is a self-serve and managed network for push, in-page push, pop, banner, video, direct click and keyword traffic, with a $100 minimum deposit, a $50 minimum campaign budget and blocking by subID. It advertises “0% fraudulent traffic” filtered by in-house and third-party technology, but its terms leave fraud decisions to its sole discretion, make its own reporting prevail after 3 days and offer no invalid-traffic credit, and first deposits aren’t refundable. Read visits per subID and block the weak ones. We don’t run EZmob campaigns ourselves; the facts below are EZmob’s own pages.
| Detail | |
|---|---|
| Formats | Push, in-page push, pop, banner, video, direct click and keyword. source |
| Minimums | A $50 campaign budget and a $10 daily cap; pop CPM from $0.20–0.50 and push CPC from $0.003–0.01 by tier. source |
| Minimum deposit | $100; $300 by USDT-ERC20 and $500 by wire. source |
| Fees | Card 4% + $0.30, PayPal 4.4–5.4% + $0.30, crypto and Capitalist 3.2%, wire and Payoneer 1%. source |
| Blocking | Edit Campaign → SubID step → Blocklist, or switch a subID off; IP ranges and referrer domains go in IP & Domain lists. source |
| Service | Self-serve, or a managed service where EZmob’s team makes the changes. source |
| Bot traffic | Claims “0% fraudulent traffic”, filtered by in-house experience and unnamed third-party technology. source |
| Terms | EZmob’s reporting prevails unless you dispute within 3 days, and fraud is decided at its sole discretion (§4.2, §7); no invalid-traffic credit. source |
| Refunds | First deposits aren’t refundable; later ones within 60 days, for $50 or 15%, whichever is higher. Its terms say 6 months and a 10% fee. source |
| Trustpilot | 3.1/5 from 43 reviews on 26 October 2026, mostly advertisers; complaints are about bot traffic, click-count gaps and refused first-deposit refunds. |
Checked against EZmob’s own pages on 2026-10-26. ValidVisit is independent of EZmob.
EZmob is a self-serve, multi-format network (push, in-page push, pop, banner, video, direct click and keyword) reaching a broad publisher base across mobile and desktop, and it sells both display inventory and XML feed traffic. Every click can carry {publisher} (the publisher), {pubzone} (the zone inside it), {subid} (the publisher feed subID), {campaign}, {banner} and the {conversion} click ID. The subID is the unit EZmob’s SubID blocklist works on, so it is the level ValidVisit’s invalid share is most useful at.
EZmob sells many formats across a wide range of publishers, and invalid traffic tends to concentrate in a few of them rather than spread evenly. A placement that looks fine on volume can still rank near the bottom on quality, and because {publisher}, {pubzone} and {subid} ride on every click, each Invalid verdict attributes back to the individual source.
EZmob’s own lists can block IP ranges and referrer domains, which handles addresses already known to be bad. Per-visit verdicts are what surface the sources those lists don’t name yet.
{subid}) invalid shareRank subIDs by invalid share. Those well above your campaign baseline are the ones to add to the campaign’s SubID blocklist.
{pubzone})Where a publisher is mostly valid but one {pubzone} is bad, the zone breakdown lets you cut the placement without losing the publisher.
EZmob’s {source} macro means different things by channel: the site or app ID for display, the publisher feed plus its original subID for XML feed traffic. Keep display and feed campaigns apart so a source value always means the same kind of thing when you compare invalid shares.
Invalid share broken down by:
{publisher}The publisher ID.Invalid share broken down by:
{pubzone}The publisher's zone ID: the placement inside a publisher.Per-click id: EZmob passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in EZmob’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own EZmob sub-sources judged this way.
Each EZmob 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=ezmob&utm_medium=push&vv_click_id={conversion}&vv_campaign_id={campaign}&vv_ad_id={banner}&vv_publisher_id={publisher}&vv_placement_id={pubzone}&subid={subid}| Token | EZmob macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {conversion} | click_id | click |
| Campaign ID | {campaign} | campaign_id | campaign |
| Ad ID | {banner} | ad_id | ad |
| Publisher ID | {publisher} | publisher_id | publisher |
| Zone ID | {pubzone} | placement_id | placement |
| SubID | {subid} | subid | click |
{conversion}{campaign}{banner}{publisher}{pubzone}{subid}Macros checked against EZmob’s own documentation on 2026-10-02. EZmob docs
The verdict works the same way on every network. ValidVisit never changes your EZmob account: you make the exclusion there yourself. How the verdict works →
EZmob is a working ad network with self-serve and managed options, published terms and subID-level blocking. First deposits aren’t refundable and its own reporting prevails after 3 days, so start small, judge visits per subID and block the weak ones early.
Open Edit Campaign, go to the SubID step and set the mode to Blocklist; add the bad subIDs with "Add to Blocklist", or switch a row’s status off. You can also adjust bids per subID there.
{conversion} is the click ID EZmob requires for conversion tracking, with {pixel} accepted as an alias. Add {publisher} and {pubzone} for publisher and zone, {subid} for the unit you blacklist, and {campaign} and {banner} for campaign and ad. EZmob rejects any macro not on its list, {click_id} included, and macros are case-sensitive, so copy them exactly as written.
Partly. EZmob documents IP-range and referrer-domain lists, as a whitelist or blacklist, alongside subID blocking; it doesn’t document a proxy-type filter.
Yes. EZmob passes your own UTM parameters through, for example utm_source=ezmob with utm_campaign={campaign}, and ValidVisit reads the UTMs and the EZmob macros on the same visit.
Weighing a blocker for push traffic? How ValidVisit compares to PureGuard, Adscore and Tracker bot filtering.
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