CodeFuel revenue,pulled hourly into ClickFlare

ClickFlare connects to CodeFuel (Perion) with your Client ID and Client Secret and pulls conversions and revenue every hour for 3 days after each conversion. The click ID travels in gclid, and the postback can sit right in the offer URL.

CF
CodeFuel (Perion)
Perion search feed
At a glance
How it connects
CodeFuel Client ID and Client Secret + postback
What syncs
Conversions and revenue
Sync schedule
Hourly for 3 days after the conversion
Key parameters
q, gd, gclid, subid, pb
Works with
Paid traffic to CodeFuel search links
Good to know
The click ID must go in gclid. There is no sub ID choice.
Search feed
Hourly revenue sync
Postback in the URL

CodeFuel revenue without waiting on reports

Postback in the link

Encode the ClickFlare postback into the pb parameter of your offer URL and it travels with every visit, with no account manager needed.

Or let CodeFuel add it

Prefer not to edit links? Share the postback with your CodeFuel account manager and they implement it for you.

Revenue that keeps updating

ClickFlare pulls CodeFuel revenue every hour for 3 days after each conversion, so ROI keeps pace with the feed.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

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

Two ways to send CodeFuel conversions

The offer URL sends {cf_click_id} in gclid and subid. For conversions, encode the postback into the pb parameter or have your account manager add it. Revenue then syncs by API every hour for 3 days.
  • gclid carries the ClickFlare click ID
  • Encode the postback before adding it to pb
  • Revenue pulled hourly for 3 days
Today, one campaign
example
Spend pulled from CodeFuel (Perion)
cost
$412.30
Conversions recorded
today
38
Sent back to CodeFuel (Perion)
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every CodeFuel (Perion) click
key macros
q, gd, gclid, subid, pb
captured
From the CodeFuel (Perion) 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 CodeFuel (Perion) 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.
1h
Revenue sync interval
3 days
Of hourly updates
2.3B
Events tracked
Setup

Connected in three steps

You need an active CodeFuel account, your CodeFuel Client ID and Client Secret, and a ClickFlare account.
  1. Add the CodeFuel integration Open Integrations and click Add Integration under Revenue Stream. Pick the CodeFuel template, name it, enter your Client ID and Client Secret, choose the custom conversion and save.
  2. Build the offer URL Use your CodeFuel search link with q and gd, and send {cf_click_id} in gclid and subid. The integration has no sub ID setting because gclid is required.
  3. Set up the postback Encode the ClickFlare postback into the pb parameter of the offer URL, or share the postback with your CodeFuel account manager to implement.
CodeFuel offer URL with the ClickFlare click ID
https://search.automotivepro.co/search?q=shoes&gd=AP1007384&gclid={cf_click_id}&subid={cf_click_id}
app.clickflare.com/integrations
CF
CodeFuel (Perion)
Search feed
Connected
CodeFuel (Perion) account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
CodeFuel (Perion) template selected
Macros pre-filled
Tracking URL in CodeFuel (Perion)
Click ID captured
Conversions reported
Payout included where supported
CodeFuel (Perion) connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
CodeFuel (Perion) added
Offer URL carries the click ID
Postback set in CodeFuel (Perion)
Payout and event included
Conversions arriving
Matched to the click
CodeFuel (Perion) connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
Encode the postback before you add it to the pb parameter. An unencoded postback inside the URL can break.
CodeFuel setup guide
Open the guide
In your reports

What you see once it's connected

  • Revenue per campaign
  • Revenue per search link
  • Conversions per campaign
  • Hourly revenue updates
  • Profit after ad cost
  • ROI by traffic source
Use cases

How media buyers run it

Native ad → CodeFuel search page with a set query

Native to CodeFuel search

Compare campaigns on the revenue each one returns per click.
Meta → CodeFuel search page

Social to CodeFuel search

Keep gclid and subid on every link and judge each ad on its CodeFuel revenue.

Hands-off postback

Running many links? Ask your account manager to implement the postback once instead of encoding it into each URL.
Frequently asked questions

Questions about CodeFuel (Perion)

No items found.
Setup guides
CodeFuel setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with CodeFuel?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare pulls CodeFuel (Perion) conversions and revenue through the API with your Client ID and Client Secret."}}, {"@type": "Question", "name": "How often is CodeFuel revenue updated?", "acceptedAnswer": {"@type": "Answer", "text": "Every hour for 3 days from the moment a conversion happens."}}, {"@type": "Question", "name": "Which parameter takes the CodeFuel click ID?", "acceptedAnswer": {"@type": "Answer", "text": "gclid. CodeFuel needs {cf_click_id} there, so the integration doesn't ask you to choose a sub ID like other feeds."}}, {"@type": "Question", "name": "Where does the CodeFuel postback go?", "acceptedAnswer": {"@type": "Answer", "text": "Either encoded in the pb parameter of your offer URL, or set up by your CodeFuel account manager. For the second option, share the ClickFlare postback with them."}}, {"@type": "Question", "name": "What do I need from CodeFuel to connect?", "acceptedAnswer": {"@type": "Answer", "text": "An active CodeFuel account and your CodeFuel Client ID and Client Secret."}}]}