Pushground sites and sources,scaled on what converts

ClickFlare reads Pushground's click ID, CPC bid and 9 macros, including site, sub-source and subscriber freshness, from the campaign URL. Each conversion goes back to lupush.com by S2S postback with the payout in amount, so Pushground's stats and optimization match yours.

Start for free

Read the setup guide

Pushground

Self-serve push and pop ad network

At a glance

How it connects

Traffic source template + S2S postback

What syncs

Click ID, CPC bid, site, source, creative, city, user age

Sync schedule

Real time, per conversion

Key parameters

{bid}, {site_id}, {source}, {creativity_id}, {userAge}

Works with

Push notifications, in-page push, pops

Good to know

Pushground answers 200 OK to every postback, matched or not

Push & pop network

Postback with payout

9 macros captured

Blacklist and bid up Pushground placements on data

Site and sub-source detail

site_id and source are Pushground's sub-source 2 and 3. Group by them to see which placements convert, then blacklist or bid up in Pushground.

Subscriber freshness on push

{userAge} shows how recently the push subscriber was acquired. Fresh subscribers often click and convert differently from old ones.

Ready to use as shipped

The template postback already holds {external_id} and {payout}, with no account ID to fill in. Pushground matches on the click ID alone.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Your ad

Visitor clicks

Ad on Pushground

ClickFlare

Click recorded

A unique cf_click_id is created

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to Pushground

Through the Conversion API or postback

Cost API

Spend pulled in

Pushground cost matched to each campaign

Your ad

Pushground click

Macros fill the tracking URL

ClickFlare

Click recorded

Zone, site and device data stored

Offer or lander

Visitor converts

On your page or the offer

ClickFlare

Conversion logged

With payout and event type

Postback

Reported to Pushground

So its optimization sees the result

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

Your article

Keyword block

Click ID passed to the feed

Results page

Paid click

Conversion fired to ClickFlare

Pushground API

Revenue matched

Pulled on a schedule and reconciled

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

cf_click_id passed to the offer

Pushground

Offer or call

The network tracks the action

Pushground

Conversion

Lead, sale, call or rebill

Postback

Payout in ClickFlare

Matched to the original click

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

Pushground

Store or funnel

Click ID kept through checkout

Events

View, cart, checkout

Each step tracked

ClickFlare

Purchase recorded

Order value matched to the ad

Push & pop network

Click ID in, click_id and amount back out

Pushground fills its click ID in ClickFlare's click_id parameter. ClickFlare stores it as the External ID and, on conversion, calls lupush.com/conversion with that ID and the payout in amount.

Every postback counts as one conversion
A 200 response doesn't prove a match
{deviceName}, {userAge} keep their capital letters

Today, one campaign

example

Spend pulled from Pushground

cost

$412.30

Conversions recorded

today

Sent back to Pushground

per event

38/38

Profit

campaign

$227.70

Example numbers. Cost and conversions sit in the same report row.

Captured on every Pushground click

key macros

{bid}, {site_id}, {source}, {creativity_id}, {userAge}

captured

From the Pushground 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 Pushground 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.

Tracking macros captured

Ad formats supported

2.3B

Events tracked

Setup

Connected in four steps

You need a Pushground account, a ClickFlare offer that posts conversions back, and your own tracking domain.

Create the Pushground traffic source In a new campaign, click + New Traffic Source and pick the Pushground template. It fills the click ID, {bid} as cost and 9 tracking macros.
Turn on the postback Turn on Traffic source postback URL. It already sends {external_id} and {payout}, with nothing to replace. Map it to the step Pushground should optimize on.
Launch in Pushground Set Cost Model to Not Tracked and paste the campaign URL into Pushground's tracking URL field. Confirm the postback shown is lupush.com/conversion with click_id and amount.
Test with a fake click ID Open the campaign URL with click_id=test123, convert, and check Logs → Postback Status for the lupush.com request. Then watch Pushground's stats for the first real conversion.

Pushground postback URL in the ClickFlare template

https://lupush.com/conversion?click_id={external_id}&amount={payout}

app.clickflare.com/integrations

Pushground

Push & pop network

Connected

Pushground account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

Pushground template selected

Macros pre-filled

Tracking URL in Pushground

Click ID captured

Conversions reported

Payout included where supported

Pushground connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

Pushground added

Offer URL carries the click ID

Postback set in Pushground

Payout and event included

Conversions arriving

Matched to the click

Pushground connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Ready to track

{bid} is your CPC bid, not the CPM price. On CPM campaigns, switch the Cost Model to CPC and enter your CPM bid divided by 1,000, or spend divided by clicks for push.

Pushground postback setup guide

Open the guide

In your reports

What you see once it's connected

ROI by site ID
Conversions by sub-source
Results by subscriber freshness
EPC by creative
Country and city breakdowns
Results by device name
Browser language results

Use cases

How media buyers run it

Pushground push → lander → offer

Push to lander to offer

Group by user age and bid more on the subscriber freshness that converts.

Pushground pop → offer

Pops on CPM

A pop impression is roughly one visit, so set CPC to your CPM bid divided by 1,000 and cut losing sites.

In-page push → offer

In-page push by publisher

Add {supply_id} as an extra parameter to see which publishers convert, alongside site and source.

Frequently asked questions

Questions about Pushground

No items found.

Related integrations

More templates that plug into the same ClickFlare account.

AdOperator

Self-serve popunder and push network

Push & pop network

BidVertiser

Self-serve pop, push and native network

Push & pop network

EvaDav

Self-serve push and popunder network

Push & pop network

Galaksion

Self-serve push, pop and native network

Push & pop network

Noviclick

Self-serve pop and push network

Push & pop network

PlugRush

Self-serve CPV ad network

Push & pop network

Browse all integrations ->

Setup guides

Pushground postback setup guide

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Pushground?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare's Pushground template captures the click ID, CPC bid and 9 macros, and its S2S postback sends conversions with payout to lupush.com."}}, {"@type": "Question", "name": "Do I need an account ID or password in the Pushground postback?", "acceptedAnswer": {"@type": "Answer", "text": "No. Pushground matches the conversion on the click ID alone. The template's postback works as it is."}}, {"@type": "Question", "name": "Why does Pushground show no conversion after a 200 response?", "acceptedAnswer": {"@type": "Answer", "text": "Pushground returns 200 OK to every postback, even when it can't process it. Check the conversion in Pushground's stats too."}}, {"@type": "Question", "name": "What does the user age column show?", "acceptedAnswer": {"@type": "Answer", "text": "The freshness of the push subscriber, not the visitor's age. Use it to compare new and old subscribers and bid on the segments that convert."}}, {"@type": "Question", "name": "Should I use Pushground's pixel?", "acceptedAnswer": {"@type": "Answer", "text": "Use the S2S postback for conversions. It fires from ClickFlare's server and doesn't depend on the visitor's browser. The pixel is separate."}}, {"@type": "Question", "name": "How is Pushground cost tracked?", "acceptedAnswer": {"@type": "Answer", "text": "The template passes {bid}, your CPC bid, so set Cost Model to Not Tracked. If Pushground charges less than your bid, ClickFlare's cost runs slightly high."}}]}

Pushground sites and sources,scaled on what converts

Blacklist and bid up Pushground placements on data

Site and sub-source detail

Subscriber freshness on push

Ready to use as shipped

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Click ID in, click_id and amount back out

Connected in four steps

What you see once it's connected

How media buyers run it

Push to lander to offer

Pops on CPM

In-page push by publisher

Questions about Pushground

Related integrations

Your Pushground traffic, tracked to the payout.