feed / source in Push.HouseValidVisit ranks the bad {feed} (and {site}); disable or down-bid the feed in your Push.House campaign.
Push.House is a self-serve push and onclick network built on subscriber databases and partner feeds. Advertisers choose feeds and can disable or individually bid each one — so the feed and traffic source are the levers you act on. Push.House passes a {site} (traffic source), {feed} (the subscriber feed), {camp} and a {click_id} on every click. ValidVisit captures these the moment the click lands, weighs each one against 100+ independent data points covering the feed it came from, the device behind it and how the visitor behaves, and folds them into a single 0–100 quality score — then reports which sources and feeds are carrying non-human traffic.
https://yoursite.com/landing?utm_source=push-house&utm_medium=push&vv_campaign_id={camp}&vv_publisher_id={site}&vv_placement_id={feed}&vv_click_id={click_id}Push.House quality is set at the feed level: each {feed} is a subscriber database or partner pool, and how it was assembled determines how much of its click volume is genuine. The defining pattern is feed quality — a feed built on incentivised or bot-inflated opt-ins clicks in unnaturally regular bursts aligned to send windows, and that rhythm, paired with how the device and visitor behave, is exactly what pulls a padded feed's score down while a real subscriber sails through.
On the onclick side, automated page-loaders run off hosting and proxy infrastructure, concentrated in specific {site} values. Across both, the same engine sees through the disguise: a click that looks like a browser on the surface but fails to behave like a real one across enough of those 100+ signals scores low. Because {site} and {feed} ride on every click, ValidVisit attributes each finding to the individual source or feed, so you can disable the bad feed while keeping the good ones.
Rank active {feed} values by quality and by the share of clicks scoring in the suspicious or bad tier. Feeds sitting above your baseline are candidates to disable or down-bid (Push.House lets you bid feeds individually).
Where invalid traffic clusters under a single {site}, ValidVisit surfaces it so you can cut that source across every feed it touches.
Suspiciously even click bursts timed to send windows are a signature of bot-inflated feeds; ValidVisit ties the pattern back to the specific {feed} producing it.
Clicks clustered on hosting or proxy infrastructure, combined with weak scores across the device and behaviour signals, point to automation rather than real subscribers within that source.
Each Push.House macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | Push.House macro | Maps to | Identifies |
|---|---|---|---|
| Campaign / Ad ID | {camp} | campaign_id | campaign |
| Traffic Source | {site} | publisher_id | publisher |
| Feed ID | {feed} | placement_id | placement |
| Click ID | {click_id} | click_id | click |
{camp}{site}{feed}{click_id}Push.Houseitself 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 Push.House tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — Push.House traffic scored 0–100 per sub-source, worst first.
See your own Push.House sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{site}Traffic source id — the source you disable/blacklist in the campaign.Bot / invalid-traffic score broken down by:
{feed}The subscriber-feed id (feeds can be disabled or bid individually).Per-click id: Push.House 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 Push.House's macros — {site}, {feed}, {camp} and {click_id} — to your destination URL. ValidVisit reads them as each click arrives and stores a scored verdict per click, segmented by source and feed, with nothing on the click path.
Yes. Because {feed} and {site} ride on every click, ValidVisit ranks your feeds and sources by their quality scores and shows which ones are dragging the average down, then you disable or down-bid the offenders inside your Push.House campaign. ValidVisit reports; you apply the change in the dashboard.
Push.House quality is a function of which subscriber database or feed you buy. Scoring per feed separates pools of genuine, intentional subscribers from those padded with incentivised or bot opt-ins — the distinction a campaign average hides, and the exact lever Push.House hands you.
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