PushWhich Push.House zones send bots and invalid traffic?
Not all Push.House 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.
site ID in Push.HouseThe buyer pastes bad site IDs one per line into a BLACK LIST audience in the Audiences section and attaches that audience to the campaign; coarser bad-feed cleanup is done by flipping the switch next to a feed’s name in campaign settings.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and Push.House supports OS version, browser, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through Push.House zones.
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 visit 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.
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.
What to watch on Push.House
{feed}) IVT distributionRank active {feed} values by quality and by the share of visits scoring in the suspect or invalid tier. Feeds sitting above your baseline are candidates to disable or down-bid (Push.House lets you bid feeds individually).
{site}) concentrationWhere invalid traffic clusters under a single {site}, ValidVisit surfaces it so you can cut that source across every feed it touches.
Unnaturally 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.
Pinpoint the bot publishers & placements in Push.House.
Push.House 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 Push.House tokens, not by creative (which says nothing about whether a click was human).
Bought as one Push.House line, a buy reads as a single number. Scored per sub-source, a spread like this illustration runs from 87 down to 21 — the worst is nearly all bots. That’s the leak a blended average hides.
Illustrative: Push.House traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Traffic Source
{site}Traffic source id — the source you disable/blacklist in the campaign.
Bot / invalid-traffic score broken down by:
- Feed ID
{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 visit.
Compare bot & invalid-traffic breakdown across every ad network →See your own Push.House sub-sources scored this way.
How ValidVisit attributes Push.House traffic
Each Push.House 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=push-house&utm_medium=push&vv_campaign_id={camp}&vv_publisher_id={site}&vv_placement_id={feed}&vv_click_id={click_id}| 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 |
- Push.House macro
{camp}- Maps to
- campaign_id
- Identifies
- campaign
- Push.House macro
{site}- Maps to
- publisher_id
- Identifies
- publisher
- Push.House macro
{feed}- Maps to
- placement_id
- Identifies
- placement
- Push.House 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 site IDs on Push.House.
Scoring and attribution are the means — the point is cutting the Push.House 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 Push.House 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 Push.House site ID and zone via the network’s own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the site IDs 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 Push.House and put your next dollar behind the traffic that converts.
Push.House traffic quality, answered.
What’s needed to wire ValidVisit into a Push.House campaign?
ValidVisit’s script on your landing page, and Push.House’s macros — {site}, {feed}, {camp} and {click_id} — carried through your destination URL. The pixel reads them the moment a click lands and files a scored verdict against the source and feed it came from. Nothing runs on the click itself; the scoring happens once the visitor has already arrived.
How do I know which Push.House feeds are worth disabling?
{feed} and {site} are both attached to every click, so ValidVisit ranks them by quality and shows what’s dragging the average down. You take the worst performers and disable or down-bid them inside your Push.House campaign — ValidVisit reports the finding, the change happens in your own dashboard.
Why does the feed matter more than the traffic source here?
Because that’s the lever Push.House actually gives you — each {feed} is a distinct subscriber pool with its own acquisition history, and quality varies by pool far more than by anything else. Scoring at that level separates feeds built on genuine, intentional subscribers from ones padded with incentivised or bot opt-ins, a distinction a blended campaign average would otherwise hide.
Detect fraud on other push networks
AdOperator
AdsCompass
Adsterra
DAO.ADFind the bots in your Push.House 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