Which ClickAdilla zones send real traffic?
Not all ClickAdilla 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.
spot in ClickAdillaThe buyer selects the campaign in Statistics, ticks the bad spot IDs (or domains in the Sites tab) and clicks "Add to black list", or pastes the spot/site list into the campaign's Sources white/blacklist; ClickAdilla then stops serving to those spots/sites.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and ClickAdilla supports OS version, browser version, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through ClickAdilla zones.
ClickAdilla is a self-serve, multi-format SSP — popunder, push, in-page, banner and video — connecting advertisers to a wide publisher base. That breadth makes it scalable but uneven: a small number of bot-heavy sites can absorb a disproportionate share of budget while campaign-level metrics stay ambiguous. ClickAdilla exposes a {site_id} and a {spot_id} (the specific ad spot/zone) on every click, alongside {campaign_id} and a {click_id} — and the site is the unit you blacklist in the campaign. ValidVisit captures these as each click lands, weighs the visit against 100+ independent data points covering the source network, the device and the visitor's behavior, and condenses them into one 0–100 quality score — then reports which sites and spots are carrying non-human traffic.
ClickAdilla's headline formats (popunder, in-page push) fire without a deliberate click, so the format offers no quality filter — automated page-loaders can trigger events at scale. The IVT patterns ValidVisit surfaces map onto the network's site/spot structure. First, infrastructure clustering by site: clicks that trace back to server farms or proxy/VPN exit points pile up inside particular {site_id} values rather than spreading evenly across the campaign.
Second, traffic that doesn't behave like a real browser: across that bundle of 100+ data points, a bot reveals itself through technical and behavioral mismatches that a clean user-agent string can't paper over. Third, clients that load the page but never act like people: sites with a disproportionate share of visitors who pull the HTML yet show none of the runtime behavior a genuine person produces are a reliable tell for automated loaders. Because {site_id} and {spot_id} ride on every click, ValidVisit attributes all of these to the individual site or spot, so one bad source is separable from a campaign that is otherwise clean.
What to watch on ClickAdilla
Sort active {site_id} values by quality and by the share of visits landing in the suspicious/bad tier. Sites running above your baseline are blacklist candidates.
Where a site is mostly clean but one {spot_id} is bad, the spot breakdown lets you cut the placement without losing the site.
Pop and push clicks that originate from cloud hosting or proxy/VPN infrastructure rarely convert. ValidVisit ties each such finding back to the {site_id} so you blacklist the offending sources cleanly.
When a single site shows a heavy concentration of low 0–100 scores, that points to automated loaders — and the verdict rests on signals far harder to fake than a user-agent string.
Pinpoint the bot publishers & placements in ClickAdilla.
ClickAdilla 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 ClickAdilla tokens, not by creative (which says nothing about whether a click was human).
Bought as one ClickAdilla line, your spend is a single number. Scored per sub-source it runs from 84 down to 28 — the worst is nearly all bots. That’s the leak a blended average hides.
ClickAdilla traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Spot / Zone ID
[SPOT_ID]The specific ad spot / zone within a site.
Per-click id: ClickAdilla 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 ClickAdilla sub-sources scored this way.
How ValidVisit attributes ClickAdilla traffic
Each ClickAdilla 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=clickadilla&utm_medium=pop&vv_campaign_id=[CAMPAIGN_ID]&vv_placement_id=[SPOT_ID]&vv_click_id=[CLICK_ID]| Token | ClickAdilla macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | [CAMPAIGN_ID] | campaign_id | campaign |
| Spot / Zone ID | [SPOT_ID] | placement_id | placement |
| Click ID | [CLICK_ID] | click_id | click |
- ClickAdilla macro
[CAMPAIGN_ID]- Maps to
- campaign_id
- Identifies
- campaign
- ClickAdilla macro
[SPOT_ID]- Maps to
- placement_id
- Identifies
- placement
- ClickAdilla macro
[CLICK_ID]- Maps to
- click_id
- Identifies
- click
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 spots on ClickAdilla.
Scoring and attribution are the means — the point is cutting the ClickAdilla 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 ClickAdilla 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 ClickAdilla spot and zone via the network's own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the spots 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 ClickAdilla and put your next dollar behind the traffic that converts.
ClickAdilla traffic quality, answered.
How do I set up ValidVisit for ClickAdilla?+
Add ValidVisit's script to your landing page and append ClickAdilla's macros — {site_id}, {spot_id}, {campaign_id} and {click_id} — to your destination URL. The pixel captures them as the visitor arrives and stores a scored verdict per visit, segmented by site and spot, with nothing on the click path.
Can ValidVisit tell me which ClickAdilla sites to blacklist?+
Yes. Because {site_id} is on every click, ValidVisit ranks your sources by quality and by what is dragging their scores down, and you blacklist the offenders in your ClickAdilla campaign. ValidVisit surfaces the evidence; the blacklist is applied in your account.
Will real but low-engagement pop visits score badly?+
No. The score is built from 100+ technical and behavioral data points about the source, device and visitor — not from time-on-page or scroll depth, which are naturally low for pop. A genuine person and an automated loader on a hosting IP look very different across those data points, regardless of how briefly the human stays.
Detect fraud on other pop / pop-under networks
Find the bots in your ClickAdilla 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