Funnelish funnels,tracked from page view to sale

A ClickFlare script added to your Funnelish funnel fires view_content and checkout_created. A Funnelish automation sends purchases to ClickFlare by webhook as sale and product_sale. Each event is attributed through the click ID on your offer URLs.

FN
Funnelish
Funnel builder
At a glance
How it connects
Funnel custom code + On Purchase webhook
What syncs
Page views, checkouts, sales, product sales
Sync schedule
Real time, per event
Key parameters
click_id={cf_click_id}
Works with
Front-end offers, upsells, downsells and OTOs
Good to know
The checkout step name must contain the word Checkout.
Checkout & funnel builder
Funnel script + webhook
Upsells and OTOs

Every Funnelish step, tied to the ad

One script for every step

Add the script once under Custom Codes and it runs on all steps of the funnel, firing page views and checkout loads.

Upsells and OTOs included

Any purchase that triggers the On Purchase automation reaches ClickFlare, so upsells, downsells and OTOs count when the click ID is passed.

Sale and product detail

Purchases arrive as sale and product_sale, so you see order revenue and what was bought, per campaign.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

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

Script for pages, automation for purchases

Funnelish doesn't send purchases through the script. So the ClickFlare script covers page views and checkout loads, and a Funnelish automation triggered On Purchase (All steps) posts each sale to the ClickFlare webhook URL.
  • Script fires view_content and checkout_created
  • Webhook fires sale and product_sale
  • Click ID passed on every offer URL
Today, one campaign
example
Spend pulled from Funnelish
cost
$412.30
Conversions recorded
today
38
Sent back to Funnelish
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every Funnelish click
key macros
click_id={cf_click_id}
captured
From the Funnelish 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 Funnelish 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.
4
Funnel events tracked
2.3B
Events tracked
Setup

Connected in four steps

You need a Funnelish funnel, a ClickFlare account and a ClickFlare tracking domain.
  1. Create four custom conversions In Settings, Custom Conversions, add view_content, checkout_created, sale and product_sale with these exact parameters. Usually only Sale goes into revenue reporting.
  2. Add the ClickFlare script In Funnelish, open your funnel, go to Settings, then Custom Codes, and click Create a new code. Paste the ClickFlare Funnelish script with your tracking domain.
  3. Create the purchase automation In the funnel's Automations, create one from scratch with the trigger On Purchase (All steps). Add a Webhook action with the ClickFlare webhook URL, then End Automation, and save.
  4. Pass the click ID to your offers Append ?click_id={cf_click_id} to every Funnelish offer URL you create in ClickFlare, so each event is attributed to the right click.
Script for Funnelish Custom Codes
<script src="https://your-tracking-domain.com/cf/scripts/funnelish"></script>
app.clickflare.com/integrations
FN
Funnelish
Checkout & funnel builder
Connected
Funnelish account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Funnelish template selected
Macros pre-filled
Tracking URL in Funnelish
Click ID captured
Conversions reported
Payout included where supported
Funnelish connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Funnelish added
Offer URL carries the click ID
Postback set in Funnelish
Payout and event included
Conversions arriving
Matched to the click
Funnelish connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
Name your checkout step with the word Checkout, for example Checkout Page. The script reads the step name to fire checkout_created. Without it, that event never fires.
Funnelish setup guide
Open the guide
In your reports

What you see once it's connected

  • Page views per campaign
  • Checkouts by traffic source
  • Sales and revenue per ad
  • Product-level sales
  • Upsell and OTO revenue
  • Checkout-to-sale drop-off
Use cases

How media buyers run it

Meta → Funnelish funnel

Send Meta traffic to the funnel and see page views, checkouts and sales per ad, next to cost.

Front end plus OTOs

Pass the click ID on each upsell URL and count OTO purchases against the same click as the front-end sale.
Native → advertorial → Funnelish checkout

Advertorial → checkout

Compare presell angles by checkout loads and completed sales.
Frequently asked questions

Questions about Funnelish

No items found.
Setup guides
Funnelish setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Funnelish?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. A ClickFlare script in your funnel tracks page views and checkouts, and a Funnelish automation sends purchases to ClickFlare by webhook."}}, {"@type": "Question", "name": "Do I need both the script and the webhook?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The script handles view_content and checkout_created. The webhook handles sale and product_sale, because Funnelish doesn't send purchase events through the script."}}, {"@type": "Question", "name": "Why isn't checkout_created firing in Funnelish?", "acceptedAnswer": {"@type": "Answer", "text": "The checkout step name must contain the word Checkout, such as Checkout or Checkout Page. The script uses the step name to recognize the checkout."}}, {"@type": "Question", "name": "Can I track Funnelish upsells, downsells and OTOs?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, as long as the click ID is passed, for example in the URL, and the purchase triggers the On Purchase automation."}}, {"@type": "Question", "name": "Does my Funnelish domain need to match my tracking domain?", "acceptedAnswer": {"@type": "Answer", "text": "No. They can be different. Only the script and webhook URLs must use the same ClickFlare tracking domain."}}, {"@type": "Question", "name": "Should I use a custom tracking domain with Funnelish?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, it's recommended. Custom domains reduce the risk of blocklisting."}}]}