On EZmob, your push 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 click back to its exact publisher / zone and score it 0-100 for traffic quality, so you can finally see which sources are actually worth paying for.
Attribution on EZmob hangs on the macros EZmob fills in at click time. The {pub_id} and {zone} macros are the ones that matter most: {pub_id} identifies the publisher delivering the impression and {zone} pins it down to the specific placement inside that publisher, which is the level a push buyer actually cares about. The {click_id} macro is required and gives each click a unique id so ValidVisit can line up its quality score 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 scores the traffic and flags the bad {pub_id} / {zone} combinations that are sending invalid traffic or bots; from there you add those publishers and zones to your EZmob campaign blacklist yourself. ValidVisit only reports and scores after the click arrives, it never blocks or auto-excludes anything, 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.
| Token | EZmob macro | ValidVisit param | Example |
|---|---|---|---|
| Campaign IDcampaign | {campaign} | vv_campaign_id | 44021 |
| Publisher IDpublisher | {pub_id} | vv_publisher_id | pub_771 |
| Zone IDplacement | {zone} | vv_placement_id | zone_22 |
| Ad / Banner IDad | {banner} | vv_ad_id | ad_5 |
| Click ID *click | {click_id} | vv_click_id | ck_ez |
{campaign}vv_campaign_id{pub_id}vv_publisher_id{zone}vv_placement_id{banner}vv_ad_id{click_id}vv_click_id* required for EZmob attribution.
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}ValidVisit flags the bad {pub_id} / {zone}; add them to your EZmob campaign blacklist.
The **{pub_id}** and **{zone}** macros. **{pub_id}** tells you the publisher and **{zone}** narrows it to the exact placement within that publisher, which is the granularity ValidVisit scores so you can spot the specific sources sending invalid traffic.
Yes. **{click_id}** is the one required token here. It gives every click a unique identifier so ValidVisit can match its 0-100 quality score back to the exact click, keeping your EZmob reporting and ValidVisit's scoring perfectly aligned.
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.
See which EZmob publishers and placements send real, converting traffic vs. bots.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis