Make and ClickFlare,conversions flowing both ways

ClickFlare events like conversions can start a Make scenario that logs them, alerts your team or updates your CRM. In the other direction, any app Make connects can report conversions to ClickFlare by click ID, and scenarios can pull report data through the ClickFlare API.

Mk
Make
Visual automation platform

Make integration at a glance

How it connects
ClickFlare webhook out; conversions and API calls back in
What syncs
ClickFlare events out; conversions and report data in
How fresh the data is
Instantly, or on a schedule you set in Make
What you can optimize
Campaigns judged on sales reported by your other apps
Works with
Visits, clicks, conversions and custom conversions
Good to know
A Make webhook with no active scenario for 5 days stops working.
Automation platform
Conversions both ways
Events start scenarios

Every app Make connects can report to ClickFlare

Conversions from any app

Apps with no postback of their own can report conversions, as long as they store the click ID and the scenario sends it to ClickFlare.

Partner payloads mapped directly

Make reads nested data and does math as it maps, so a partner's own payload becomes a ClickFlare conversion with no extra steps.

Key stored once

Your ClickFlare API key sits in a Make keychain and goes with every request, kept out of addresses and scenario logs.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue

01
Your ad
Visitor clicks
Ad on Make
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to Make
Through the Conversion API or postback
05
Cost API
Spend pulled in
Make cost matched to each campaign
01
Your ad
Make click
Placement, device and country come along
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 Make
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
Make API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
The click follows the visitor to the offer
03
Make
Offer or call
The network tracks the action
04
Make
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
Every click gets its own ID
03
Make
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
01
Your ad
Visitor clicks
Form, call or landing page
02
ClickFlare
Click recorded
Every click gets its own ID
03
Make
Lead or call stored
The ad stays linked to the lead
04
Make
Qualified or closed
Workflow or call rule fires
05
ClickFlare
Revenue recorded
Tied to the ad that drove it
01
ClickFlare
Event happens
Click, conversion or custom event
02
Webhook or API
Data goes out
Or comes back in
03
Make
Your workflow
Rules, apps or an AI assistant
04
Make
Action
Alert, update, pause or scale
05
ClickFlare
Back in reports
Changes show in your data
01
ClickFlare
Report data
Campaigns, sources, offers
02
ClickFlare API
Your numbers go out
Secured with your API key
03
Your setup
Scheduled refresh
A sheet, script or connector
04
Make
Data lands
Tables refreshed on schedule
05
Make
Dashboards
Blended with your other data
Automation platform

ClickFlare events out, conversions in

Out: each mapped ClickFlare event lands in your Make webhook's queue and runs the scenario. In: a scenario step sends the click ID, payout and conversion type to ClickFlare, which counts the conversion on the original click.
  • Each Make webhook keeps its own queue
  • Every conversion matched by its click ID
  • Conversion types match your custom conversions
Today, one campaign
example
Spend pulled from Make
cost
$412.30
Conversions recorded
today
38
Sent back to Make
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
ROI per placement
example
Placement A · mobile
cost
$38.20
Placement A
revenue
$71.40
Placement A
ROI
+87%
Placement B · desktop
ROI
−42%
Example numbers. Keep the placements that pay and cut the ones that lose money.
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 Make 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.
One lead, followed to revenue
example
Lead created
day 0
$0.00
Qualified
day 2
+$25.00
Deal closed
day 14
+$480.00
Renewal
day 45
+$120.00
Example values. Each stage can be its own event type in ClickFlare.
A scheduled report refresh
example
Campaigns
in the report
1,240 rows
Cost, revenue, profit
per campaign
included
Refresh
your schedule
done
Dashboards fed
Make
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
Make
received
Workflow ran
Make
done
Team notified
your apps
done
Example run. What happens after the event is up to your workflow.
10
Events per integration
5 days
Before idle webhooks stop
3 days
Make webhook log retention
2.3B
Events tracked
Setup

Connected in three steps

