Push.House traffic,ready for CPA Goal bidding

ClickFlare's Push.House template records the click ID, the click price as cost, and the traffic source, ad, feed and subscriber of each click. Conversions go back to api.push.house by S2S postback with your payout, so CPA Goal optimization and Push.House stats use the conversions you track.

PH
Push.House
Self-serve push advertising network
At a glance
How it connects
Template with click macros + S2S postback
What syncs
Click ID, click price, traffic source, ad, feed
Sync schedule
Real time, per conversion
Key parameters
click_id, price, traffic_source_id, campaign_id, feed
Works with
Web push, in-page push, OnClick (popunder, clickunder)
Good to know
Cashback only counts conversions sent by postback.
Push & pop network
Click price as cost
Payout postback

Run Push.House CPA Goal on conversions you trust

CPA Goal that learns

CPA Goal raises bids on sources that convert and switches off the rest, using the conversions you post back. The template's postback feeds it directly.

Click price on every visit

The template passes {price}. Push.House charges per click on both CPC and CPA Goal, so Not Tracked cost works for either.

Source-level reports

Traffic Source ID shows which sources convert, so you can blacklist or bid up sources in Push.House.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

01
Your ad
Visitor clicks
Ad on Push.House
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to Push.House
Through the Conversion API or postback
05
Cost API
Spend pulled in
Push.House cost matched to each campaign
01
Your ad
Push.House click
Macros fill the tracking URL
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to Push.House
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
Push.House API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
cf_click_id passed to the offer
03
Push.House
Offer or call
The network tracks the action
04
Push.House
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Push.House
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
Push & pop network

Push.House click ID out, payout back

Push.House fills its click ID into click_id and the click price into price. ClickFlare stores the ID as the External ID and records the cost. On conversion, ClickFlare posts the ID back with your payout in Push.House's cost parameter.
  • {external_id} in the postback, never a Push.House macro
  • Postback cost carries your payout
  • Send payout in USD
Today, one campaign
example
Spend pulled from Push.House
cost
$412.30
Conversions recorded
today
38
Sent back to Push.House
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every Push.House click
key macros
click_id, price, traffic_source_id, campaign_id, feed
captured
From the Push.House template in ClickFlare. Use them as report columns and rules.
Revenue for one click
example
Paid click
day 0
$0.00
First revenue pull
+1h
$0.41
Scheduled updates
next days
$0.58
Final pull
last sync
$0.62
Example amounts. Sync timing for Push.House is in the facts above.
Events for one click
example
Lead
day 0
$0.00
Sale
day 0
+$40.00
Upsell
day 1
+$15.00
Refund
day 9
−$15.00
Example events. Each one arrives by postback and is matched to the click.
One visitor's path
example
Product view
step 1
—
Add to cart
step 2
—
Checkout
step 3
—
Purchase
step 4
$68.00
Example order. Each event is tied to the ad that brought the visitor.
6
Macros in the template
$50
Minimum deposit
200+
Countries
2.3B
Events tracked
Setup

Connected in four steps

You need a funded Push.House account, a ClickFlare account with your own tracking domain, and an offer that posts conversions to ClickFlare.
  1. Add the Push.House traffic source In the campaign editor, click + New Traffic Source and pick the Push.House template. It fills click ID, click price and four tracking fields.
  2. Turn on the postback Turn on Traffic source postback URL. There is nothing to replace. Map it to Conversions, or to the custom conversion Push.House should optimize on.
  3. Finish the campaign Set the Cost Model to Not Tracked so ClickFlare uses {price}. Add lander and offer, save, and check the campaign URL contains the click_id parameter.
  4. Create the campaign in Push.House Click Create Campaign, choose vertical and format, and paste the ClickFlare campaign URL into Target Page. Set click cost, targeting and budget, then submit.
Push.House postback URL in the ClickFlare template
https://api.push.house/v1/postback?click_id={external_id}&cost={payout}
app.clickflare.com/integrations
PH
Push.House
Push & pop network
Connected
Push.House account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Push.House template selected
Macros pre-filled
Tracking URL in Push.House
Click ID captured
Conversions reported
Payout included where supported
Push.House connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Push.House added
Offer URL carries the click ID
Postback set in Push.House
Payout and event included
Conversions arriving
Matched to the click
Push.House connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
If the User ID column shows {uid} as text or stays empty, change its TS Token to {pdpid}, Push.House's subscriber ID, and rename the row Subscriber ID.
Push.House postback setup guide
Open the guide
In your reports

What you see once it's connected

  • ROI by traffic source
  • Conversions by ad
  • Revenue by feed
  • Cost per conversion
  • Subscriber breakdown
  • Format splits (with {format})
Use cases

How media buyers run it

Push → lander → offer

Run web push to a lander on CPC, find converting sources in ClickFlare, then switch the campaign to CPA Goal once the postback works.

OnClick → offer

Send OnClick popunder traffic straight to an offer and compare feeds and sources by ROI before raising bids.

Registration then deposit

Track registration and deposit as custom conversions, and send Push.House only deposit so CPA Goal optimizes on paying users.
Frequently asked questions

Questions about Push.House

No items found.
Setup guides
Push.House postback setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Push.House?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a Push.House traffic source template with its click macros, click price cost and an S2S postback to api.push.house."}}, {"@type": "Question", "name": "How do I set up Push.House postback tracking?", "acceptedAnswer": {"@type": "Answer", "text": "Turn on Traffic source postback URL on the Push.House traffic source in ClickFlare. The template's URL needs no edits. Optionally compare it with the one in Push.House's Tracking section."}}, {"@type": "Question", "name": "Why does the postback send my payout in a parameter called cost?", "acceptedAnswer": {"@type": "Answer", "text": "That is Push.House's name for it. In the postback, cost is the conversion's value. Your click cost travels the other way, in the campaign URL's price parameter."}}, {"@type": "Question", "name": "Do I need the postback on plain CPC campaigns?", "acceptedAnswer": {"@type": "Answer", "text": "It is strongly recommended. Push.House's statistics only show conversions you send, and its cashback is only paid on campaigns with an active postback."}}, {"@type": "Question", "name": "Does Push.House pass cost to ClickFlare?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The template passes {price}, the price of the click. Set the Cost Model to Not Tracked. It works for CPC and CPA Goal campaigns."}}, {"@type": "Question", "name": "Why does the Campaign ID column show ad IDs?", "acceptedAnswer": {"@type": "Answer", "text": "The row carries {camp}, which Push.House's own guide describes as the ad ID. Read that column as the ad rather than the campaign."}}]}