> ## Documentation Index
> Fetch the complete documentation index at: https://clickflare.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# CAPI or Pixel Not Firing

> The integration saves but the ad platform receives no conversion events. Check permissions, event mapping and which campaigns the integration covers.

The Conversion API integration is configured and shows no error, but the ad platform reports no conversions coming from ClickFlare.

Sending conversions *back* to the ad platform is a separate mechanism from recording them in ClickFlare. Conversions can be perfectly visible in your reports and still never reach the platform.

<Info>
  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](/docs/en/troubleshooting/conversions-not-showing).
</Info>

## Check in this order

<AccordionGroup>
  <Accordion title="1. Does the connected account have permission?" icon="user">
    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.
  </Accordion>

  <Accordion title="2. Is the integration assigned to the campaign?" icon="tag">
    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](/docs/en/advanced-tracking-configuration/how-to-send-one-event-to-specific-campaigns-in-click-flare).
  </Accordion>

  <Accordion title="3. Is the right event mapped?" icon="bolt">
    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](/docs/en/getting-started-with-click-flare/understanding-clickflare-events).
  </Accordion>

  <Accordion title="4. Is an event filter blocking it?" icon="filter">
    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)](/docs/en/advanced-tracking-configuration/conversion-filter).
  </Accordion>

  <Accordion title="5. Is the platform's click identifier present?" icon="link">
    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](/docs/en/troubleshooting/tokens-arriving-empty).
  </Accordion>

  <Accordion title="6. Have you waited?" icon="clock">
    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.
  </Accordion>
</AccordionGroup>

## 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.

Where both are possible, a server-to-server postback is more reliable than a pixel. See [Conversion Tracking Methods Explained](/docs/en/getting-started-with-click-flare/conversion-tracking-methods-explained).

## Related

<Columns cols={2}>
  <Card title="Adding an integration" icon="plug" href="/docs/en/integrations/adding-an-integration">
    Connecting a conversion API integration from scratch.
  </Card>

  <Card title="Conversion pixel" icon="crosshairs" href="/docs/en/tracking/track-conversions-using-a-conversion-tracking-pixel">
    Placing and testing a conversion tracking pixel.
  </Card>
</Columns>