Black Friday came early.Early-access pricesuntil Nov 8.Black Friday: early-access prices until Nov 8.Early-access price ends in0d00h00m00sClaim the deal
ClickFlare's TrafficForce template captures the click ID plus site, channel, campaign, ad group, ad, keyword, country and language macros on every click. When a conversion lands, ClickFlare posts the click ID back to TrafficForce, so its stats and auto-optimization use your real conversions.
Postback takes only the click ID. Set payout in TrafficForce.
Display & pop network
S2S postback
11 macros captured
Find the TrafficForce sites and channels that pay
Placement-level decisions
site_id and channel_id land in their own columns, so you can see which sites and placements convert and exclude or bid up channels in TrafficForce.
Auto-optimization on real data
Conversions reach TrafficForce through the S2S postback. Once they arrive reliably, its auto-optimization favors the ad with the most conversions, not the best CTR.
Readable reports
The template also captures site_name and channel_name, so placement reports make sense without looking IDs up in TrafficForce.
How it works
From ad click to profit per campaignattributed revenueattributed salesa matched conversion
01
Your ad
Visitor clicks
Ad on TrafficForce
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 TrafficForce
Through the Conversion API or postback
05
Cost API
Spend pulled in
TrafficForce cost matched to each campaign
01
Your ad
TrafficForce 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 TrafficForce
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
TrafficForce 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
TrafficForce
Offer or call
The network tracks the action
04
TrafficForce
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
TrafficForce
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
Display & pop network
How the TrafficForce click ID makes the round trip
TrafficForce fills {CLICK_ID} into cid when the ad is clicked. ClickFlare stores it as the External ID. When the offer converts, ClickFlare fires the TrafficForce postback with that ID, and TrafficForce updates its conversion and ROI stats.
cid={CLICK_ID} in the campaign URL, upper case
click_id={external_id} in the postback
Conversion settings live on each ad group
Today, one campaign
example
Spend pulled from TrafficForce
cost
$412.30
Conversions recorded
today
38
Sent back to TrafficForce
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
From the TrafficForce 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 TrafficForce 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.
11
Macros in the template
10
Tracking fields left free
2.3B
Events tracked
Setup
Connected in four steps
You need a TrafficForce account, a ClickFlare account with your own tracking domain, and an offer that posts conversions to ClickFlare.
Add the TrafficForce traffic source In the campaign editor, open Traffic Source, click + New Traffic Source and pick the TrafficForce template. It fills in the click ID and ten tracking fields.
Turn on the postback Under Passing conversion info to traffic source, turn on Traffic source postback URL. It has no placeholders. Map it to Conversions or to the custom conversion TrafficForce should learn from.
Finish the campaign with CPC cost Set the Cost Model to CPC, since the template passes no cost. Add your lander and offer, save, and copy the campaign URL from your own tracking domain.
Enable conversion tracking in TrafficForce Paste the campaign URL as the ad's click URL. In the ad group, turn on Enable Conversion Tracking and fill in Action Name, Earnings per conversion and Tracking Period.
TrafficForce postback URL in the ClickFlare template
TrafficForce sells mostly on CPM. Enter your CPM bid divided by 1,000 as the CPC value for popunders. For banners and native, divide spend by clicks and update it as CTR changes.
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with TrafficForce?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a TrafficForce traffic source template with its click macros and an S2S postback to delivery.trafficforce.com/conv.php."}}, {"@type": "Question", "name": "How do I set up TrafficForce postback tracking?", "acceptedAnswer": {"@type": "Answer", "text": "Turn on Traffic source postback URL on the TrafficForce traffic source in ClickFlare. Then turn on Enable Conversion Tracking in the TrafficForce ad group settings and paste the ClickFlare campaign URL as the click URL."}}, {"@type": "Question", "name": "Why is it cid in the campaign URL and click_id in the postback?", "acceptedAnswer": {"@type": "Answer", "text": "Both carry the same value. ClickFlare reads TrafficForce's click ID from cid, and TrafficForce expects it back in click_id. Change neither."}}, {"@type": "Question", "name": "Can ClickFlare send the payout to TrafficForce?", "acceptedAnswer": {"@type": "Answer", "text": "No. TrafficForce's conversion URL only accepts the click ID. Enter your average payout as Earnings per conversion in the TrafficForce ad group."}}, {"@type": "Question", "name": "Does TrafficForce pass cost to ClickFlare?", "acceptedAnswer": {"@type": "Answer", "text": "No. The template has no cost row. Use the CPC cost model with a cost per visit, and correct spend with a manual cost upload if it drifts."}}, {"@type": "Question", "name": "Do I need TrafficForce's conversion pixel too?", "acceptedAnswer": {"@type": "Answer", "text": "No. The pixel and the S2S postback do the same job. The postback fires from ClickFlare's server and doesn't depend on cookies in the visitor's browser."}}]}
Your TrafficForce traffic, tracked to the placement.
Site, channel and ad data on every click, conversions sent back by click ID. Free 14-day trial and free migration from any tracker.