PlugRush visits,costed and tracked to the subsource

ClickFlare's PlugRush template records the cost of each visit from {$cpv}, the click ID and the subsource, domain, country, OS, browser and creative. Conversions go back to PlugRush by S2S postback with payout and currency, so its Detailed Stats and Automated Rules use your real results.

Start for free

Read the setup guide

PlugRush

Self-serve CPV ad network

At a glance

How it connects

Template with click macros + S2S postback

What syncs

Click ID, CPV cost, subsource, domain, geo, OS, creative

Sync schedule

Real time, per conversion

Key parameters

{$click_id}, {$cpv}, {$source_id}, {$domain_id}, {$cc}, {$os}

Works with

Pops, push ads, native ads, banners on desktop and mobile

Good to know

Replace REPLACE in the postback with your PlugRush user ID.

Push & pop network

CPV cost per visit

Payout postback

Blacklist PlugRush subsources on profit, not visits

Cost recorded on every visit

The template passes {$cpv}. One PlugRush visit is one ClickFlare visit, so with Not Tracked cost, spend lines up with what you bid.

Subsource-level reports

{$source_id} carries the subsource ID, the level PlugRush recommends tracking and the one you blacklist and whitelist on.

Automated Rules that work

PlugRush's Detailed Stats and Automated Rules run on the conversions you send. The postback includes payout, so ROI-based rules have real numbers.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Your ad

Visitor clicks

Ad on PlugRush

ClickFlare

Click recorded

A unique cf_click_id is created

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to PlugRush

Through the Conversion API or postback

Cost API

Spend pulled in

PlugRush cost matched to each campaign

Your ad

PlugRush 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 PlugRush

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

PlugRush 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

PlugRush

Offer or call

The network tracks the action

PlugRush

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

PlugRush

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

How a PlugRush visit turns into a conversion

PlugRush fills click ID, CPV and source macros into your campaign URL. ClickFlare stores the click ID as the External ID and records the cost. On conversion, ClickFlare posts the click ID, payout and payout currency to prprocess.com.

click_id on both sides, different values
Payout and currency sent on every postback
Cost Model: Not Tracked

Today, one campaign

example

Spend pulled from PlugRush

cost

$412.30

Conversions recorded

today

Sent back to PlugRush

per event

38/38

Profit

campaign

$227.70

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

Captured on every PlugRush click

key macros

{$click_id}, {$cpv}, {$source_id}, {$domain_id}, {$cc}, {$os}

captured

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

Macros in the template

2.3B

Events tracked

Setup

Connected in four steps

You need a PlugRush account and your PlugRush user ID, a ClickFlare account with your own tracking domain, and an offer.

Find your PlugRush user ID In PlugRush, open Account → API, or Conversion Tracking from a campaign's Actions icon. Your user ID is the user_id value in the postback URL shown there.
Add the PlugRush traffic source In the campaign editor, click + New Traffic Source and pick the PlugRush template. Turn on Traffic source postback URL, replace REPLACE with your user ID, and map it to your final event.
Finish the campaign Set the Cost Model to Not Tracked so ClickFlare uses {$cpv}. Add your lander and offer, save, and copy the campaign URL from your own tracking domain.
Create the campaign in PlugRush Pick the campaign type, set targeting, CPV bid and budget, and paste the ClickFlare campaign URL. For push, native and banners, assign your creatives.

PlugRush postback URL with your user ID

https://prprocess.com/conversion/?user_id=YOUR_USER_ID&click_id={external_id}&currency={payout_currency}&payout={payout}

app.clickflare.com/integrations

PlugRush

Push & pop network

Connected

PlugRush account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

PlugRush template selected

Macros pre-filled

Tracking URL in PlugRush

Click ID captured

Conversions reported

Payout included where supported

PlugRush connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

PlugRush added

Offer URL carries the click ID

Postback set in PlugRush

Payout and event included

Conversions arriving

Matched to the click

PlugRush connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Ready to track

Prefer not to share payouts? Send a fixed value such as payout=1. Conversions still count, but PlugRush revenue, ROI and rules based on them become meaningless.

PlugRush postback setup guide

Open the guide

In your reports

What you see once it's connected

ROI by subsource
Conversions by domain ID
Cost per visit by country
OS and browser splits
Creative performance
Site orientation breakdown

Use cases

How media buyers run it

Pop → offer

Run PlugRush pops straight to an offer, sort subsources by profit in ClickFlare, and paste the losers into a PlugRush blacklist with Import Entries.

Push → lander → offer

Test several push creatives, compare them by {$creative_id} in ClickFlare, and keep the ones that convert after cost.

Rule-driven optimization

Send payout on every sale so PlugRush's Automated Rules can pause or adjust campaigns on revenue and ROI, not just visits.

Frequently asked questions

Questions about PlugRush

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

PropellerAds

Self-serve pop and push ad network

Push & pop network

Browse all integrations ->

Setup guides

PlugRush postback setup guide

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with PlugRush?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a PlugRush traffic source template with its click macros, CPV cost and an S2S postback to prprocess.com."}}, {"@type": "Question", "name": "How do I set up PlugRush postback tracking?", "acceptedAnswer": {"@type": "Answer", "text": "Turn on Traffic source postback URL on the PlugRush traffic source in ClickFlare and replace REPLACE with your PlugRush user ID, found under Account → API."}}, {"@type": "Question", "name": "Does PlugRush pass cost to ClickFlare?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The template passes {$cpv}, PlugRush's cost per visitor. Set the Cost Model to Not Tracked. If {$cpv} arrives empty, use CPC with your CPV bid."}}, {"@type": "Question", "name": "Why does the template call the subsource Unique ID?", "acceptedAnswer": {"@type": "Answer", "text": "It is a naming quirk. The row carries {$source_id}, PlugRush's subsource ID. Rename the row to Subsource if you like. The parameter and token stay the same."}}, {"@type": "Question", "name": "Why does the Domain column show numbers?", "acceptedAnswer": {"@type": "Answer", "text": "{$domain_id} passes PlugRush's ID for the publisher domain, not the domain name. Values that look like codes are expected."}}, {"@type": "Question", "name": "Is PlugRush's conversion data used against me in bidding?", "acceptedAnswer": {"@type": "Answer", "text": "PlugRush says it has never used conversion data to raise what advertisers pay. If you are wary, send a fixed payout in the postback."}}]}

PlugRush visits,costed and tracked to the subsource

Blacklist PlugRush subsources on profit, not visits

Cost recorded on every visit

Subsource-level reports

Automated Rules that work

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

How a PlugRush visit turns into a conversion

Connected in four steps

What you see once it's connected

How media buyers run it

Pop → offer

Push → lander → offer

Rule-driven optimization

Questions about PlugRush

Related integrations

Your PlugRush campaigns, tracked to the subsource.