Zeropark tracking tokens & macros
Zeropark is a pop and domain network where your traffic is bought across many publisher sources, and each one sends the visitor through to your landing page via the URL you set on the campaign. Appending these macros to that destination URL lets ValidVisit attribute every visit back to the exact source it came from, and judge each one Valid or Invalid, with its evidence, so you can see which sources are sending real visitors and which are sending invalid traffic.
Cross-check any macro against the network’s official documentation. Zeropark official docs →
On Zeropark, the buyer-facing identifier is the {source} token, which carries the source ID of the publisher that delivered the visit, while {target} pinpoints the individual target inside that source for even tighter granularity. The one required token is {cid}, the Click ID Zeropark sends for conversion tracking and marks as mandatory, and you can layer in {campaign_id}, {campaign_name}, {creative_number}, and {keyword} for fuller context. Note Zeropark's macros use lowercase names wrapped in curly braces, so keep them exactly as written; {source} and {target} are what let ValidVisit attribute a visit to the placement actually responsible for it.
Once every visit is tied to its {source}, per-source granularity becomes actionable: ValidVisit reports an invalid share for each source so you can tell apart the sources sending valid visits from those pushing bots and IVT. ValidVisit attributes and judges after the visit arrives and never pauses a Zeropark source on its own. You take the sources with a high invalid share to the campaign's Sources tab, tick them and choose Bulk actions → Pause, so the manual exclusion happens entirely in your own Zeropark dashboard.
Zeropark macro → ValidVisit param
| Token | Zeropark macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {cid} | vv_click_id | 8f3c1a2b-9d4e-4f12-bc77-0a1b2c3d4e5f |
| Campaign IDcampaign | {campaign_id} | vv_campaign_id | 1234567 |
| Campaign Namecampaign | {campaign_name} | vv_campaign_name | US_Pop_Sweepstakes |
| Source IDpublisher | {source} | vv_publisher_id | 5566778 |
| Target IDplacement | {target} | vv_placement_id | 9988776 |
| Creative Numbercreative | {creative_number} | vv_creative_id | 3 |
| Keywordkeyword | {keyword} | vv_keyword | best+vpn |
- Zeropark macro
{cid}- ValidVisit param
vv_click_id- Example
- 8f3c1a2b-9d4e-4f12-bc77-0a1b2c3d4e5f
- Zeropark macro
{campaign_id}- ValidVisit param
vv_campaign_id- Example
- 1234567
- Zeropark macro
{campaign_name}- ValidVisit param
vv_campaign_name- Example
- US_Pop_Sweepstakes
- Zeropark macro
{source}- ValidVisit param
vv_publisher_id- Example
- 5566778
- Zeropark macro
{target}- ValidVisit param
vv_placement_id- Example
- 9988776
- Zeropark macro
{creative_number}- ValidVisit param
vv_creative_id- Example
- 3
- Zeropark macro
{keyword}- ValidVisit param
vv_keyword- Example
- best+vpn
* required for Zeropark attribution.
Ready-to-use Zeropark tracking URL
https://yoursite.com/landing?utm_source=zeropark&utm_medium=pop&vv_click_id={cid}&vv_campaign_id={campaign_id}&vv_campaign_name={campaign_name}&vv_publisher_id={source}&vv_placement_id={target}&vv_creative_id={creative_number}&vv_keyword={keyword}Append these params to your landing-page URL — Zeropark fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which Zeropark sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the Zeropark tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What Zeropark tokens let you break bots down by
- Source ID — Sends a source ID. A source is a large traffic source containing multiple targets (publisher-level identifier).
- Target ID — Sends a target ID. The actual sub-placement of your ad within a source.
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
- Languagenot offered
Tokens last verified against Zeropark’s docs on 2026-10-02.
In the campaign’s Sources/Targets tab the buyer ticks the bad IDs (or pastes the list into the Search box), then Bulk actions → Pause; for a global block they paste target IDs into My Account → Blocked list.
Zeropark tracking token FAQs
Which Zeropark token identifies the source I should evaluate?+
The {source} token carries the source ID for the publisher behind each visit, and that is the unit ValidVisit reports on. If you want a finer level, add {target} to break a source down into its individual targets.
Is {cid} required?+
Yes. {cid} is the Click ID Zeropark sends for conversion tracking, and Zeropark's docs mark it as mandatory. It identifies each click so ValidVisit can attribute and judge each visit. The other tokens like {source}, {target}, {campaign_name}, and {keyword} are optional but add useful context.
Do I need a funnel hop to use these macros?+
No. These are plain URL parameters you append to your campaign's destination URL in Zeropark, following the format shown in their tracking docs. There is no funnel hop or extra hop required; Zeropark fills in each macro at click time and the values arrive with the visit.
Tracking tokens for other pop / pop-under networks
Judge every Zeropark visit — and find the fake ones.
See which Zeropark 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