Zapier and ClickFlare Integration Guide

• ClickFlare → Zapier. ClickFlare’s Custom Webhook sends an event (a conversion, a purchase, a click) to a Zapier Catch Hook. The Zap passes it on to Google Sheets, your CRM, Slack or any other app.
• Zapier → ClickFlare. A Webhooks by Zapier POST step sends a conversion to ClickFlare’s postback endpoint as JSON. Any app Zapier connects to (a form tool, a CRM, a payment platform, a partner program) can then report conversions to ClickFlare, as long as it has the click ID.

​

At a glance

1. Create a Catch Hook in Zapier.
2. Map the event in ClickFlare.
3. Set up the conversion trigger.
4. Add the POST to ClickFlare.

​

How the data flows

ClickFlare → Zapier
  Conversion recorded in ClickFlare
  → Custom Webhook fires (POST, with macros)
     https://hooks.zapier.com/hooks/catch/123456/abcde/
  → Catch Hook trigger parses the body
  → Actions: Google Sheets row, CRM record, Slack message...

Zapier → ClickFlare
  Trigger in any app (new deal, new payment, partner webhook)
  → Webhooks by Zapier: POST, payload type JSON
     https://trk.yourdomain.com/cf/cv
     {"cf_click_id": "CF_CLICK_ID", "payout": 25, "ct": "sale"}
  → ClickFlare matches the conversion to the original click

​

What you’ll need

• A ClickFlare account with your own tracking domain for postbacks. See Tracking domains.
• A Zapier account. Zapier’s help pages list Webhooks by Zapier as available on its Free, Professional, Team and Enterprise plans. Check your own account for what your plan includes, and for task limits.
• For Zapier → ClickFlare: the click ID stored somewhere the trigger app can return it, for example a hidden form field or a CRM field.
• For API calls: an API key from Settings → API Keys.

​

Send ClickFlare events to Zapier

1

Create a Catch Hook in Zapier

In the Zap editor, click the trigger step, search for Webhooks by Zapier and pick the Catch Hook event. Click Continue. Leave Pick Off A Child Key empty to use the whole body. In the Test tab, click Copy to copy the webhook URL.Use Catch Raw Hook instead only if you need the request headers or the unparsed body. Its limit is 2MB, against 10MB for Catch Hook.

2

Add a Webhooks integration in ClickFlare

Go to Integrations, click Conversion API → New integration and choose Webhooks. Pick the Workspace and give it a Name, for example “Purchases to Zapier”.

3

Map the event

Under Event Type Mapping:

1. Pick the ClickFlare Event, for example the conversion or a custom conversion such as Purchase.
2. Set the Request Method to POST.
3. Paste the Zapier URL as the Webhook URL.
4. Add the values you need with ClickFlare macros, in the URL or the body. For example:

https://hooks.zapier.com/hooks/catch/123456/abcde/?click_id={cf_click_id}&payout={payout_currency}

ClickFlare replaces each macro with the real value when the event fires. With a POST and a JSON body, it sets Content-Type: application/json for you.

4

Filter, save and test

To fire only on some events, click Add Conditions: for example payout greater than 0, one campaign or offer, or one country. Click Next, then Save.Trigger a real event, go back to the Zap’s Test tab and click Test trigger. Zapier splits the request into fields you can map in the next steps. Then add your actions and turn the Zap on.

​

Report conversions from Zapier to ClickFlare

curl -X POST 'https://trk.yourdomain.com/cf/cv' \
  -H 'Content-Type: application/json' \
  --data '{"cf_click_id": "abc", "ct": "search", "param1": "test", "payout": 1}'

​

Read ClickFlare data in a Zap

• For a simple read, use a Webhooks by Zapier GET step to https://public-api.clickflare.io/api/campaigns/list with the api-key header in Headers.
• For the report endpoint, POST /api/report, use Custom Request. Its body has nested arrays (groupBy, metrics), and Custom Request sends raw JSON exactly as you type it. Check it with a JSON validator first: Zapier doesn’t format it for you.

{
  "startDate": "2026-11-01 00:00:00",
  "endDate": "2026-11-01 23:59:59",
  "timezone": "UTC",
  "groupBy": ["campaignID"],
  "metrics": ["campaignID", "campaignName", "visits", "conversions", "revenue", "cost", "roi"],
  "sortBy": "revenue",
  "orderType": "desc",
  "page": 1,
  "pageSize": 100,
  "includeAll": false
}

​

Limits and behavior worth knowing

• Turned-off Zaps. When a Zap is off or deleted, Zapier answers its Catch Hook URL with a 404, after a delay of up to several hours. Turn it back on and it returns 200 again.
• Ownership. The hook URL contains the owner’s Zapier ID. It only changes if the Zap moves to another user, and then you must paste the new URL into ClickFlare.
• Arrays. If a request body is a JSON array of objects, Zapier runs the Zap once per object.
• Payload size. 10MB for Catch Hook, 2MB for Catch Raw Hook, 5MB for webhook actions. Rate limits apply to Webhooks by Zapier.
• Several Zaps from one event. Zapier can combine hook URLs owned by the same user, but it’s simpler to map the event several times in ClickFlare.

​

Verify the setup

​

Troubleshooting

​

FAQ

​

Related