PushPop / Pop-under

Push channel · judged Valid or Invalid

Which DAO.AD sources send bot traffic?

DAO.AD traffic quality by source and sub-source: every push, in-page, pop and video visit judged Valid or Invalid, then blacklist or down-bid in DAO.AD.

Not ready? Estimate your invalid clicks →

validvisit · dao-ad cut-list

Exclude the bad source in DAO.AD

The buyer pastes the bad source IDs (or SubIds) into the campaign’s Blacklist field — or sets whitelist-only — can set per-source or per-SubId bids under Micro-bidding Rules, and can add automatic rules for BL that blacklist a Source ID when a postback-fed condition is met.

Where: Campaign settings Blacklist/Whitelist section (per-campaign), mirrored in the Campaign Management API as blacklist/whitelist (source IDs) and subIdBlack/subIdWhite (hex-encoded SubIds), blackDomain/whiteDomain (domains)

Controls in DAO.AD’s campaign settings

✓ IP lists✓ OS✓ OS version✓ Browser✓ Language✓ Device✓ Connection

DAO.AD macros mapped to report columns

2026-10-02

macros checked against DAO.AD’s own docs

no-hop

one script, nothing added to the click path

Valid / Invalid

a verdict on every visit

01 / SIGNAL

How bot traffic slips in through DAO.AD sources.

DAO.AD is a self-serve platform selling push notification, in-page push, popunder and video (VAST) traffic, and it describes itself as both an SSP and a DSP. Push and in-page push campaigns are bought on CPC, and the pay model is fixed once a campaign is created. Every click can carry {source_id} (the publisher source), {sub_id} (the sub-source inside it), {campaign_id} and {click_id}, plus {creative_id} on push, in-page push and video. Source and sub-source IDs are exactly what DAO.AD’s own blacklist and micro-bidding fields take, so ValidVisit’s invalid share per source and sub-source points straight at the setting you change.

DAO.AD’s formats reach a visitor in different ways, so invalid traffic gets in at different points. A popunder opens when someone clicks anywhere on the publisher’s page, so the visit itself says little about intent. In-page push renders on the site with no subscription at all. Classic push depends on a subscriber base, and DAO.AD passes how long ago the visitor subscribed through {subs_age}.

On the supply side, DAO.AD’s publisher guide offers a Link source type for monetising traffic without a website, naming social, messenger, purchased and arbitrage traffic as typical inputs. DAO.AD documents its own anti-fraud systems, automated checks and manual reviews, and says it does not accept bot, incentivised, VPN or proxy traffic. ValidVisit adds a verdict on each visit that actually reached your page, attributed to the {source_id} and {sub_id} that sent it, so what slips past the network’s filters shows up per source.

What to watch on DAO.AD

Sub-source ({sub_id}) invalid share

Rank {sub_id} values by invalid share within each {source_id}. Where one sub-source is bad and the rest of its source is valid, act on the sub-source and keep the source.

Traffic quality level ({quality})

DAO.AD sells traffic at low, regular, high and premium quality levels and recommends High or Premium. Add {quality} to your URL and check whether the level you target really shows a lower invalid share than the others.

Subscription age on push

DAO.AD groups push subscribers into 1-3, 4-7, 8-15 and 16+ day ranges. If invalid share concentrates in one {subs_age} range, narrow the Age of subscription targeting instead of dropping whole sources.

02 / VERDICTS

What DAO.AD lets you judge by.

Publisher / site / zone

Invalid share broken down by:

Source ID {source_id}

Placement / widget

Invalid share broken down by:

Sub ID {sub_id}

Per-click id: DAO.AD passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in DAO.AD’s own reports.

Compare bot & invalid-traffic breakdown across every ad network →

See your own DAO.AD sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes DAO.AD traffic

Each DAO.AD macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.

validvisit · tracking url

Tracking URL for DAO.AD, ready for ValidVisit

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}

All DAO.AD tracking tokens →

Token	DAO.AD macro	Maps to	Identifies
Click ID	`{click_id}`	click_id	click
Campaign ID	`{campaign_id}`	campaign_id	campaign
Source ID	`{source_id}`	publisher_id	publisher
Sub ID	`{sub_id}`	placement_id	placement
Creative ID	`{creative_id}`	creative_id	creative

Click ID

DAO.AD macro: {click_id}
Maps to: click_id
Identifies: click

Campaign ID

DAO.AD macro: {campaign_id}
Maps to: campaign_id
Identifies: campaign

Source ID

DAO.AD macro: {source_id}
Maps to: publisher_id
Identifies: publisher

Sub ID

DAO.AD macro: {sub_id}
Maps to: placement_id
Identifies: placement

Creative ID

DAO.AD macro: {creative_id}
Maps to: creative_id
Identifies: creative

Macros checked against DAO.AD’s own documentation on 2026-10-02. DAO.AD docs

The verdict works the same way on every network. ValidVisit never changes your DAO.AD account: you make the exclusion there yourself. How the verdict works →

FAQ

DAO.AD traffic quality, answered.

How do I blacklist a source in DAO.AD?

On the campaign page, open the Black/Whitelist section and enter the Source IDs, separated by commas, in the Blacklist of sources field, or use the Whitelist of sources to run only on approved ones. The same section takes IPv4 and IPv6 CIDR ranges. DAO.AD notes that changes are not always instant: users who already received a notification can still click.

Can I act on one sub-source instead of the whole source?

Yes. Micro-bidding Rules, in the same Black/Whitelist section, set a custom bid for specific Source IDs or Sub IDs. DAO.AD’s Campaign Management API also keeps a subId black list per campaign, with a batch call that adds sub IDs to several campaigns at once.

Can DAO.AD blacklist sources automatically?

Yes. Automatic rules for BL use IF-THEN conditions that pair spend, impressions or clicks with clicks, leads, ROI or cost per lead. They need a working postback that returns the {click_id}, and a triggered rule adds the Source ID to the campaign blacklist. ValidVisit’s verdicts come from the visits themselves rather than from conversions, so they read a source without waiting on lead data.

Does ValidVisit change my DAO.AD campaign?

No. ValidVisit judges each visit Valid or Invalid with its evidence and reports it by source, sub-source, campaign and creative. The blacklist, bid or rule change is yours to make in DAO.AD.