Skip to main content
The Conversion API sends the events Cometly tracks (leads, sales and other conversions) from Cometly’s servers straight to your ad platforms. It does not rely on the visitor’s browser, so a conversion still reaches the platform when a cookie is blocked or the sale happens days after the click. It matters because ad platforms optimize on the conversions they can see. When Meta, Google or TikTok receives the conversions Cometly attributed to its ads, it can find more people like the ones who became leads and customers, and its own reporting gets closer to what happened. To set up the Conversion API in Cometly, pick your platform under Set up by platform.

What the Conversion API sends

Cometly sends the conversions you track as events: a lead from a form, a purchase from Stripe or Shopify, a deal from your CRM, and so on. Each one goes out with the details the ad platform needs to match it to a person and, when Cometly knows it, to the ad click that came before it. Cometly sends each conversion about 15 minutes after the event is tracked, so allow that long before you look for it in the ad platform. The Conversion API is separate from attribution. Cometly records and attributes your leads and sales whether or not the Conversion API is on. Turning it on only controls whether those conversions are also sent back to your ad platforms.

You choose what each platform receives

The Conversion API is set up one ad platform at a time. In the left sidebar, click Events Manager, open the Conversion API tab and expand the row of the platform.
  • How much to share. Each platform has its own data sharing setting. For Meta, for example, the options are Turn off data sharing, Send only attributed events and Send all events. The guide for each platform lists the options it offers.
  • Where to send it. You pick the ad account, and for some platforms the pixel or the conversion actions, that should receive the conversions.
  • One event at a time. You can flag an individual event so Cometly keeps it for attribution and reporting but sends it to no ad platform. See Exclude an event.
A platform whose data sharing is turned off receives nothing.

When to turn it on

Ad platforms use these conversions to make bidding decisions, so the data you send needs to be right. Cometly recommends waiting at least 7 days after your space starts receiving event data before you turn on the Conversion API. A week gives you enough data to confirm that events are tracked correctly, attributed properly and not duplicated. The Conversion API tab shows how many days remain. Before you start, connect the ad platform and create the events you want to send.

Set up the Conversion API by platform

Check it is working

Click Setup in the left sidebar and open the Tracking Health tab. The Conversion API check passes when the Conversion API is on and a conversion was sent successfully in the last 14 days. See Tracking Health.

Frequently asked questions

Do I have to turn on the Conversion API to use Cometly?

No. Cometly tracks and attributes your conversions either way. The Conversion API only adds the step of sending them back to your ad platforms.

How long does it take for a conversion to reach the ad platform?

Cometly sends each conversion about 15 minutes after the event is tracked. The ad platform can then take more time of its own before the conversion shows in its reports.

Why are my conversions not showing in the ad platform?

Check that data sharing is on for that platform, that the right ad account is selected, and that conversions are coming in. See Conversion API not sending conversions for the full list of checks.

Next steps

Still have questions or need a hand? We’re happy to help. Reach our team at support@cometly.com.