Meta Conversions API (CAPI)

What Is Meta Conversions API

Meta Conversions API (CAPI) lets you send web events from your server directly to Meta. Compared to the browser-based Meta Pixel, server-side events are not blocked by ad blockers, browser privacy features, or iOS App Tracking Transparency restrictions.

PixelsCleared acts as the server-side bridge. Events flow from your website to PixelsCleared, get scrubbed and consent-checked, then are forwarded to Meta CAPI on your behalf.

Credentials You Need

Meta CAPI requires two pieces of information:

• Pixel ID -- A numeric identifier for your Meta Pixel (for example, 123456789012345).
• Access Token -- A long-lived token that starts with EAAB and authorizes server-side event submission.

Get Your Credentials from Meta Events Manager

1. Open Meta Events Manager and sign in with your Meta Business account.
2. Select the Pixel you want to connect (or create a new one).
3. Copy the Pixel ID from the pixel overview page. It is a long number displayed below the pixel name.
4. Go to Settings in the left sidebar.
5. Scroll to Conversions API and click Generate Access Token.
6. Follow the prompts. Copy the token and store it somewhere secure -- Meta does not display it again.

The access token does not expire, but you should rotate it if you suspect it has been compromised.

Add Meta CAPI in PixelsCleared

1. Open the PixelsCleared dashboard.
2. Go to Gateway > Destinations.
3. Click Add Destination and select Meta Conversions API.
4. Paste your Pixel ID and Access Token into the corresponding fields.
5. Choose which event types to forward (for example, PageView, Lead, Purchase, CompleteRegistration).
6. Click Save.

PixelsCleared validates the credentials immediately. If the connection test succeeds, you will see a green confirmation. If it fails, double-check that the Pixel ID is numeric and the access token starts with EAAB.

Consent Signals

PixelsCleared attaches consent metadata to every event it sends to Meta. You do not need to configure anything extra -- the consent state detected by the widget is included automatically.

Limited Data Use (LDU) mode:

• When consent is granted, PixelsCleared sends events in standard mode with full tracking signals.
• When consent is denied or not detected, PixelsCleared sends events in LDU mode. Meta restricts data processing for these events and does not use them for ad optimization.

Opt-out flag:

• If a visitor explicitly withdraws consent, PixelsCleared sets the opt_out flag on the event. Meta discards these events entirely.

Test Events Tool

After connecting Meta CAPI, verify that events are arriving correctly:

1. Open Meta Events Manager and select your pixel.
2. Go to Test Events tab.
3. In PixelsCleared, enable Test Mode on the Meta CAPI destination (this adds a test event code to outgoing payloads).
4. Visit your website, accept the consent banner, and trigger a tracked action.
5. Return to Meta Events Manager. The event should appear in the Test Events panel within a few seconds, showing the event name, parameters, and match quality score.

Once you see events arriving correctly, disable Test Mode in PixelsCleared so events are sent in production mode.

Match Quality Tips

Meta uses event parameters to match server-side events to Meta users. PixelsCleared automatically forwards available match keys:

• External ID -- a hashed identifier derived from your site
• IP address -- hashed before sending
• User agent -- included when consent is granted

Do not send email addresses, phone numbers, or names through PixelsCleared. The scrubbing engine removes these fields before forwarding, which is intentional for privacy compliance. Match quality will rely on IP and user agent signals.