Is PropellerAds traffic real? How to check PropellerAds traffic quality
zone in PropellerAdsValidVisit ranks the bad zone_ids; add them to PropellerAds' zone Exceptions / block list.
PropellerAds aggregates inventory across thousands of independent publishers, making it one of the broadest reach networks for push notification and pop-under formats. That publisher breadth is its core value proposition — and the same reason that traffic quality varies sharply from one zone to the next. Push notification inventory carries a specific IVT dynamic: subscriber lists grow quickly and age slowly. Bot-enrolled devices and abandoned browsers can remain inside a push subscriber pool for months, generating click events that have no human behind them. The mechanism is different from display IVT — the click is real in the sense that a device responds to a push trigger, but the device is either automated or a dormant endpoint with no purchasing intent. Pop and popunder zones add a second pressure: publisher-side automation can fire impression and click events from environments that never load a page the way a person would, producing sessions that touch your landing page without any genuine user navigation. ValidVisit looks at each click arriving via your PropellerAds tracking link and weighs it against 100+ independent data points — where on the network it came from, the device sitting behind it, and the way the visitor actually behaves — then folds all of that into a single 0–100 quality score per click. Real people pass cleanly; automated and low-quality endpoints stand out. Every scored event retains the zone and subzone identifiers from PropellerAds' own tracking tokens, so the output is directly actionable inside the PropellerAds dashboard rather than an opaque aggregate score.
https://yoursite.com/landing?utm_source=propellerads&utm_medium=push&vv_click_id=${SUBID}&vv_campaign_id={campaign_id}&vv_publisher_id={zoneid}&vv_placement_id={subzone_id}&vv_creative_id={bannerid}How invalid traffic shows up on PropellerAds
Push IVT on PropellerAds rarely distributes evenly across a campaign. A single Zone ID will often account for a disproportionate share of total clicks while contributing a much smaller fraction of any meaningful downstream action — a pattern that only becomes visible when you break reporting by zone rather than reading campaign-level averages. The `{zoneid}` token PropellerAds exposes in tracking URLs is the first place to look: zones where click volume and conversion volume move in opposite directions are the clearest sign that something in that zone's subscriber pool has degraded.
Subzone granularity compounds this. The `{subzone_id}` token sits beneath the zone and represents the specific publisher property or widget placement sending traffic within it. A zone that appears clean at the parent level can carry one or two subzones generating the bulk of suspect activity — a pattern that is invisible unless you're capturing and reporting on that second token. Subzone-level concentration of low-scoring clicks is one of the most reliable IVT signals specific to PropellerAds' inventory architecture.
Pop traffic carries a different signature. Sessions from many pop sources behave nothing like a real consumer device once you score them — the device and behavioral picture lines up far better with automation than with a person browsing, and the click quality scores cluster low as a result. The originating sources often trace back to server-farm infrastructure rather than the home and mobile connections genuine visitors come from. Taken together, the 100+ data points behind each score separate scripted pop impression generation from legitimate popunder inventory far more reliably than any single test could on its own.
What to watch on PropellerAds
When a zone delivers a disproportionate share of clicks relative to its share of any downstream conversion or engagement signal, that divergence is the primary indicator of degraded subscriber-pool quality. Filter your ValidVisit report by {zoneid} to surface which zones show this pattern before you draw campaign-level conclusions.
Capturing {subzone_id} alongside {zoneid} reveals whether a zone's IVT problem is structural or confined to one publisher property within it. A single subzone generating a well-above-baseline share of low-scored clicks is the signal to exclude that subzone specifically in PropellerAds — not the entire parent zone.
Pop and popunder placements where the device and behavior of incoming clicks consistently read as automated rather than human, and where the sources trace back to server-farm infrastructure instead of real consumer connections, are a reliable sign of scripted inventory. ValidVisit's per-click quality score concentrates these at the zone level, giving you a basis for a targeted exclusion in PropellerAds rather than a broad category pause.
Push clicks arriving from endpoints that behave nothing like an interactive browser session tend to score low across the 100+ data points ValidVisit weighs — a pattern common in server-side push delivery to non-browser endpoints. A zone where these low-quality clicks pile up relative to its total click count is worth investigating at the subzone level.
How ValidVisit attributes PropellerAds traffic
Each PropellerAds macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | PropellerAds macro | Maps to | Identifies |
|---|---|---|---|
| Subscriber / Click ID (SUBID) | ${SUBID} | click_id | click |
| Campaign ID | {campaign_id} | campaign_id | campaign |
| Zone ID | {zoneid} | publisher_id | publisher |
| Subzone ID | {subzone_id} | placement_id | placement |
| Banner / Creative ID | {bannerid} | creative_id | creative |
- PropellerAds macro
${SUBID}- Maps to
- click_id
- Identifies
- click
- PropellerAds macro
{campaign_id}- Maps to
- campaign_id
- Identifies
- campaign
- PropellerAds macro
{zoneid}- Maps to
- publisher_id
- Identifies
- publisher
- PropellerAds macro
{subzone_id}- Maps to
- placement_id
- Identifies
- placement
- PropellerAds macro
{bannerid}- Maps to
- creative_id
- Identifies
- creative
Pinpoint the bot publishers & placements in PropellerAds
PropellerAdsitself 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 PropellerAds tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — PropellerAds traffic scored 0–100 per sub-source, worst first.
See your own PropellerAds sub-sources scored this way.
Bot / invalid-traffic score broken down by:
- Zone ID
{zoneid}Unique ID of the ad zone (site/source) where the ad is displayed.
Bot / invalid-traffic score broken down by:
- Subzone ID
{subzone_id}Unique ID of the subzone (more granular placement within an ad zone).
Per-click id: PropellerAds passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every click.
Compare bot & invalid-traffic breakdown across every ad network →How the detection works
Data points → one score
Every click 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 click — 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.
PropellerAds traffic quality — FAQ
How do {zoneid} and {subzone_id} work together in ValidVisit reporting for PropellerAds?+
PropellerAds exposes {zoneid} as the top-level inventory unit and {subzone_id} as the publisher property or placement nested within it. Passing both in your PropellerAds tracking link lets ValidVisit attach both dimensions to every scored click event. This matters because zone-level reporting can mask a subzone that is producing a disproportionate share of low-quality traffic — you need both to make a precise exclusion rather than a broad one. The subscriber/click identifier ({SUBID} where available) adds individual-event traceability useful for velocity analysis across repeated clicks from the same endpoint.
PropellerAds already runs its own quality controls. What does ValidVisit add?+
PropellerAds' internal quality controls operate across its full inventory pool with the goal of maintaining network-wide metrics. That is a different measurement objective than evaluating how each individual click performs against your specific campaign — your landing page environment, your target geography, your conversion definition. ValidVisit scores each click against your setup and returns a clear 0–100 quality score tied to the exact zone and subzone that generated it. The output is yours: you decide which sub-sources to exclude in PropellerAds, and the audit trail stays independent of the network's own reporting.
Does ValidVisit work the same way for PropellerAds push and pop formats, or do I need separate configurations?+
The scoring approach is the same — every click is weighed against the same 100+ data points and reduced to one quality score — but the signals that carry the most weight differ by format. For push, where the click came from on the network and how the subscriber endpoint behaves are the most diagnostic. For pop and popunder, the device picture and behavioral signals tend to be more revealing, because pop traffic is more likely to involve scripted, non-human environments. You can run both formats through the same ValidVisit tracking link by passing the format type as an additional sub-ID dimension, which lets you segment scored results by format in reporting.
Detect fraud on other push networks
Catch the fake clicks on PropellerAds.
See which campaigns and publishers send real, converting traffic vs bots — every click scored 0–100.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis