Which DatsPush zones send real traffic?
Not all DatsPush 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.
Platform merged: DatsPush was folded into Mondiad — its site now points there and campaigns run on the Mondiad platform. See Mondiad →
zone/subid in DatsPushThe buyer pastes the bad ZoneIDs/SubIDs into the campaign's blacklist (or saves them as a reusable Audience and attaches it to the campaign in Blacklist mode) so those sub-sources stop receiving the ads.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and DatsPush 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 DatsPush zones.
DatsPush is a self-serve push and onclick network with a broad subscriber and publisher base. It exposes a {SITE_ID} (the site/source a click came from), {CAMPAIGN_ID} and a {CLICK_ID} on every click — and the site is the unit you blacklist in the campaign. ValidVisit reads these macros as each click lands, then measures the visit against more than 100 independent data points — where the traffic originated, the device on the other end and the way the visitor actually behaves — and folds them into one 0–100 quality score. Real people clear that bar and bots don't, so ValidVisit can tell you which sites carry non-human traffic and you act on the exact sources rather than the campaign average.
DatsPush spans push (subscriber-driven) and onclick (forced-view) inventory, and both resolve to the {SITE_ID}. On push, sites built from incentivised or bot opt-ins click in unnaturally regular bursts aligned to send windows — a rhythm that looks nothing like the staggered, human pattern ValidVisit's scoring expects from real subscribers.
On onclick, automated page-loaders fire from server-farm and proxy infrastructure, concentrated in specific {SITE_ID} values. In both cases ValidVisit's per-visit score collapses for those sites because the origin, the device and the behaviour all point to automation instead of a curious human. Since {SITE_ID} rides on every click, ValidVisit attributes the whole pattern to the individual site, so one bad source stays separable from a clean campaign.
What to watch on DatsPush
Rank active {SITE_ID} values by quality and by the share of visits landing in the low-score, likely-invalid tier. Sites above your baseline are blacklist candidates.
Unnaturally even click bursts aligned to notification schedules point to bot-inflated subscriber sites; ValidVisit's scoring surfaces where that pattern concentrates.
OnClick clicks arriving from cloud server farms or proxy infrastructure rarely convert. ValidVisit ties each of those origin patterns back to the {SITE_ID} so you blacklist the offending sources cleanly.
A spike in visits scoring at the bottom of the 0–100 range within a single site signals automation rather than real visitors — the kind of signal that doesn't fall for a swapped user-agent string.
Pinpoint the bot publishers & placements in DatsPush.
DatsPush 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 DatsPush tokens, not by creative (which says nothing about whether a click was human).
Bought as one DatsPush line, your spend is a single number. Scored per sub-source it runs from 92 down to 23 — the worst is nearly all bots. That’s the leak a blended average hides.
DatsPush traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Site ID
{SITE_ID}The site / source the click came from — the unit you blacklist in the campaign.
Per-click id: DatsPush 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 DatsPush sub-sources scored this way.
How ValidVisit attributes DatsPush traffic
Each DatsPush 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=datspush&utm_medium=push&vv_campaign_id={CAMPAIGN_ID}&vv_publisher_id={SITE_ID}&vv_click_id={CLICK_ID}| Token | DatsPush macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {CAMPAIGN_ID} | campaign_id | campaign |
| Site ID | {SITE_ID} | publisher_id | publisher |
| Click ID | {CLICK_ID} | click_id | click |
- DatsPush macro
{CAMPAIGN_ID}- Maps to
- campaign_id
- Identifies
- campaign
- DatsPush macro
{SITE_ID}- Maps to
- publisher_id
- Identifies
- publisher
- DatsPush 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 zone/subids on DatsPush.
Scoring and attribution are the means — the point is cutting the DatsPush 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 DatsPush 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 DatsPush zone/subid and zone via the network's own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the zone/subids 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 DatsPush and put your next dollar behind the traffic that converts.
DatsPush traffic quality, answered.
How do I set up ValidVisit for DatsPush?+
Add ValidVisit's script to your landing page and append DatsPush's macros — {SITE_ID}, {CAMPAIGN_ID} and {CLICK_ID} — to your destination URL. ValidVisit captures them as the click arrives and stores a scored verdict per visit, segmented by site, with nothing on the click path.
Can ValidVisit tell me which DatsPush sites to blacklist?+
Yes. Because {SITE_ID} is on every click, ValidVisit ranks your sites by their 0–100 quality scores and by what is dragging the weak ones down, and you blacklist the offenders in your DatsPush campaign. ValidVisit reports the evidence; the block is applied in your account.
Does ValidVisit cover both push and onclick DatsPush traffic?+
Yes. Push clicks lean more on subscriber-timing patterns; onclick clicks lean more on where the traffic comes from and how the device behaves. Both run through the same 100+ data points and resolve to a transparent 0–100 score attributed to the {SITE_ID}.
Detect fraud on other push networks
Find the bots in your DatsPush 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