site in DatsPushValidVisit flags the bad {SITE_ID}; add it to your DatsPush campaign blacklist.
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 it 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.
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}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-click 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.
Rank active {SITE_ID} values by quality and by the share of clicks 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 clicks 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.
Each DatsPush macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| 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 |
{CAMPAIGN_ID}{SITE_ID}{CLICK_ID}DatsPushitself 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).
Illustrative example — DatsPush traffic scored 0–100 per sub-source, worst first.
See your own DatsPush sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{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 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 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 click, segmented by site, with nothing on the click path.
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.
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}.
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