Skip to main content
The Conversion API sends the events Cometly tracks (leads, purchases and other conversions) from Cometly’s servers straight to Meta. When you set up the Meta Conversion API in Cometly, you choose which events Meta receives and can set a different rule for any single event. This matters because Meta optimizes ad delivery from the conversions it can see. Sending the conversions Cometly has tied to your ads lets Meta link more of them to the correct ad, so your campaigns learn from real leads and sales.

How it works and why it helps

When Cometly sends data back to Meta, it provides accurate, enriched information about your conversions. This gives you:
  • Better match quality: Meta can link more conversions to the correct ads.
  • Improved ad optimization: better data leads to smarter ad delivery.
  • Faster AI learning: Meta’s AI can optimize campaigns faster with richer data.

How Cometly’s Conversion API is different

Other Conversion APIs send only the data available at the time of an event. Cometly builds a profile for every visitor and keeps it up to date, so the most complete data is sent when an event occurs. That gives Meta a better chance of matching the event, which improves ad optimization.

Before you start

  • Connect your Meta ad account to the space (your Cometly workspace). See Connect your ad platforms.
  • Make sure your events are tracking accurately in Cometly. The Conversion API page recommends waiting at least 7 days after events start flowing before you turn data sharing on.

Configure the Meta Conversion API

  1. In Cometly, click Events Manager in the sidebar, then open the Conversion API tab.
  2. Click the Meta row to expand it.
  3. Under Master Data Sharing Settings, select one of the options:
    • Turn off data sharing: no event data is sent to Meta.
    • Send only attributed events (recommended): sends only events that Cometly can attribute to a Meta ad click. This prioritizes quality by including key parameters (like fbclid) that improve the match score in Meta Events Manager. If your event has a phone number, you can expect an event match quality score between 8.0 and 9.3.
    • Send all events: sends all event data to Meta, including unattributed events. This prioritizes quantity over quality, because some parameters (like fbclid) may be missing, which lowers the match score in Meta Events Manager.
  4. Select a Meta ad account and enter a Pixel ID. Cometly uses this account’s Meta login and this pixel for unattributed events and Meta lead forms. Attributed events go to the pixel attached to the ad that drove them. Both fields are required when you send all events, either as the master setting or in a custom rule.
    Meta section of the Conversion API tab with arrow 1 on the selected Send only attributed events option, arrow 2 on the Meta ad account and Pixel ID fields, and arrow 3 on the Save button.
  5. Click Save.

Custom rules for specific events

The master setting applies to every event. To make one event behave differently, add a custom rule. Events without a rule follow the master setting.
  1. Expand Custom Rules for Specific Events and click Add custom rule.
  2. Under Cometly event, select one of your tracked events.
    Custom Rules for Specific Events panel with four rules and the Cometly event dropdown open on the first rule, showing a searchable list of events.
  3. Under Rule, pick one of the options:
    • Do not send any events: the event is never sent to Meta.
    • Only send attributed events: sends the event only when it is attributed to a Meta ad.
    • Send all events: sends every occurrence of the event, regardless of attribution.
    Custom Rules for Specific Events panel with three rules and the Rule dropdown open on the first rule, with a box around the options Do not send any events, Only send attributed events and Send all events.
  4. Click Save.

Advanced: force all events to a single Meta pixel

When the master setting is Send all events, an Advanced section appears with the option Force all events to a single Meta pixel. By default Cometly routes each conversion to the Meta pixel attached to the ad that drove it, which is correct for nearly all accounts. Turning this on sends every conversion to the Pixel ID you entered above instead.
Only turn this on if you have consolidated to a single pixel, or Meta support or your agency told you to send everything to one pixel. Forcing events to the wrong pixel can break attribution in Meta Ads Manager and is difficult to reverse.

Check it worked

On the Conversion API tab, the Meta row shows an Active badge once data sharing is on. Cometly sends each conversion to Meta about 15 minutes after the event is tracked, so allow that long before you look for new events in Meta Events Manager. If you choose Send only attributed events, you see higher match quality scores inside Meta, because Cometly sends enriched data for each event.
Meta Events Manager Event Quality tab showing an Event Match Quality Score of 8.0 out of 10

Important considerations

  • One Conversion API only: Meta allows only one active Conversion API. Disable any others before enabling Cometly’s.
  • Page view events: Cometly’s Conversion API doesn’t send page view events. Add the Meta Pixel to the <head> of all your site pages for browser-based tracking.
  • Best setup: place the Meta Pixel in the <head> of your site for page views, and use Cometly’s Conversion API to send all other events to Meta from the server.

Frequently asked questions

How long does it take for Cometly events to show up in Meta Events Manager?

Cometly sends each conversion to Meta about 15 minutes after the event is tracked, so a new lead or sale does not appear in Meta instantly. If events still have not arrived after that, work through Meta CAPI not sending events.

Can I stop a single conversion from being sent to Meta, for example when a visitor opts out?

Yes. You can flag an individual event so Cometly records it for attribution and reporting but does not send it through the Conversion API. The flag applies to every ad platform, not only Meta. See Exclude an event.

Why does Meta say my site is in a category with restrictions?

Meta flags or blocks Conversion API events from sites that deal with sensitive topics (health, political or social issues) unless the event includes the Event Source URL parameter. You can send that URL to Cometly so it is included in the events sent to Meta. See Event source URL for the Meta Conversion API.

Next steps

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