Tool · Advertising
Meta Conversions API integrations across CDPs
Directory data as of October 18, 2026
13 of the 44 customer data platforms in the CdpHub directory list an integration with Meta Conversions API, with 16 listings between them. Of those platforms, 1 both sends data to Meta Conversions API and reads from it and 12 only send data to it. 14 can run server-side and 1 in the warehouse. 15 of the 16 listings link to their platform's own documentation.
Which CDPs list Meta Conversions API
13 of 44- ActionIQ (sends data to Meta Conversions API)
- Adobe (sends data to Meta Conversions API)
- Bloomreach (sends data to Meta Conversions API)
- Blueshift (sends data to Meta Conversions API)
- Chord (sends data to Meta Conversions API)
- DinMo (sends data to Meta Conversions API)
- Insider One (sends data to Meta Conversions API)
- Lexer (sends data to Meta Conversions API)
- RudderStack (sends data to Meta Conversions API)
- Segment (sends data to Meta Conversions API)
- Snowplow (sends data to Meta Conversions API)
- Treasure AI (sends data to Meta Conversions API and reads from it)
- Zeotap (sends data to Meta Conversions API)
Not listed by 31 CDPs: 6sense, Amperity, BlueConic, Braze, CaliberMind, CleverTap, Fivetran Activations, Hightouch, Informatica, Klaviyo, Leadspace, Listrak, Lytics, Microsoft Dynamics 365 Customer Insights, mParticle, NICE, Odie, Ometria, Optimizely, Oracle, Redpoint Global, Salesforce Data 360, SAP CDP, SAP Engagement Cloud, SAS, Simon Data, Spotler ActivatePro, Tealium, Teradata, Upland BlueVenn and Zeta Global.
How each CDP connects to Meta Conversions API
13 CDPs · 16 listingsActionIQ (sends data to Meta Conversions API)1 listing
Facebook Conversions API
Adobe Experience Platform (sends data to Meta Conversions API)1 listing
Facebook Conversions API. Sends events server-side to the Facebook (Meta) Conversions API through event forwarding, tied to a Meta Pixel ID, to improve ad targeting and measurement.
Bloomreach (sends data to Meta Conversions API)1 listing
Sends purchase and other conversion events from Bloomreach scenarios to Meta's Conversions API through an action node, with hashed customer details and deduplication against the pixel.
Blueshift (sends data to Meta Conversions API)1 listing
Sends offline conversion events such as in-store purchases from Blueshift campaign journeys to Meta through the Conversions API, using a pixel ID, access token and cloud app template.
Chord (sends data to Meta Conversions API)1 listing
Sends Chord page and commerce events to Meta's Conversions API from the server with a pixel ID and system user token, letting Meta deduplicate them against the pixel by event ID.
DinMo (sends data to Meta Conversions API)1 listing
Sends online, offline or CRM lead conversion events from DinMo event segments to a Meta dataset through the Conversions API, one event type and action source per activation.
Insider One (sends data to Meta Conversions API)2 listings
Click to WhatsApp ads. Reports website and app purchases by shoppers who arrived through Click-to-WhatsApp ads to Meta's Conversions API automatically, so Insider One customers see ROI in Ads Manager.
MindBehind offline events. Sends add-to-cart and purchase events from conversations on Insider One's MindBehind conversational platform to a Meta Pixel dataset as offline Conversions API events.
Lexer (sends data to Meta Conversions API)2 listings
Offline conversions. Sends in-store purchases from a Lexer dataset to a Meta offline dataset through the Conversions API once a day, with Limited Data Use on, so Facebook can attribute store sales to ads.
Online conversions. Sends website purchase events from a Lexer dataset to a Meta web dataset through the Conversions API each day, server side, to credit online sales to Facebook and Instagram ads.
RudderStack (sends data to Meta Conversions API)1 listing
Facebook Conversions API. Sends RudderStack events server-side to Facebook through the Conversions API, for ad measurement and optimization that doesn't rely on the browser pixel.
Segment (sends data to Meta Conversions API)1 listing
Facebook Conversions API (Actions). Sends Segment data to Facebook Conversions API for advertising through Actions such as Custom Event, Purchase and Search.
Snowplow (sends data to Meta Conversions API)1 listing
Sends Snowplow events to Meta's Conversions API for ad measurement and optimization, one event per request, passing the user ID and the click and browser IDs from Meta cookies for matching.
Treasure AI (sends data to Meta Conversions API and reads from it)2 listings
Export. Sends conversion events such as purchases and registrations from Treasure Data job results to Facebook through the Conversions API, including in-store offline events and web server logs.
Dataset quality import. Imports Meta Conversions API quality metrics, such as event match quality, event coverage, deduplication and additional conversions reported, for website or offline datasets into Treasure Data.
Zeotap (sends data to Meta Conversions API)1 listing
Streams web and app conversion events, such as purchases, sign-ups and page views, from Zeotap Journeys to Facebook's Conversions API, with event IDs to deduplicate against the Pixel.
Other Advertising tools
All tools on two or more CDPs →About these numbers
CdpHub documents each integration from the platform's own catalog, so a listing records what the platform says it supports, not a test of the connector. Each one notes which way data flows and where the integration runs. A platform can list more than one connector for Meta Conversions API, so listings can outnumber platforms; a platform that both sends data to Meta Conversions API and reads from it is counted once, as doing both. The rank orders all 2,365 tools in the directory by how many platforms list them; tools listed on the same number of platforms share a rank. Counts are updated as catalogs change; this page reflects the directory as of October 18, 2026. CdpHub is independent and not affiliated with Meta Conversions API or any platform listed.
Connecting Meta Conversions API to a CDP?
Vendor-neutral help choosing the CDP that fits how you use Meta Conversions API, and getting the connection running in your stack.