PushPop / Pop-underWhich RichAds zones send real traffic?
Not all RichAds 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.
publisher/site in RichAdsPaste the bad 32-character publisher/site source IDs into the campaign's Black list field, one ID per line with no extra characters, and untick bad sublists in the Sources selector.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and RichAds supports OS, browser, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through RichAds zones.
RichAds operates one of the larger push notification ecosystems, connecting advertisers to subscriber lists assembled by a global publisher network. The channel's mechanics create a specific IVT exposure that search and social don't share: clicks don't originate from a live browsing session but from a push delivery, which means the subscriber relationship — and who built that list — matters more than the referring URL. A publisher that drove bot or incentivized opt-ins to inflate list size will silently absorb budget across every campaign that touches it, because the problem is baked into the list itself rather than a single bad placement.\n\nValidVisit integrates with RichAds by reading the network's native tracking tokens — `[CLICK_ID]`, `[PUBLISHER_ID]`, `[SITE_ID]`, and `[SUB_LIST_ID]` — on each click. After a click arrives, ValidVisit weighs the visit against 100+ independent data points — where it came from, the device behind it, and how the visitor behaves — and folds them into a single 0–100 quality score, so real people pass and bots stand out. Because that score travels with the network's own token values, a low-scoring visit ties straight back to the exact subscriber list and publisher responsible — not just a vague traffic segment. The result is a report layer that tells you precisely which sub-sources to exclude manually in the RichAds campaign dashboard.
Push notification IVT on RichAds tends to enter through the subscriber acquisition layer rather than through click manipulation at delivery time. Because publishers self-report list quality and RichAds pays on a performance or CPM basis, there is economic pressure to grow list sizes quickly — and bot or low-intent opt-ins are the fastest path. Once a degraded subscriber enters a list, every campaign using that list pays for the resulting clicks indefinitely.\n\nWhere push clicks tend to give themselves away is the origin behind the connection. Traffic routed through server-farm infrastructure or residential proxy pools — the kind of relays bad actors lean on to dress up a click as a real consumer device in a premium location — looks different from a genuine subscriber tapping a notification. Those differences are part of what feeds the quality score, so geographic spoofing surfaces even when the declared GEO looks perfectly plausible.\n\nA second pressure point is what happens once the click lands. Push clicks open a page straight from the OS notification layer, and a meaningful share of automated activity never behaves the way a real visitor on a real device would once that page loads. ValidVisit measures how the arrival actually unfolds rather than trusting the click at face value, and when a click that looks active behaves nothing like a human session, that gap is part of what pushes the score toward the high-risk end.\n\nThe granularity that distinguishes RichAds from most other push networks is the `[SUB_LIST_ID]` token. A single publisher may manage several subscriber lists that were built at different times, through different acquisition channels, with very different quality outcomes. ValidVisit maps its scores to the sub-list dimension, so a degraded list can be identified and excluded without penalizing other lists the same publisher operates that may be delivering clean traffic.
What to watch on RichAds
Review score distributions at the publisher level. Publishers where a disproportionate share of visits land in the lowest quality-score bands warrant closer scrutiny — the pattern often reflects a subscriber acquisition method that favored volume over intent. Blacklisting a publisher ID in RichAds campaign settings removes that source from all future delivery.
Watch for Site IDs that deliver a concentration of clicks well above what impression pacing would predict, especially when dwell time and downstream engagement are both near zero. Sudden velocity spikes on a site that previously showed normal cadence are a common signal of automated click activity, not audience behavior.
Push subscriber lists do not stay static — publishers can add opt-ins continuously, and list quality can erode as lower-quality sources are mixed in over time. Track quality scores by `[SUB_LIST_ID]` across rolling periods so you catch degradation in a list that looked acceptable at campaign launch. A list whose scores trend downward over time warrants pausing even if the parent publisher still looks clean overall.
RichAds spans Tier 1 and emerging-market GEOs. When clicks attributed to a publisher claiming premium GEO traffic consistently score low because the connection behind them traces to server-farm or proxy infrastructure rather than a genuine device footprint, that publisher is likely sourcing reach through IP-masking relays. This mismatch appears at the publisher and site level and is worth cross-referencing with the sub-list dimension before excluding.
Pinpoint the bot publishers & placements in RichAds.
RichAds 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 RichAds tokens, not by creative (which says nothing about whether a click was human).
Bought as one RichAds line, your spend is a single number. Scored per sub-source it runs from 89 down to 29 — the worst is nearly all bots. That’s the leak a blended average hides.
RichAds traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Publisher ID
[PUBLISHER_ID]Returns a unique ID of the publisher (a publisher can contain several websites).
Bot / invalid-traffic score broken down by:
- Site ID
[SITE_ID]Returns a unique website ID (a specific site/placement belonging to a publisher).
Per-click id: RichAds 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 RichAds sub-sources scored this way.
How ValidVisit attributes RichAds traffic
Each RichAds 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=richads&utm_medium=push&vv_click_id=[CLICK_ID]&vv_campaign_id=[CAMPAIGN_ID]&vv_campaign_name=[CAMPAIGN_NAME]&vv_creative_id=[CREATIVE_ID]&vv_publisher_id=[PUBLISHER_ID]&vv_placement_id=[SITE_ID]&vv_adset_id=[SUB_LIST_ID]| Token | RichAds macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | [CLICK_ID] | click_id | click |
| Campaign ID | [CAMPAIGN_ID] | campaign_id | campaign |
| Campaign Name | [CAMPAIGN_NAME] | campaign_name | campaign |
| Creative ID | [CREATIVE_ID] | creative_id | creative |
| Publisher ID | [PUBLISHER_ID] | publisher_id | publisher |
| Site ID | [SITE_ID] | placement_id | placement |
| Subscriber List ID (RichPush) | [SUB_LIST_ID] | adset_id | adset |
- RichAds macro
[CLICK_ID]- Maps to
- click_id
- Identifies
- click
- RichAds macro
[CAMPAIGN_ID]- Maps to
- campaign_id
- Identifies
- campaign
- RichAds macro
[CAMPAIGN_NAME]- Maps to
- campaign_name
- Identifies
- campaign
- RichAds macro
[CREATIVE_ID]- Maps to
- creative_id
- Identifies
- creative
- RichAds macro
[PUBLISHER_ID]- Maps to
- publisher_id
- Identifies
- publisher
- RichAds macro
[SITE_ID]- Maps to
- placement_id
- Identifies
- placement
- RichAds macro
[SUB_LIST_ID]- Maps to
- adset_id
- Identifies
- adset
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 publisher/sites on RichAds.
Scoring and attribution are the means — the point is cutting the RichAds 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 RichAds 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 RichAds publisher/site and zone via the network's own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the publisher/sites 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 RichAds and put your next dollar behind the traffic that converts.
RichAds traffic quality, answered.
ValidVisit is analytics — how do I actually cut bad sub-sources from RichAds?+
ValidVisit scores every visit and ties that 0–100 quality score to the contributing token values — `[PUBLISHER_ID]`, `[SITE_ID]`, `[SUB_LIST_ID]` — on each scored event. The exclusion step is manual: you take the publisher or site IDs that ValidVisit surfaces as low-scoring and paste them into the blacklist fields inside your RichAds campaign settings. ValidVisit does not push those exclusions to the network automatically. That manual step is what removes those sub-sources from future delivery — ValidVisit's role is to give you the precise IDs and the evidence to act on.
Does the `[SUB_LIST_ID]` token matter if I'm already filtering at the publisher level?+
Yes, because publisher-level filtering is a blunt instrument on RichAds. A single publisher can operate multiple subscriber lists built through different acquisition channels — some clean, some not — and a publisher-level block discards all of them without distinction. The `[SUB_LIST_ID]` token lets ValidVisit score at the layer below the publisher, so you can remove a specific degraded list while continuing to receive traffic from the same publisher's other lists. For campaigns where scaling clean push volume matters, that granularity is often the difference between a useful exclusion and an over-aggressive one.
How does push notification IVT differ from what ValidVisit sees on pop or banner inventory?+
Push traffic is list-driven rather than placement-driven. On pop or banner formats the click originates from a live browsing context, so what the visitor does on the page once they arrive carries a lot of weight in the score. On push, the click arrives from the OS layer and may involve a device with no active browsing session at all, which shifts the diagnostic weight toward the origin behind the connection — where it came from and whether that path looks like a real consumer or a masking relay — rather than on-page behavior. The 100+ data points feed the same 0–100 score regardless of format, but the high-risk push clicks on RichAds tend to be flagged for infrastructure-level anomalies more often than for anything happening in the browser once the page loads.
Detect fraud on other push networks
Find the bots in your RichAds 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