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

# Conversion API not sending events to Meta Events Manager

> Fix the Meta Conversion API not sending events from Cometly: the Meta pixel settings, access and allow list checks that get events into Events Manager.

The Conversion API sends the events Cometly tracks (leads, purchases and other conversions) from Cometly's servers straight to Meta. If the Conversion API is on for Meta in Cometly (**Events Manager**, **Conversion API** tab, **Meta** row) but you are not receiving events in your Meta Events Manager, work through the checks below.

When the Meta Conversion API is not sending events that you can see in Meta, the cause is usually a setting on the Meta side. A pixel setting can block the events or their parameters, the profile connected to Cometly may not be an admin on the pixel, your domain may be missing from the allow list, or a second Conversion API may be competing with Cometly's. The six checks below cover each of these in turn.

## 1. Check the Meta pixel's Settings tab

In Meta, go to **Events Manager > Datasets > your pixel > Settings** and check the following.

> [!WARNING]
>
> **If you are in a Special Ad Category:**
>
> * Make sure Core Setup is turned ON.
> * Make sure you are feeding the [Event Source URL back to Meta](https://docs.cometly.com/guides/conversion-api/meta-event-source-url.md).
> * Make sure you are NOT using standard events (use custom events instead).

* **Manage Parameter Blocking:** do NOT block any parameters that could be coming from Cometly.
* **Manage Event Blocking:** do NOT block any events that could be coming from Cometly.
* Turn ON First Party Cookies.
* Turn ON Automatic Advanced Mapping.
* Turn OFF "Track events automatically without code".
* Create an allow list and allow the domains that you know you are using.
* Turn ON "Auto-tracking" for the ad account that you use this pixel with.

[Health check of the Meta pixel settings for the Cometly Conversion API](https://www.loom.com/embed/43ba561357654013a9931069799a2348)

## 2. Check admin access on the Meta pixel

Make sure the profile connected to Cometly is an admin on the Meta pixel (also known as a dataset):

1. Go to your Meta Events Manager.
2. Navigate to the pixel section.
3. Verify that the profile connected to Cometly has admin access.
4. If the profile is not listed as an admin, click **Add People**, enter the profile details and assign the admin role.

## 3. Verify the domain allow list

If you use a domain allow list (whitelisting) in the Meta pixel settings, make sure your domain is on it. Cometly sends the URL where the event was tracked as the event source URL in the Conversions API payload.

1. Go to your Meta Events Manager.
2. Navigate to the pixel settings.
3. Look for the domain allow list section.
4. Make sure your domain is listed. If it is not, add it.

## 4. Configure the Conversion API as an integration

Make sure the Conversion API is configured as an integration in Meta:

1. Go to your Meta Events Manager.
2. Navigate to the Integrations section.
3. Click **Manage Integrations**.
4. Look for the Cometly Conversion API and make sure it is configured correctly.

## 5. Avoid multiple Conversion APIs

Make sure you do not have more than one Conversion API enabled. Meta allows only one Conversion API to send server events. Several active Conversion APIs for the same funnel can lead to conflicts and incorrect attribution.

1. Go to your Meta Events Manager.
2. Navigate to the Conversion API section.
3. Check whether more than one Conversion API is enabled.
4. If there are several, disable the ones you do not need and keep only the Cometly Conversion API.

## 6. Resync your Meta profile

To make sure Cometly has your latest Meta configuration, click **Integrations** in the Cometly sidebar. Under **Ad Platforms**, expand **Meta Ads** and click **Resync** next to your Meta profile.

## Allow for processing delays

Occasionally, data sent through the Conversions API can take up to **48 hours** to be processed and displayed in Meta Events Manager. Allow enough time before you conclude that there is an issue.

## Confirm the Meta Conversion API is sending events

In Cometly, open **Events Manager** and the **Conversion API** tab, and check that the **Meta** row shows an **Active** badge. Then wait for a new conversion to be tracked. Cometly sends each conversion to Meta about 15 minutes after the event is tracked, so look for it in Meta Events Manager after that, and allow up to 48 hours for Meta to display it.

If events still do not arrive after these checks, Meta support can review the pixel from their side.

## Frequently asked questions

### Why are only some of my Cometly events showing in Meta Events Manager?

This is expected when the Meta row is set to **Send only attributed events**: Cometly then sends only the events it can attribute to a Meta ad click. A custom rule can also stop a single event from being sent. To change either setting, see [Configure the Meta Conversion API](https://docs.cometly.com/guides/conversion-api/meta.md).

### Which Meta pixel does Cometly send my events to?

Attributed events go to the pixel attached to the ad that drove them. Unattributed events and Meta lead forms go to the **Pixel ID** you entered on the **Meta** row. If you are looking at a different pixel in Meta Events Manager, the events will not be there.

### Does Cometly's Conversion API send page views to Meta?

No. Cometly's Conversion API doesn't send page view events, so they never arrive from Cometly. Add the Meta Pixel to the `<head>` of your site pages for page views, and use the Conversion API for all other events.

## Next steps

* [Review your Meta Conversion API settings in Cometly](https://docs.cometly.com/guides/conversion-api/meta.md)
* [Send the Event Source URL to Meta](https://docs.cometly.com/guides/conversion-api/meta-event-source-url.md)
* [Check which events Cometly tracked in the Events Log](https://docs.cometly.com/support/troubleshooting/general/event-log.md)
* [Contact Cometly support](https://docs.cometly.com/support/contact.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.