EvaDav tracking tokens & macros
Buying push or pop traffic on EvaDav means your spend is spread across thousands of individual zones, and the campaign report alone rarely tells you which ones are sending real subscribers versus padding. By appending EvaDav's macros to your destination URL, ValidVisit can attribute every visit back to its exact zone and judge it Valid or Invalid, with its evidence. You get a per-zone invalid share instead of one blended campaign number.
Cross-check any macro against the network’s official documentation. EvaDav official docs →
On EvaDav, attribution starts with {CLICKID}, the required click identifier the network stamps on every click so each visit can be matched one-to-one. The macro that actually matters for cleanup is {ZONE_ID}, the publisher zone the push subscriber came from, with {SOURCE_ID} and {CAMPAIGN_ID} adding context for which source and campaign drove it. Note EvaDav uses the curly-brace, all-caps macro format, so the tokens go in exactly as written, e.g. ?click_id={CLICKID}&zone={ZONE_ID} appended to your target URL.
Per-zone granularity is what turns a verdict into action. Once every click is tied to its {ZONE_ID}, ValidVisit ranks the zones sending the most invalid traffic and bots, and you take those zone IDs and add them to a blacklist Audience in EvaDav yourself. ValidVisit judges after the visit arrives and never touches your EvaDav account, so the exclusion stays a manual decision you make in EvaDav's own dashboard, against the specific zones dragging your numbers down rather than the network as a whole.
EvaDav macro → ValidVisit param
| Token | EvaDav macro | ValidVisit param | Example |
|---|---|---|---|
| Campaign IDcampaign | {CAMPAIGN_ID} | vv_campaign_id | 70021 |
| Zone IDpublisher | {ZONE_ID} | vv_publisher_id | s123 |
| Source IDsource | {SOURCE_ID} | vv_source | s123_abc |
| Click ID *click | {CLICKID} | vv_click_id | ck_evd |
- EvaDav macro
{CAMPAIGN_ID}- ValidVisit param
vv_campaign_id- Example
- 70021
- EvaDav macro
{ZONE_ID}- ValidVisit param
vv_publisher_id- Example
- s123
- EvaDav macro
{SOURCE_ID}- ValidVisit param
vv_source- Example
- s123_abc
- EvaDav macro
{CLICKID}- ValidVisit param
vv_click_id- Example
- ck_evd
* required for EvaDav attribution.
Ready-to-use EvaDav tracking URL
https://yoursite.com/landing?utm_source=evadav&utm_medium=push&vv_campaign_id={CAMPAIGN_ID}&vv_publisher_id={ZONE_ID}&vv_source={SOURCE_ID}&vv_click_id={CLICKID}Append these params to your landing-page URL — EvaDav fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which EvaDav sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the EvaDav tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What EvaDav tokens let you break bots down by
- Zone ID — Zone ID or common source ID (e.g. s123) — the unit you blacklist in the campaign.
Carries a per-click id, stored with each visit so a verdict traces back to the click.
- IP exclusionnot offered
- Device targetingdocumented
- OS targetingdocumented
- Browser targetingdocumented
- Connection typedocumented
- Languagedocumented
Tokens last verified against EvaDav’s docs on 2026-10-02.
The buyer creates an audience holding the bad zone or source IDs, then attaches it as a blacklist on the campaign; automated rules can also move sources that match the buyer’s conditions into a blacklist or whitelist audience.
EvaDav tracking token FAQs
Which token identifies the zone I should exclude?+
{ZONE_ID} is the one to watch. It maps each click to the specific EvaDav publisher zone, which is the unit you blacklist. {SOURCE_ID} and {CAMPAIGN_ID} add useful context, but {ZONE_ID} is what ValidVisit ranks so you know exactly which zones to add to your campaign blacklist.
Do I need a funnel hop or tracking script to use these macros?+
No. These are plain URL parameters appended to your target URL. EvaDav fills in {CLICKID}, {ZONE_ID}, {SOURCE_ID} and {CAMPAIGN_ID} at click time, so there is no extra hop or extra script required. {CLICKID} is the only required token; include it so every click can be matched.
Where do I add the macros, and where do I act on the results?+
Add the macros to your campaign's target URL in EvaDav (the destination link you set on the campaign). ValidVisit then judges each visit by zone; when a zone's invalid share climbs, you add that {ZONE_ID} to a blacklist Audience in EvaDav manually. ValidVisit never adds zones to that blacklist for you.
Tracking tokens for other push networks
Judge every EvaDav visit — and find the fake ones.
See which EvaDav 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