zone in RollerAdsValidVisit ranks the bad zoneid (and feed); blacklist them in RollerAds or feed them into an auto-rule.
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 it 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.
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}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 clicks 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.
Rank active {zoneid} values by quality and by the share of clicks 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 clicks 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.
Each RollerAds macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| 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 |
{campaignid}{zoneid}{feedid}{clickId}RollerAdsitself 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).
Illustrative example — RollerAds traffic scored 0–100 per sub-source, worst first.
See your own RollerAds sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{zoneid}The traffic zone / source the click came from — the unit you blacklist in the campaign.Bot / invalid-traffic score broken down by:
{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 click.
Compare bot & invalid-traffic breakdown across every ad network →Every click is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
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.
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.
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
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 click, segmented by zone and feed, with nothing on the click path.
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.
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.
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