EZmob tracking tokens & macros
On EZmob, your push, pop and display traffic is spread across many publishers and the individual zones inside them, so a single campaign can mix great inventory with sources that send mostly noise. Appending these macros to your landing-page URL lets ValidVisit attribute every visit back to its exact publisher / zone and judge it Valid or Invalid, with its evidence, so you can finally see which sources are actually worth paying for.
Cross-check any macro against the network’s official documentation. EZmob official docs →
Attribution on EZmob hangs on the macros EZmob fills in at click time. The {publisher} and {pubzone} macros are the ones that matter most: {publisher} identifies the publisher delivering the impression and {pubzone} pins it down to the specific placement inside that publisher, which is the level a push buyer actually cares about. The {conversion} macro is required and gives each click a unique id so ValidVisit can line up each visit's verdict with the exact click in your reports, while {campaign} and {banner} add context about which campaign and creative drove it. These are plain URL parameters in EZmob's {brace} format, so no funnel hop or extra hop is involved.
Once every click is tied to its publisher and zone, per-source granularity is what makes the data actionable. ValidVisit judges the traffic and flags the bad {publisher} / {pubzone} combinations that are sending invalid traffic or bots; from there you add the subIDs behind them to your EZmob campaign’s SubID blocklist yourself. ValidVisit judges after the visit arrives and never edits your EZmob blacklist, so the exclusion stays in your hands inside the EZmob dashboard where you control your buy. Blaming the specific zone rather than the whole campaign means you keep the publishers that perform and cut only the placements dragging your quality down.
EZmob macro → ValidVisit param
| Token | EZmob macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {conversion} | vv_click_id | ck_ez |
| Campaign IDcampaign | {campaign} | vv_campaign_id | 44021 |
| Ad IDad | {banner} | vv_ad_id | ad_5 |
| Publisher IDpublisher | {publisher} | vv_publisher_id | pub_771 |
| Zone IDplacement | {pubzone} | vv_placement_id | zone_22 |
| SubIDclick | {subid} | subid | 771_22 |
- EZmob macro
{conversion}- ValidVisit param
vv_click_id- Example
- ck_ez
- EZmob macro
{campaign}- ValidVisit param
vv_campaign_id- Example
- 44021
- EZmob macro
{banner}- ValidVisit param
vv_ad_id- Example
- ad_5
- EZmob macro
{publisher}- ValidVisit param
vv_publisher_id- Example
- pub_771
- EZmob macro
{pubzone}- ValidVisit param
vv_placement_id- Example
- zone_22
- EZmob macro
{subid}- ValidVisit param
subid- Example
- 771_22
* required for EZmob attribution.
Ready-to-use EZmob tracking URL
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}Append these params to your landing-page URL — EZmob fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which EZmob sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the EZmob tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What EZmob tokens let you break bots down by
- Publisher ID — The publisher ID.
- Zone ID — The publisher's zone ID: the placement inside a publisher.
Carries a per-click id, stored with each visit so a verdict traces back to the click.
- IP exclusiondocumented
- Device targetingdocumented
- OS targetingdocumented
- Browser targetingdocumented
- Connection typedocumented
- Languagedocumented
Tokens last verified against EZmob’s docs on 2026-10-02.
The 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 tracking token FAQs
Which EZmob token identifies the sub-source I should judge?+
The {publisher} and {pubzone} macros. {publisher} tells you the publisher and {pubzone} narrows it to the exact placement within that publisher, which is the granularity ValidVisit reports at so you can spot the specific sources sending invalid traffic.
Is the {conversion} macro mandatory?+
Yes. {conversion} is the one required token here. It gives every click a unique identifier so ValidVisit can match each visit's verdict back to the exact click, keeping your EZmob reporting and ValidVisit's verdicts perfectly aligned.
Do I need a funnel hop, and where do these macros go?+
No funnel hop is needed. These are ordinary URL parameters in EZmob's {brace} format that you append to your destination/landing-page URL in your EZmob campaign settings. EZmob substitutes the real values at click time and ValidVisit reads them on arrival.
Tracking tokens for other push networks
Judge every EZmob visit — and find the fake ones.
See which EZmob publishers and placements send real buyers vs. bots.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored