Which UngAds zones send bot traffic?
ValidVisit judges every UngAds visit Valid or Invalid and pins it to the zone that sent it, worst first.
publisher ID in UngAdsThe buyer pastes the list of unprofitable publisher IDs into the campaign’s publisher list and switches it to "Exclude" (blacklist), or sets an auto-optimization rule (e.g. spend >= $50 and <1 conversion) that adds publishers to the campaign blacklist automatically.
How bot traffic slips in through UngAds zones.
UngAds is a push channel — exactly where invalid traffic concentrates. See which UngAds publishers, placements and sub-sources send real clicks versus bots, attributed via UngAds’s own tracking tokens and judged Valid or Invalid per source.
What UngAds lets you judge by.
Invalid share broken down by:
- Publisher ID
{site}
Per-click id: UngAds passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in UngAds’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own UngAds sub-sources judged this way.
How ValidVisit attributes UngAds traffic
Each UngAds macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.
https://yoursite.com/landing?utm_source=ungads&utm_medium=push&vv_click_id={subid}&vv_campaign_id={campaignid}&vv_publisher_id={site}&vv_ad_id={bannerid}| Token | UngAds macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {subid} | click_id | click |
| Campaign ID | {campaignid} | campaign_id | campaign |
| Publisher ID | {site} | publisher_id | publisher |
| Banner ID | {bannerid} | ad_id | ad |
- UngAds macro
{subid}- Maps to
- click_id
- Identifies
- click
- UngAds macro
{campaignid}- Maps to
- campaign_id
- Identifies
- campaign
- UngAds macro
{site}- Maps to
- publisher_id
- Identifies
- publisher
- UngAds macro
{bannerid}- Maps to
- ad_id
- Identifies
- ad
Macros not yet checked against UngAds’s documentation.
The verdict works the same way on every network. ValidVisit never changes your UngAds account: you make the exclusion there yourself. How the verdict works →
UngAds traffic quality, answered.
How does ValidVisit detect invalid UngAds traffic?
Every UngAds visit is checked against 100+ independent data points spanning the network it came from, the device behind it and the page it loaded. One thing a real visitor cannot produce makes it Invalid; otherwise it is Valid, with its evidence either way.
Can I see which UngAds publishers send bots?
Yes. Using UngAds's own tracking tokens, ValidVisit attributes each judged visit to the publisher, placement and sub-source, so invalid traffic is pinned to the exact sub-source — which you can then exclude manually in UngAds.
Does it require a funnel hop on my UngAds links?
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your UngAds destination URLs.
Detect fraud on other push networks
Adsterra
Bidvertiser
PlugRush
TrafficHunt
TwinRed
7Search PPCWeighing a blocker for push traffic? How ValidVisit compares to PureGuard, Adscore and Tracker bot filtering.
Find the bots in your UngAds spend.
See which publishers and placements send real buyers vs bots — every visit judged Valid or Invalid, worst first.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored