Which RollerAds zones send real traffic?
Not all RollerAds 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 RollerAdsThe buyer pastes the bad zone IDs (or feed IDs for macro-level cuts) into the campaign's zone blacklist field to exclude those placements, or sets an auto-rule to blacklist zones automatically once they spend without converting.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and RollerAds supports OS, browser version, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through RollerAds zones.
RollerAds is a self-serve push and onclick (pop) network with a large subscriber base. It passes a {zoneid} on every click — the traffic zone/source behind it — plus a {feedid} (the subscriber feed), {campaignid} and a {clickid}. RollerAds itself recommends adding the feed id to optimise, and both zone and feed are units you can blacklist or auto-rule in the campaign. ValidVisit reads these tokens once the click lands, then judges the visit against 100+ independent data points — the network it arrived through, the device sitting behind it, and the way the visitor actually behaves — rolling them into one 0–100 quality score so real people clear and bots surface. The result is a per-zone, per-feed read on which units carry non-human traffic.
RollerAds spans push (subscriber-driven) and onclick (forced-view) inventory, and the IVT patterns differ by format but both resolve to the zone/feed. On push, subscriber feeds built from incentivised or bot opt-ins click in unnaturally regular bursts aligned to send windows — that mechanical timing, weighed alongside how the visiting environment behaves, separates them from genuine subscribers and lands on the {feedid}.
On onclick, the ad fires on page entry without a deliberate click, so automated page-loaders can trigger events at scale from hosting providers or proxy networks, concentrated in specific {zoneid} values. Across both formats, when a zone's visits consistently fall to the bottom of the 0–100 score — automation giving itself away across dozens of device and behaviour data points at once — it reads as machines rather than real users. Because {zoneid} and {feedid} ride on every click, ValidVisit attributes all of these to the individual zone or feed.
What to watch on RollerAds
Rank active {zoneid} values by quality and by the share of visits landing in the suspicious/bad tier. Zones above your baseline are blacklist candidates — pair with RollerAds' auto-rules.
RollerAds recommends tracking the {feedid}; ValidVisit scores per feed so a bot-inflated subscriber feed is isolated from a clean one.
OnClick traffic arriving through cloud or proxy infrastructure rarely converts. ValidVisit ties that pattern back to the {zoneid} so you blacklist the offending zones cleanly.
A zone whose visits keep bottoming out across the 0–100 range points to automation — a verdict built from 100+ data points, far harder to fake than a user-agent string.
Pinpoint the bot publishers & placements in RollerAds.
RollerAds 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 RollerAds tokens, not by creative (which says nothing about whether a click was human).
Bought as one RollerAds line, your spend is a single number. Scored per sub-source it runs from 91 down to 24 — the worst is nearly all bots. That’s the leak a blended average hides.
RollerAds 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}The traffic zone / source the click came from — the unit you blacklist in the campaign.
Bot / invalid-traffic score broken down by:
- Feed ID
{feedid}The subscriber-feed id (RollerAds recommends adding it for optimisation).
Per-click id: RollerAds 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 RollerAds sub-sources scored this way.
How ValidVisit attributes RollerAds traffic
Each RollerAds 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=rollerads&utm_medium=push&vv_campaign_id={campaignid}&vv_publisher_id={zoneid}&vv_placement_id={feedid}&vv_click_id={clickId}| Token | RollerAds macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {campaignid} | campaign_id | campaign |
| Zone ID | {zoneid} | publisher_id | publisher |
| Feed ID | {feedid} | placement_id | placement |
| Click ID | {clickId} | click_id | click |
- RollerAds macro
{campaignid}- Maps to
- campaign_id
- Identifies
- campaign
- RollerAds macro
{zoneid}- Maps to
- publisher_id
- Identifies
- publisher
- RollerAds macro
{feedid}- Maps to
- placement_id
- Identifies
- placement
- RollerAds macro
{clickId}- 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 zones on RollerAds.
Scoring and attribution are the means — the point is cutting the RollerAds 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 RollerAds 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 RollerAds 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 RollerAds and put your next dollar behind the traffic that converts.
RollerAds traffic quality, answered.
How do I set up ValidVisit for RollerAds?+
Add ValidVisit's script to your landing page and append RollerAds' macros — {zoneid}, {feedid}, {campaignid} and {clickid} — to your destination URL. The pixel captures them once the visitor arrives and stores a scored verdict per visit, segmented by zone and feed, with nothing on the click path.
Can ValidVisit tell me which RollerAds zones to blacklist?+
Yes. Because {zoneid} (and {feedid}) is on every click, ValidVisit ranks your zones and feeds by quality and by how far each one drags the score down, and you blacklist the offenders — or feed them into RollerAds' auto-rules — in your campaign. ValidVisit reports; you apply the block.
Does ValidVisit handle both push and onclick RollerAds traffic?+
Yes. Push clicks bring subscriber-feed timing into the mix (attributed to {feedid}); onclick clicks lean more on where the traffic came from and how the device behaves (attributed to {zoneid}). Both run through the same weighing of 100+ data points to land on a clear 0–100 quality score.
Detect fraud on other push networks
Find the bots in your RollerAds 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