Meta Conversions API (CAPI)

Enhance your tracking reliability and ensure accurate conversion data with our server-side integration for Meta (Facebook) via the Conversions API (CAPI).

Server-side tracking requires an active Grow or Business plan.

Check our pricing page for more details.

Browser-side tracking—such as the standard Meta Pixel—is increasingly limited by ad-blockers, browser privacy features (like ITP), and user cookie settings. This can lead to significant data loss and inaccurate campaign reporting.

Our Meta CAPI integration solves this by sending your conversion events directly from our servers to Meta.

Capture conversions even when users employ ad-blockers or privacy-focused browsers, ensuring no event goes untracked.

Higher data quality allows for more accurate conversion attribution and better optimization of your Facebook ad campaigns. We automatically capture and send _fbp and _fbc cookies, IP Address, User Agent, and Page URL to maximize Meta's Event Match Quality (EMQ).

When using both the Meta Pixel (browser) and CAPI (server), we generate a unique Event ID for every form submission. Meta uses this ID to deduplicate events, preventing double-counting.

• Consent-Aware: We automatically respect user consent preferences collected on your forms, ensuring your tracking practices remain compliant with privacy regulations.

• Secure Transmission: Data is sent directly from our secure servers to Meta, minimizing the surface area for tracking interference and ensuring the integrity of your data.

1. Event Collection: When a user submits your form, we securely capture the necessary conversion metadata alongside user consent status.

2. Secure Server-to-Server Transfer: Alongside browser events, our platform securely sends this event data directly to Meta's Conversions API.

3. Accurate Reporting: Meta receives the verified event, allowing you to track conversions reliably within your Meta Ads Manager.

Our platform integrates seamlessly with the Google Consent Mode v2 standard. We automatically inspect the window.dataLayer on your site.

For server-side tracking events to be dispatched to Meta, the user must have granted consent for both ad_storage and ad_user_data. If consent is missing or denied, no server-side events are sent.

To start using Meta CAPI:

Navigate to your form settings and select the Conversions tracking section. Select an existing Facebook conversion or click the "Add conversion" button.

Select Facebook conversion (event) type and name. After the event type is selected, you will see the "Configure server-side tracking" button, click on it.

In the pop-up window click on the "Add Pixel" button.

Enter the details for your pixel:

• Pixel Name - describe the name of your pixel; this will only be visible within your dashboard.

• Pixel ID - copy and paste your pixel ID from the Facebook Events Manager dashboard.

• Pixel Access Token - in the Facebook Events Manager, go to the pixel settings and find the "Generate access token" button. Generate a new token and copy the value.

Click on the "Add" button.

You'll be able to use this configured pixel in other conversions and forms across your organization.

Please note that all organization members will be able to view your pixel settings.

After your pixel is created, click the "Use this pixel" link to attach it to your front-end conversion event.

Save your form.

You can verify that Meta is receiving your server-side events properly using the Test Events tool:

1. Go to your Meta Events Manager and open the "Test events" tab for your dataset.

2. From the "Select channel" dropdown, choose "Website".

3. Expand the "Confirm your server’s events are set up correctly" section.

4. Copy the Test Event Code (it looks like TESTxxxxx).

5. In your form's server-side tracking settings, paste this code into the "Test Event Code" field.

6. Submit a test entry on your form. Make sure you have granted consent on your website (both ad_storage and ad_user_data), otherwise the event will not fire.

7. The event should appear in your Meta Events Manager within a few moments.

Remember to remove the Test Event Code from your form settings once testing is complete, or Meta will continue to treat real conversions as test events.