Push.House tracking tokens & macros
Push.House sends push-notification clicks through its own subscriber feeds, and the network passes a handful of curly-brace macros into your destination URL when each click fires. Appending the macros below lets ValidVisit attribute every visit to the exact feed / source it came from and judge it Valid or Invalid, with the evidence in your dashboard, so you can see which feeds are sending real interest and which are sending invalid traffic.
Cross-check any macro against the network’s official documentation. Push.House official docs →
Attribution on Push.House hinges on the {click_id} macro, which is required and gives every click a unique id ValidVisit can tie back to its origin. The macros that actually matter for spotting bad inventory are {feed} (the subscriber feed) and {site} (the traffic source), with {camp} rounding out the campaign-level picture. Push.House macros use the lowercase curly-brace format ({feed}, {site}, {click_id}), so paste them verbatim into your tracking URL as standard parameters; there is no funnel hop and no script involved.
Per-feed granularity is what makes this actionable. Once each click is tied to its {feed} (and {site}), ValidVisit ranks which feeds are sending the most invalid traffic / bots and which are valid, and you act on that ranking inside Push.House itself: open the campaign, then disable or down-bid the bad feed. The verdict blocks nothing and ValidVisit never excludes anything in Push.House for you, so the actual exclusion is always something you do manually in your own Push.House dashboard, against the offending feed rather than the network as a whole.
Push.House macro → ValidVisit param
| Token | Push.House macro | ValidVisit param | Example |
|---|---|---|---|
| Ad IDcampaign | {camp} | vv_campaign_id | 33110 |
| Traffic Sourcepublisher | {site} | vv_publisher_id | src_881 |
| Feed IDplacement | {feed} | vv_placement_id | feed_4 |
| Click ID *click | {click_id} | vv_click_id | ck_ph |
- Push.House macro
{camp}- ValidVisit param
vv_campaign_id- Example
- 33110
- Push.House macro
{site}- ValidVisit param
vv_publisher_id- Example
- src_881
- Push.House macro
{feed}- ValidVisit param
vv_placement_id- Example
- feed_4
- Push.House macro
{click_id}- ValidVisit param
vv_click_id- Example
- ck_ph
* required for Push.House attribution.
Ready-to-use Push.House tracking URL
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}Append these params to your landing-page URL — Push.House fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which Push.House sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the Push.House tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What Push.House tokens let you break bots down by
- Traffic Source — Traffic source id — the source you disable/blacklist in the campaign.
- Feed ID — The subscriber-feed id (feeds can be disabled or bid individually).
Carries a per-click id, stored with each visit so a verdict traces back to the click.
- IP exclusiondocumented
- Device targetingdocumented
- OS targetingdocumented
- Browser targetingdocumented
- Connection typedocumented
- Languagedocumented
Tokens last verified against Push.House’s docs on 2026-10-02.
The 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.
Push.House tracking token FAQs
Which token identifies the sub-source I should judge on Push.House?+
Use {feed} as your primary sub-source -- it names the subscriber feed the click came from -- backed up by {site} for the traffic source. ValidVisit ranks quality at this level so you know exactly which feed to disable or down-bid in your campaign.
Is the {click_id} macro really required?+
Yes. {click_id} is the one mandatory macro: it stamps each Push.House click with a unique id so ValidVisit can attribute and judge the resulting visit. Without it, individual clicks can't be tied back reliably to their feed.
Do I need a funnel hop to add these macros?+
No. These are plain URL parameters -- you append {camp}, {site}, {feed} and {click_id} directly to your destination URL in the Push.House campaign setup. No funnel hop, no extra script, nothing else to install.
Tracking tokens for other push networks
Judge every Push.House visit — and find the fake ones.
See which Push.House publishers and placements send real buyers vs. bots.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored