Skip to content

Connect Meta Conversions API (CAPI)

Last updated: March 18, 20266 min readIntermediateBrandDeveloper

Meta Conversions API (CAPI) enables server-side event tracking that works alongside or independently of the Meta Pixel. Arqam360 forwards consent-compliant events to Meta.

Prerequisites

  • A Meta Business Manager account
  • A Meta Pixel ID
  • A CAPI access token (generated in Meta Events Manager)
  • An Arqam360 Pro or Enterprise plan
1

Go to Integrations

Navigate to Integrations tab in your Arqam360 dashboard.

2

Select Meta CAPI

Click the Meta Conversions API card and click 'Connect'.

3

Enter credentials

Provide your Pixel ID and CAPI Access Token.

4

Test the connection

Click 'Test Connection' to verify events reach Meta.

5

Enable

Toggle the integration to active.

Meta CAPI configuration
1
The Meta CAPI connection form with Pixel ID and access token fields.
Meta CAPI connection modal
Enter your Pixel ID and access token to connect Meta Conversions API.

Limited Data Use (LDU)

When a visitor denies marketing consent, Arqam360 automatically sends the Limited Data Use flag to Meta. This tells Meta to restrict data processing for that event, helping you comply with privacy regulations.

Testing Events

After connecting, go to Meta Events Manager → Test Events. You should see ConsentUpdate events appearing with the correct consent state.

Meta CAPI test connection result
A successful test confirms events are flowing to Meta correctly.
Meta CAPI events are forwarded server-side, so they're not affected by ad blockers. This improves your event match quality and attribution accuracy.

Next Steps

  1. 2Configure routing rules

Was this article helpful?