PushWhich Push.House zones send bot traffic?
Judge every Push.House push and onclick visit by traffic source and feed. Disable the feeds sending invalid traffic — you make the call.
site ID in Push.HouseThe buyer pastes bad site IDs one per line into a BLACK LIST audience and attaches it to the campaign; a whole feed is cut with the switch next to its name in Traffic Settings.
How bot traffic slips in through Push.House zones.
Push.House is an advertising network selling push notification, in-page push, OnClick, banner and DirectClick traffic, mainstream and adult, on CPC bids, with CPA Goal and CPM in beta. Supply comes from its own subscription bases plus partner feeds you switch on or off, and the site ID is the source you blacklist or bid separately. Push.House passes {site} (the traffic source ID), {feed}, {camp} (the ad ID) and {click_id}. ValidVisit captures them and judges every visit Valid or Invalid with its evidence, so each source and feed gets its own invalid share.
Push.House quality is set by source and by feed. Each {feed} is a partner subscription base, and Push.House recommends starting on its internal bases and connecting feeds only to scale, since a new feed adds volume with no guarantee of results. On OnClick, the offer opens in a new tab through a script on the publisher’s page when the user clicks or scrolls, so the format does nothing to filter automated page loads, and those concentrate in particular {site} values.
Because {site} and {feed} ride on every click, ValidVisit attributes each visit’s verdict to its source and feed, so you can disable one bad feed or blacklist one site while keeping the rest.
What to watch on Push.House
{feed}) invalid shareRank active feeds by invalid share. A feed well above your baseline is a candidate to switch off in Traffic Settings, or to down-bid with an automated rule on that feed.
{site}) invalid shareRank site IDs by invalid share. The worst go into an ID-type Black List. Where a site is mostly valid but poor value, Prices by Platforms (micro-bidding) lowers its bid instead of cutting it.
Under CPA Goal, zones without conversions are blocked once they reach the test limit. Check the invalid share of what it blocks: mostly invalid confirms the block, mostly valid points at the offer or landing page rather than the traffic.
What Push.House lets you judge by.
Invalid share broken down by:
- Traffic Source
{site}Traffic source id — the source you disable/blacklist in the campaign.
Invalid share 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, and ValidVisit stores it with each visit, so a verdict traces back to the click in Push.House’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own Push.House sub-sources judged this way.
How ValidVisit attributes Push.House traffic
Each Push.House macro maps to a normalized parameter, so every judged visit 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 |
|---|---|---|---|
| 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
Macros checked against Push.House’s own documentation on 2026-10-02. Push.House docs
The verdict works the same way on every network. ValidVisit never changes your Push.House account: you make the exclusion there yourself. How the verdict works →
Push.House traffic quality, answered.
How do I disable a feed or block a site in Push.House?
Feeds: in the campaign’s Traffic Settings, each feed has a switch next to its name that disables it for that campaign. Sites: in the Audiences section, create a list with ID type BLACK LIST, add the bad site IDs one per line, and attach that audience in the campaign’s Audience field when creating or editing it.
Can I block IP ranges in Push.House?
Yes. An IP-type Audiences list takes ranges written like 64.233.0.0-64.233.255.255, one per line, and is attached to the campaign the same way as a site blacklist.
Can Push.House act on sources and feeds automatically?
Yes. Automated rules watch a campaign, a source or a feed on metrics such as clicks, leads, spend, CR, CTR or ROI over 30 minutes to 7 days, then change the bid, disable the feed or add the source to a black or white list. Rules act on performance; the verdict shows whether a source with no leads was sending invalid visits or real visitors who did not convert.
Which Push.House macros should I use?
{click_id} for conversions, {site} and {feed} for the source and feed you act on, and {camp} for the ad. {pdpid} is the subscription ID used for retargeting. In ad titles and descriptions, macros must be uppercase, such as {CITY}; that rule is for creative text, not your landing page URL.
Detect fraud on other push networks
Pushground
RichAds
RollerAds
Adsterra
Bidvertiser
PlugRushWeighing a blocker for push traffic? How ValidVisit compares to PureGuard, Adscore and Tracker bot filtering.
Find the bots in your Push.House spend.
See which publishers and placements send real buyers vs bots — every visit judged Valid or Invalid, worst first.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored