Configure Meta Conversions API
Meta Conversions API provides a server-side delivery path for mapped CRM events alongside permitted browser measurement. It does not remove consent obligations or guarantee attribution.
What you need
Section titled “What you need”- Admin or Manager access
- Target Meta dataset or Pixel ID
- Access token permitted to send events to that dataset
- At least one Meta event-name mapping
- Optional Meta Test Event Code for validation
Treat the access token as a secret. Stored tokens are not shown again by Convertly.
Configure
Section titled “Configure”- Open Integrations from the main navigation.
- Find Meta Conversions API and select Setup.
- Enter the Pixel or dataset ID.
- Enter or replace the access token.
- Add the event name for each CRM milestone you intend to send.
- Add a Test Event Code during setup.
- Keep test mode enabled and save.
Example mappings might use Lead for a new lead, QualifiedLead for qualification, and Purchase for a won sale. Use only events that match the workspace’s actual campaign strategy.
Identity and event data
Section titled “Identity and event data”Delivery may include supported click and browser identifiers, normalized and hashed customer identifiers, event time, source URL, CRM deduplication key, lead value, and workspace currency when available and permitted.
A lead does not always require fbclid if another accepted matching strategy is configured, but identifier quality affects matching.
Test and verify
Section titled “Test and verify”Perform one controlled CRM event and review Meta Test Events plus Logs from the Meta Conversions API card or setup page. Check event name, dataset, test code, identifier availability, value, currency, and provider response.
Meta conversion logs are kept separate from Google Ads logs. Clearing one integration’s logs does not clear the other integration’s history.
Browser and server deduplication
Section titled “Browser and server deduplication”If the same event is sent from a browser Pixel and CAPI, use a consistent event identity according to Meta’s deduplication guidance. Test for duplicate events before enabling production delivery.
Meta Lead Ads is configured through its own integration card and can be disconnected without clearing Meta Conversions API settings.