DAO.AD tracking tokens & macros
One macro set having to serve push, pop, native, and banner traffic at once is a familiar challenge for multi-format self-serve networks, and DAO.AD handles it the way most of its peers do, a lean five-token set built around click, campaign, source, and creative that works the same regardless of format. Append those tokens to your destination URL and ValidVisit attributes every DAO.AD visit back to the source and sub-placement that sent it, then scores it 0-100.
Cross-check any macro against the network’s official documentation. DAO.AD official docs →
{click_id} is required and gives each visit a unique identifier ValidVisit ties back to DAO.AD. {source_id} is the publisher-level token, naming the traffic source behind a given push, pop, native, or banner impression, while {sub_id} goes finer still, identifying the specific placement or sub-source within that source, which is the level that tends to vary most when one macro set is stretched across four formats. {campaign_id} groups everything for reporting, and {creative_id} identifies the specific ad when a source is running more than one. All five populate automatically once DAO.AD serves the click, they're ordinary URL parameters rather than anything requiring a separate feed or export, so the destination URL works the same way across whichever format a given campaign happens to be using.
A source running push notifications and a source running native placements rarely produce the same quality of traffic even when they're nominally the same publisher account, and {sub_id} is what lets that difference actually surface instead of getting averaged away inside {source_id}. Scoring at that finer level is what tells you whether a source is worth keeping in full or only worth keeping for one of its formats. ValidVisit's part is limited to producing and reporting that score, it doesn't have a way to reach into DAO.AD and turn a sub-source off. That decision, and the action of making it, happens in your DAO.AD dashboard once the scores make the case for it.
DAO.AD macro → ValidVisit param
| Token | DAO.AD macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {click_id} | vv_click_id | abc123xyz |
| Campaign IDcampaign | {campaign_id} | vv_campaign_id | 123456 |
| Source IDpublisher | {source_id} | vv_publisher_id | pub_42 |
| Sub IDplacement | {sub_id} | vv_placement_id | plc_7 |
| Creative IDcreative | {creative_id} | vv_creative_id | 987 |
- DAO.AD macro
{click_id}- ValidVisit param
vv_click_id- Example
- abc123xyz
- DAO.AD macro
{campaign_id}- ValidVisit param
vv_campaign_id- Example
- 123456
- DAO.AD macro
{source_id}- ValidVisit param
vv_publisher_id- Example
- pub_42
- DAO.AD macro
{sub_id}- ValidVisit param
vv_placement_id- Example
- plc_7
- DAO.AD macro
{creative_id}- ValidVisit param
vv_creative_id- Example
- 987
* required for DAO.AD attribution.
Ready-to-use DAO.AD tracking URL
https://yoursite.com/landing?utm_source=dao-ad&utm_medium=push&vv_click_id={click_id}&vv_campaign_id={campaign_id}&vv_publisher_id={source_id}&vv_placement_id={sub_id}&vv_creative_id={creative_id}Append these params to your landing-page URL — DAO.AD fills the macros at click time, so every visit arrives attributed and ready to score. No funnel hop.
The buyer pastes the bad source IDs (or SubIds) into the campaign’s Blacklist field — or sets whitelist-only — and can additionally define up to 5 automatic rules that blacklist sources when a postback-fed condition is met.
blacklist/whitelist (source IDs) and subIdBlack/subIdWhite (hex-encoded SubIds), blackDomain/whiteDomain (domains)DAO.AD tracking token FAQs
What's the difference between {source_id} and {sub_id}?+
{source_id} identifies the publisher account, while {sub_id} identifies a specific sub-placement within it. Since one source can run multiple formats with very different quality, {sub_id} is usually the more useful level for ValidVisit to score.
Which token is required for DAO.AD attribution to work?+
{click_id}. It's the unique per-visit identifier ValidVisit needs to tie a click back to DAO.AD; {campaign_id}, {source_id}, {sub_id}, and {creative_id} all add optional detail.
Does the same macro set apply across all four formats DAO.AD offers?+
Yes. Push, pop, native, and banner traffic all use the same five tokens, so one destination URL template covers whatever format mix a campaign is running.
Score every DAO.AD click — and find the fake ones.
See which DAO.AD publishers and placements send real buyers vs. bots.
Free trial at launch · just your email
One script · no cookies · no fingerprinting · raw IP never stored