You need a ClickFlare account with your own tracking domain, a Make account with enough credits, and an API key for API calls.
  1. Start a scenario from ClickFlare Create a custom webhook in Make and add it to ClickFlare's webhook integration for the events you want, with filters if needed.
  2. Let Make learn the data Fire one real event from ClickFlare so Make lists the fields. Build the rest of the scenario and switch it on.
  3. Report conversions back Add a step that sends the click ID, payout and conversion type to ClickFlare. Run it once with a real click ID.
app.clickflare.com/integrations
Mk
Make
Automation platform
Connected
Make account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Make template selected
Macros pre-filled
Tracking URL in Make
Click ID captured
Conversions reported
Payout included where supported
Make connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Make added
Offer URL carries the click ID
Postback set in Make
Payout and event included
Conversions arriving
Matched to the click
Make connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in Make
Hidden field or call data
Workflow or rule set
Fires on the stage you choose
Conversions arriving
With payout and event type
API key created
Settings, then Security
Report pull scheduled
Dimensions and date range set
Make dashboards live
Refreshed on schedule
Connection set up
Webhook, API key or MCP
Events chosen
Only what the workflow needs
Workflow running
Tested end to end
Ready to track
Need several conversions on one click kept apart? Send a unique transaction ID with each. The same ID replaces the earlier conversion.
Make setup guide
Open the guide
In your reports

What you see once it's connected

  • Conversions from any Make app
  • Payout per conversion
  • Conversions by type
  • Partner rewards as conversions
  • Campaign stats via the API
  • ROI by campaign
Use cases

How media buyers run it

PartnerStack reward → Make → ClickFlare

Partner program rewards

Each reward becomes a conversion on the click that earned it, with the right payout.
Conversion → ClickFlare → Make → sheet row, CRM record or Slack alert, filtered to payout above 0

Conversion alerts and logging

Daily campaign report

A scheduled scenario pulls revenue, cost and ROI per campaign from the ClickFlare API and sends it to a sheet.
Frequently asked questions

Make integration FAQ

Does ClickFlare integrate with Make?

Yes, both ways. ClickFlare events start Make scenarios through a webhook, and Make can report conversions to ClickFlare or call the ClickFlare API.

Do ClickFlare events run the scenario right away?

Yes, by default. If you schedule the scenario instead, events wait in the webhook's queue and run on the next scheduled pass.

Why don't new fields from ClickFlare show up in Make?

Make still uses the data it learned first. Ask the webhook to learn the data structure again and fire a new event from ClickFlare.

Can Make pull data from ClickFlare?

Yes. Store your ClickFlare API key in a Make keychain once, and any scenario can pull campaign and report data.

What if the Make queue fills up?

Make rejects new events until there is room. Check the queue, let each run take more events, or run the scenario more often.

Why did my Make webhook stop working?

A webhook with no active scenario for 5 days stops accepting events. Keep it attached to a scenario that is switched on.

No items found.
Setup guides
Make setup guide
Custom webhook integration
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Make?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, both ways. ClickFlare events start Make scenarios through a webhook, and Make can report conversions to ClickFlare or call the ClickFlare API."}}, {"@type": "Question", "name": "Do ClickFlare events run the scenario right away?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, by default. If you schedule the scenario instead, events wait in the webhook's queue and run on the next scheduled pass."}}, {"@type": "Question", "name": "Why don't new fields from ClickFlare show up in Make?", "acceptedAnswer": {"@type": "Answer", "text": "Make still uses the data it learned first. Ask the webhook to learn the data structure again and fire a new event from ClickFlare."}}, {"@type": "Question", "name": "Can Make pull data from ClickFlare?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Store your ClickFlare API key in a Make keychain once, and any scenario can pull campaign and report data."}}, {"@type": "Question", "name": "What if the Make queue fills up?", "acceptedAnswer": {"@type": "Answer", "text": "Make rejects new events until there is room. Check the queue, let each run take more events, or run the scenario more often."}}, {"@type": "Question", "name": "Why did my Make webhook stop working?", "acceptedAnswer": {"@type": "Answer", "text": "A webhook with no active scenario for 5 days stops accepting events. Keep it attached to a scenario that is switched on."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "Automation", "item": "https://www.clickflare.com/integrations/automation"}, {"@type": "ListItem", "position": 3, "name": "Make"}]}]}