Confirm first that ClickFlare is recording the conversions at all. If it is not, fix that first — there is nothing to forward. See Conversions not showing.
Check in this order
1. Does the connected account have permission?
1. Does the connected account have permission?
The most common failure, and it surfaces as a permissions error at setup rather than silently: the account you authorised cannot write to the pixel or conversion action you selected.On platforms with agency or MCC structures, the account that can see a pixel is often not the one that can send events to it. Reconnect using an account with write access.
2. Is the integration assigned to the campaign?
2. Is the integration assigned to the campaign?
An integration only forwards conversions for the traffic sources and campaigns it is assigned to. A new or duplicated campaign is not covered automatically.Check the integration’s configuration and confirm this campaign falls inside it.See How to Send One Event to Specific Campaigns.
3. Is the right event mapped?
3. Is the right event mapped?
ClickFlare events must map to the platform’s event names. If your conversions arrive as a custom event but the integration forwards
Purchase, the platform receives nothing it recognises.Check both sides: which ClickFlare event the conversion creates, and which platform event the integration sends.See Understanding ClickFlare Events.4. Is an event filter blocking it?
4. Is an event filter blocking it?
Conditional rules stop events that fail the condition from being sent. A filter added for one campaign can quietly apply more broadly than intended.See Event Filter (Conditional Conversion API and Postback).
5. Is the platform's click identifier present?
5. Is the platform's click identifier present?
Platforms match a server-side conversion to an ad using their own click identifier, captured when the visitor arrived. If that identifier was never captured, the event is received but cannot be attributed — which on most platforms looks identical to nothing arriving.An empty identifier column is the tell. See Tokens arriving empty.
6. Have you waited?
6. Have you waited?
Platforms do not display server-side events instantly, and most have their own reporting delay on top. Check the platform’s own events or diagnostics view rather than its campaign reporting, which updates more slowly.
Pixels specifically
A conversion pixel fires in the visitor’s browser, so it is subject to everything a browser can do to it.- It must be on the page the visitor reaches after converting, not on the offer page.
- Ad blockers, tracking prevention and privacy browsers stop it. Expect under-reporting relative to a postback.
- If the conversion happens on a domain you do not control, you cannot place a pixel there — use a postback instead.
Related
Adding an integration
Connecting a conversion API integration from scratch.
Conversion pixel
Placing and testing a conversion tracking pixel.