Which Clickadu zones send real traffic?
Not all Clickadu traffic is equal. ValidVisit scores every visit 0–100 and pins it to the exact zone that sent it — so you can tell real humans from bots and invalid clicks, worst zones first.
zone in ClickaduThe buyer pastes their black/white list of zone IDs into the Sites&Zones ("Zone Limitation") field on the Zones & Additional page and flips the Exclude tumbler so the campaign stops serving on those zones.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and Clickadu supports OS version, browser, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through Clickadu zones.
Clickadu operates as a popunder and pop-up exchange where delivery is counted in tab-load events rather than deliberate user clicks. That mechanic opens a specific accountability gap: a page load fires whether or not a human triggered it, so bot operators and low-quality publisher zones can pile up delivery counts that look identical to real visits until you dig below the campaign surface. ValidVisit closes that gap by weighing each inbound visit against 100+ independent data points — covering the network and route the visit travelled, the device sitting behind it, and how the visitor actually behaves once the page is open — and folding all of them into a single 0-100 quality score. Genuine humans clear that bar comfortably; automation, click farms, and proxy-routed traffic stand out. Because Clickadu passes the originating zone through its {zoneid} macro, ValidVisit can pin every score to the exact zone that sent the visit, turning an otherwise opaque volume channel into a ranked list of sub-sources you can review and manually exclude inside Clickadu's campaign targeting interface.
Pop and popunder inventory scatters delivery across a wide zone pool, which means invalid traffic tends to arrive dispersed rather than concentrated — any single bad zone can look tolerable on its own while the aggregate quietly drains a meaningful share of budget with no obvious alert. On Clickadu specifically, the patterns ValidVisit most often surfaces fall into two distinct buckets. The first is infrastructure-level automation: visits that come from hosting ranges or residential-proxy pools where the IP looks like a consumer ISP but the wider picture points to a server farm or proxy provider. These visits usually carry a believable browser user-agent yet score poorly because too many of the supporting data points disagree with what a real browser on a real connection would produce. The second bucket is session-shell traffic: the pop fires, the page technically loads, but nothing a genuine person would generate follows — no real engagement, no natural timing, no sign of a live session. ValidVisit catches this even when the on-page environment has been carefully dressed up to look human, because the score draws on so many independent signals at once that a hollow session can't satisfy all of them. Both buckets resolve to specific {zoneid} values in ValidVisit's reporting, so you can tell a zone with a structural automation problem apart from one that simply draws a geo with lower engagement.
What to watch on Clickadu
Rank your active zones by average ValidVisit score using the {zoneid} token. Pop networks spread delivery across a long tail of publisher zones, and a small handful of those zones will usually account for a wildly disproportionate share of low-scoring visits. Pulling those zones out manually inside Clickadu's targeting interface is the single biggest lever for lifting traffic quality without cutting volume across the board.
Residential-proxy operations thrive on pop inventory because the tab-fire event needs no sustained interaction, which makes it cheap for bot farms to cycle through proxy pools. The score reflects when a visit's origin looks like a hosting or proxy provider even though the IP presents as residential, and ValidVisit surfaces the associated {zoneid} so you can exclude the zone rather than sacrificing an entire geo.
ValidVisit's quality score weighs how a visitor actually behaves after the page opens, independent of any single on-page check. On Clickadu pop traffic, clusters of low-behavior, low-scoring visits tied to specific zones are a strong tell for session-shell traffic — cases where the tab-load event fired but no real browser session followed. Because the score leans on many signals together, it still catches automation that has been hardened against any one conventional check.
Use the {campaignid} token alongside {zoneid} to track whether a campaign's zone pool composition drifts over time. A sudden jump in the share of delivery coming from zones with consistently poor scores — with no matching change in your targeting settings — can mean low-quality zones are backfilling available inventory as the better zones hit their delivery caps.
Pinpoint the bot publishers & placements in Clickadu.
Clickadu itself isn't the problem — bots and invalid traffic concentrate in a handful of its sub-sources: the publisher, site or zone, and the placement or widget within it. So we roll the score up by those Clickadu tokens, not by creative (which says nothing about whether a click was human).
Bought as one Clickadu line, your spend is a single number. Scored per sub-source it runs from 84 down to 24 — the worst is nearly all bots. That’s the leak a blended average hides.
Clickadu traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Zone ID
{zoneid}ID of the ad zone (publisher site/zone) where the ad was displayed.
Per-click id: Clickadu passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every visit.
Compare bot & invalid-traffic breakdown across every ad network →See your own Clickadu sub-sources scored this way.
How ValidVisit attributes Clickadu traffic
Each Clickadu macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
https://yoursite.com/landing?utm_source=clickadu&utm_medium=pop&vv_campaign_id={campaignid}&vv_click_id=${SUBID}&vv_publisher_id={zoneid}&vv_creative_id={bannerid}| Token | Clickadu macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {campaignid} | campaign_id | campaign |
| Click ID (SubID) | ${SUBID} | click_id | click |
| Zone ID | {zoneid} | publisher_id | publisher |
| Banner/Creative ID | {bannerid} | creative_id | creative |
- Clickadu macro
{campaignid}- Maps to
- campaign_id
- Identifies
- campaign
- Clickadu macro
${SUBID}- Maps to
- click_id
- Identifies
- click
- Clickadu macro
{zoneid}- Maps to
- publisher_id
- Identifies
- publisher
- Clickadu macro
{bannerid}- Maps to
- creative_id
- Identifies
- creative
How the detection works.
Data points → one score
Every visit is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Many angles, combined
Each data point is combined rather than checked in isolation, so a genuine human almost never trips enough of them to be flagged — and bots that beat one rarely beat the rest.
Proprietary, not a black box
The detection model is ours and stays that way. What you get is a clear verdict on every visit — not a single brittle rule you can game, and not an unexplained number you can't act on.
Pinned to the source
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
How ValidVisit helps you cut fraud and bad zones on Clickadu.
Scoring and attribution are the means — the point is cutting the Clickadu traffic that wastes your spend. Here's how ValidVisit gets you a list you can act on.
- Score
See what's actually landing
You buy Clickadu clicks; what arrives are visits. ValidVisit scores each one 0–100 so real humans stand out from bots and invalid traffic — one script, no funnel hop, no fingerprinting.
- Attribute
Pin the fraud to its source
Every scored visit is tied to the exact Clickadu zone and zone via the network's own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the zones off your buy
You get the worst offenders as a ready-to-use list plus postbacks to your tracker — so you can exclude them in Clickadu and put your next dollar behind the traffic that converts.
Clickadu traffic quality, answered.
ValidVisit scores every visit — what do I actually do with those scores on Clickadu?+
ValidVisit is a detection and reporting tool. It scores traffic after the click has already arrived and never blocks, diverts, or intercepts anything in the click path. What you get is a scored, zone-attributed record of every visit: you see which {zoneid} values are sending a disproportionate share of low-scoring traffic, export that list, and then manually add those zones to the exclusion list inside your Clickadu campaign targeting. The value is in making that zone-level call with signal instead of guesswork — the exclusion itself happens inside Clickadu's interface, not inside ValidVisit.
Clickadu exposes {zoneid} and {campaignid} — is one more useful than the other for IVT analysis?+
For diagnosing traffic quality, {zoneid} is the primary dimension. Invalid traffic on pop inventory originates at the publisher zone — the individual site or zone group that fires the pop event — not at the campaign level. {campaignid} is useful for working out which of your campaigns is drawing from a particularly rough zone pool, and for separating performance issues that are zone-driven from ones that might reflect targeting or landing-page factors. The actionable exclusion unit, though, is always the zone.
Does Clickadu's own invalid traffic filtering make ValidVisit redundant?+
Clickadu applies platform-level filtering aimed at protecting delivery integrity across its whole network. That filtering isn't transparent to you as an advertiser — you can't see what was filtered, which specific zones were dropped, or whether the thresholds match your own campaign's risk tolerance. ValidVisit runs on your side of the click, scoring traffic against your campaign's actual conditions by weighing 100+ independent data points into a single 0-100 quality score, then tying that score to specific {zoneid} values. The two layers answer different questions: Clickadu's filtering is about network-wide delivery hygiene; ValidVisit is about understanding which sub-sources inside Clickadu's delivery are polluting your conversion and optimization data.
Detect fraud on other pop / pop-under networks
Find the bots in your Clickadu spend.
See which publishers and placements send real buyers vs bots — every visit scored 0–100, worst first.
Free trial at launch · just your email
One script · no cookies · no fingerprinting · raw IP never stored