System1 RSOC revenue,estimated down to the click

ClickFlare connects to System1 with your Auth Key and pulls RSOC conversions and revenue by API. Impression, search and click postbacks ride inside the offer URL. Click-level revenue is an estimate built from System1's segment, subid, geo and device data.

S1
System1
RSOC search feed
At a glance
How it connects
System1 Auth Key + postbacks in the offer URL
What syncs
Impressions, searches, clicks and revenue
Sync schedule
Depends on your ClickFlare subscription plan
Key parameters
nonrevsubid, subid, segment, headline, forceKeyA
Works with
Desktop and mobile RSOC, Facebook traffic
Good to know
Click-level revenue is an estimate. System1 reports in PST.
RSOC feed
Auth Key API
Desktop and mobile

System1 data, tied to the click that earned it

Same-day revenue

Send the ClickFlare campaign ID in subid and revenue shows the same day. Leave it out and System1 revenue only appears from the next day.

Searches and clicks as events

Impression, search and click postbacks fire from the offer URL, so you see how many visitors searched and clicked, along with what they earned.

A template for mobile

System1 Mobile has its own template with s1p parameters for campaign, ad group and ad, and sends the keyword back with search and click events.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

01
Your ad
Visitor clicks
Ad on System1
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 System1
Through the Conversion API or postback
05
Cost API
Spend pulled in
System1 cost matched to each campaign
01
Your ad
System1 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 System1
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
System1 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
System1
Offer or call
The network tracks the action
04
System1
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
System1
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
RSOC feed

Postbacks inside the offer URL, revenue by API

System1 takes your postbacks as URL-encoded parameters in the offer URL. Each event fires to ClickFlare with the click ID from nonrevsubid, and the API pulls revenue by segment, subid, geo and device.
  • nonrevsubid={cf_click_id} on every offer
  • Encode only the part after the equal sign
  • Segment name goes in param10 on clicks
Today, one campaign
example
Spend pulled from System1
cost
$412.30
Conversions recorded
today
38
Sent back to System1
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every System1 click
key macros
nonrevsubid, subid, segment, headline, forceKeyA
captured
From the System1 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 System1 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
Minimum forceKey terms
2.3B
Events tracked
Setup

Connected in four steps

You need an active System1 account, a System1 Auth Key from your account manager, and a ClickFlare account.
  1. Get your System1 Auth Key Ask your System1 account manager for the Authorization Key. ClickFlare uses it to pull conversions and revenue through the API.
  2. Add the System1 integration Open Integrations, click Add Integration under RSOC and pick the System1 or System1 Mobile template. Click + Connect Account, enter the account name and auth key, choose the custom conversion and save.
  3. Build the offer URL Add nonrevsubid={cf_click_id} and the ClickFlare campaign ID in subid (s1paid={campaign_id} on mobile). Add segment, headline and at least six forceKey terms.
  4. Encode and append the postbacks Add impression_track_url, search_track_url and click_track_url to the offer URL. URL-encode each postback after the equal sign and pass the segment name in param10 on the click postback.
Click postback to encode into click_track_url
https://your_tracking_domain/cf/cv?click_id={cf_click_id}&param10=SEGMENT_NAME&ct=click
app.clickflare.com/integrations
S1
System1
RSOC feed
Connected
System1 account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
System1 template selected
Macros pre-filled
Tracking URL in System1
Click ID captured
Conversions reported
Payout included where supported
System1 connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
System1 added
Offer URL carries the click ID
Postback set in System1
Payout and event included
Conversions arriving
Matched to the click
System1 connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
Without {cf_click_id} in nonrevsubid, postbacks don't fire and ClickFlare pulls no System1 revenue. A postback that isn't encoded correctly breaks too.
System1 RSOC setup guide
Open the guide
In your reports

What you see once it's connected

  • Impressions, searches and clicks
  • Revenue by segment
  • Revenue per campaign
  • Keywords on mobile traffic
  • Geo and device breakdowns
  • ROI by traffic source
Use cases

How media buyers run it

Facebook → System1 article

Facebook to System1 RSOC

Send network=facebook and the ClickFlare campaign ID in subid to get same-day revenue per campaign.
Facebook mobile → System1 Mobile article

Mobile-first campaigns

Pass campaign, ad group and ad IDs in s1pcid, s1pagid and s1padid to break revenue down by ad.

Comparing segments

Run each buyside account as its own System1 segment and send the segment name in param10 to compare revenue across them.
Frequently asked questions

Questions about System1

No items found.
Setup guides
System1 RSOC setup guide
System1 RSOC mobile setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with System1?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare pulls System1 RSOC conversions and revenue by API with your Auth Key. Desktop and mobile each have a template, and an older revenue stream integration lets you pick Sub ID 1 or 2."}}, {"@type": "Question", "name": "How often is System1 revenue updated?", "acceptedAnswer": {"@type": "Answer", "text": "It depends on your ClickFlare subscription plan."}}, {"@type": "Question", "name": "Why does my System1 revenue show up a day late?", "acceptedAnswer": {"@type": "Answer", "text": "Send the ClickFlare campaign ID in the subid parameter (s1paid on mobile). Without it, revenue is only reflected from the next day."}}, {"@type": "Question", "name": "Is System1 click-level revenue exact?", "acceptedAnswer": {"@type": "Answer", "text": "No. ClickFlare estimates it from the revenue dimensions System1 provides: segment, subid or campaign ID, geo and device."}}, {"@type": "Question", "name": "Where do the System1 postbacks go?", "acceptedAnswer": {"@type": "Answer", "text": "Into the offer URL, as impression_track_url, search_track_url and click_track_url. Encode each postback after the equal sign, or it breaks and conversions don't report."}}, {"@type": "Question", "name": "What is the difference between subid and nonrevsubid?", "acceptedAnswer": {"@type": "Answer", "text": "subid tracks campaign or ad group performance and has a daily limit. nonrevsubid is the most granular, has no limit and carries no revenue, so it holds {cf_click_id}."}}]}