New: The Agentic CDP

·Read the analysis

Tool · Advertising

Meta Ads integrations across CDPs

Directory data as of October 18, 2026

39 of the 44 customer data platforms in the CdpHub directory list an integration with Meta Ads, with 102 listings between them. Of those platforms, 21 both send data to Meta Ads and read from it, 17 only send data to it and 1 only reads from it. 83 can run server-side, 15 client-side and 9 in the warehouse. 100 of the 102 listings link to their platform's own documentation.

39of 44 CDPs list Meta Ads
102listings across them
21send data to Meta Ads and read from it
#1most listed of 2,243 tools

Which CDPs list Meta Ads

39 of 44
Sends data to Meta Ads Reads from Meta Ads, or uses it as a source Does both

Not listed by 5 CDPs: Informatica, Leadspace, Odie, SAP CDP and Teradata.

How each CDP connects to Meta Ads

39 CDPs · 102 listings
6sense (sends data to Meta Ads)1 listing
6sense → Meta Ads

Syncs 6sense segments to Meta ad accounts as custom audiences for Facebook and Instagram campaigns, after an administrator connects a Meta Business Manager account over OAuth.

All 6sense integrations →
ActionIQ (sends data to Meta Ads)2 listings
ActionIQ → Meta Ads

Facebook Ads

ActionIQ → Meta Ads

Facebook Conversions API

All ActionIQ integrations →
Adobe Experience Platform (sends data to Meta Ads and reads from it)4 listings
Adobe → Meta Ads

Facebook (Custom Audiences). Sends Real-Time CDP audiences to Facebook Custom Audiences, matched by hashed email, for targeting and suppression on Facebook, Instagram, Messenger and Audience Network.

Adobe → Meta Ads

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.

Adobe → Meta Ads

Facebook Pixel (Meta Pixel). Adds the Facebook Pixel (Meta Pixel) through Adobe tags to send site conversions to Meta Ads Manager, with event IDs to deduplicate against the Conversions API.

Meta Ads → Adobe

Facebook (Meta Ads source). Brings Meta Ads performance insights for Facebook and Instagram, down to the ad level, into Experience Platform for mix modeling, journey and creative analysis.

All Adobe Experience Platform integrations →
Amperity (sends data to Meta Ads)2 listings
Amperity → Meta Ads

Custom audiences. Sends custom audiences from Amperity to Meta Ads Manager, swapping members without resetting ad set learning, for Facebook, Instagram, Messenger and WhatsApp.

Amperity → Meta Ads

Offline events. Sends recent transaction events from Amperity to Meta through the Conversions API to track offline conversions from campaigns.

All Amperity integrations →
Bloomreach (sends data to Meta Ads and reads from it)3 listings
Bloomreach → Meta Ads

Custom audiences. Adds or removes Bloomreach customers in Facebook and Instagram custom audiences, including value-based ones, by hashed email or phone or by mobile ID, or loads the Facebook pixel via Tag Manager.

Bloomreach → Meta Ads

Meta Conversions API. 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.

Meta Ads → Bloomreach

Lead Ads. Captures Facebook and Instagram Lead Ads form submissions from a connected Facebook page as facebook_lead events in Bloomreach, including custom answers and disclaimer responses.

All Bloomreach integrations →
BlueConic (sends data to Meta Ads and reads from it)2 listings
BlueConic → Meta Ads

Audiences and Conversions API. Sends BlueConic segments to Meta as custom audiences, exports timeline events through the Conversions API in batches and passes profile data to the Facebook pixel in real time.

Meta Ads → BlueConic

Lead ads. Imports lead form answers from Facebook pages into BlueConic profiles on a schedule, matching people by email and optionally creating new profiles for unknown leads.

All BlueConic integrations →
Blueshift (sends data to Meta Ads and reads from it)3 listings
Blueshift → Meta Ads

Facebook (custom audiences). Syncs Blueshift segments to Facebook Custom Audiences with multikey matching on emails, phones, names, birth dates, locations and mobile ad IDs, including value-based audiences.

Blueshift → Meta Ads

Meta Conversions API. 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.

Meta Ads → Blueshift

Facebook (Lead Ads). Captures leads from Facebook Lead Ads on the pages you pick into Blueshift as identify events, saving the form, lead and page IDs on profiles that get no customer ID.

All Blueshift integrations →
Braze (sends data to Meta Ads and reads from it)3 listings
Braze → Meta Ads

Facebook (audience export). Exports a Braze segment to Facebook as a one-time, static custom audience for retargeting, exclusion lists or lookalike audiences.

Braze → Meta Ads

Facebook (Audience Sync). Adds Braze users to Facebook custom audiences from Canvas steps, matched on fields such as email, phone and name, to start or suppress ads.

Meta Ads → Braze

Facebook (Lead Ads via Zapier). Imports leads captured by Facebook Lead Ads into Braze through a Zapier workflow and logs a custom event for each one, for quick follow-up messages.

All Braze integrations →
CaliberMind (reads from Meta Ads)1 listing
Meta Ads → CaliberMind

Facebook. Pulls Facebook ad spend into CaliberMind campaign and performance tables, and lead gen form leads through a separate push connector, once a Facebook admin connects over OAuth.

All CaliberMind integrations →
Chord (sends data to Meta Ads)3 listings
Chord → Meta Ads

Custom audiences and conversions. Syncs Chord data to Facebook custom audiences and conversions through Data Activations, connected by OAuth or by a system user token with ads_management, which Chord prefers.

Chord → Meta Ads

Pixel. Loads the Meta Pixel through Chord's CDP and fires standard events like PageView, AddToCart and Purchase to one or several pixel IDs, for example one per agency or brand.

Chord → Meta Ads

Meta Conversions API. 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.

All Chord integrations →
CleverTap (sends data to Meta Ads and reads from it)3 listings
CleverTap → Meta Ads

Custom audiences. Connects Facebook Ads accounts to CleverTap for remarketing so segments sync to Facebook audiences, once an admin accepts the Custom Audiences terms and authorizes CleverTap.

Meta Ads → CleverTap

Ad cost data. Pulls per-campaign and per-user cost data from a connected Facebook Ads account into CleverTap every two hours, to compare campaign spend with revenue from acquired users.

Meta Ads → CleverTap

Lead Ads. Sends Facebook Lead Ads form submissions to CleverTap through Zapier as new profiles and lead events, and can mark converted users on their profiles.

All CleverTap integrations →
DinMo (sends data to Meta Ads and reads from it)3 listings
DinMo → Meta Ads

Custom audiences. Creates Meta audiences in a chosen ad account from DinMo segments and keeps membership current using emails and optional phone, name, gender and location fields, plain or hashed.

DinMo → Meta Ads

Meta Conversions API. 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.

Meta Ads → DinMo

Source. Pulls Meta (Facebook) Ads accounts, campaigns, ad sets, ads, creatives, custom conversions and reports in through DinMo Ingest, stored in each ad account's time zone.

All DinMo integrations →
Fivetran Activations (sends data to Meta Ads)2 listings
Fivetran Activations → Meta Ads

Audiences and Conversions API. Syncs custom audiences and Conversions API events, from web and app events to offline conversions, from Fivetran Activations to Meta Ads over OAuth or a system user token.

Fivetran Activations → Meta Ads

Product catalog. Keeps Facebook product catalog items and hotels in step with warehouse data from Fivetran Activations, for dynamic ads and Instagram Shopping, using a system user token.

All Fivetran Activations integrations →
Hightouch (sends data to Meta Ads and reads from it)3 listings
Hightouch → Meta Ads

Conversions API. Sends web, app and offline conversion events from your warehouse to Meta's Conversions API.

Hightouch → Meta Ads

Custom audiences. Syncs first-party audiences from your warehouse to Meta Ads Manager for targeting, value-based lookalikes and suppression.

Meta Ads → Hightouch

Audience size report. Writes a daily snapshot of Meta Custom Audiences sizes, including audiences Hightouch doesn't sync, to the hightouch_audit schema of a warehouse source on the Lightning sync engine.

All Hightouch integrations →
Insider One (sends data to Meta Ads)4 listings
Insider One → Meta Ads

Journey audiences. Adds people to a Facebook Custom Audience when they reach a Facebook element in an Insider One Architect journey, matched on email or phone through the Facebook Ads API.

Insider One → Meta Ads

Remarketing segments. Syncs Insider One dynamic segments to Facebook Ads as Custom Audiences through the Marketing API, hashing email, phone and optional attributes with SHA-256 and updating membership nightly.

Insider One → Meta Ads

Meta Conversions API (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.

Insider One → Meta Ads

Meta Conversions API (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.

All Insider One integrations →
Klaviyo (sends data to Meta Ads and reads from it)1 listing
Klaviyo ⇄ Meta Ads

Pushes Klaviyo lists and segments into Meta custom audiences for ad targeting and lookalikes, and pulls Meta Lead Ad sign-ups for email and SMS into Klaviyo.

All Klaviyo integrations →
Lexer (sends data to Meta Ads and reads from it)4 listings
Lexer → Meta Ads

Custom audiences. Sends Lexer segments to Facebook and Instagram ad accounts as custom audiences through the API, with optional always-on updates and multi-match on names, country and postcode.

Lexer → Meta Ads

Meta Conversions API (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.

Lexer → Meta Ads

Meta Conversions API (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.

Lexer ⇄ Meta Ads

Facebook (Pages). Brings posts, comments and messages from your Facebook Business Pages into Lexer, plus content from up to 15 monitored public Pages, after a Page admin signs in with Facebook.

All Lexer integrations →
Listrak (sends data to Meta Ads and reads from it)2 listings
Listrak → Meta Ads

Custom audiences. Syncs saved and Listrak CRM audiences to a Facebook ad account as custom audiences through Listrak Exchange, where Facebook matches them to its users.

Meta Ads → Listrak

Lead Ads. Syncs Meta Lead Ad subscribers from a connected Facebook Page into Listrak in real time through Listrak Exchange, mapping each lead form to a subscription point.

All Listrak integrations →
Lytics (sends data to Meta Ads and reads from it)2 listings
Lytics → Meta Ads

JavaScript tag plugin. Sends a visitor's Lytics audiences to Facebook from the browser as a named event through the Facebook JavaScript SDK, using the Lytics tag's facebook.ads plugin.

Lytics ⇄ Meta Ads

Audiences and Conversions API. Syncs Lytics audiences to Meta custom and website audiences, sends audience events to the Conversions API, and imports Meta ad sets with their metrics as Experiences.

All Lytics integrations →
Microsoft Dynamics 365 Customer Insights (sends data to Meta Ads)1 listing
Dynamics 365 → Meta Ads

Updates a Facebook Ads Manager customer-list custom audience from Customer Insights - Data segments with hashed email, phone or address data, for Facebook and Instagram ads.

All Microsoft Dynamics 365 Customer Insights integrations →
mParticle (sends data to Meta Ads)3 listings
mParticle → Meta Ads

Facebook (custom audiences). Sends mParticle audiences to Facebook Ads Manager as custom audiences for targeting existing or prospective customers.

mParticle → Meta Ads

Facebook (events). Forwards mParticle events to Facebook for ad conversion tracking from apps and the web.

mParticle → Meta Ads

Facebook (offline conversions). Forwards offline purchases uploaded to mParticle through a custom feed to Facebook, now through the Conversions API.

All mParticle integrations →
NICE (sends data to Meta Ads and reads from it)1 listing
NICE ⇄ Meta Ads

Facebook. Syncs posts, comments and likes on your Facebook page into NICE CXone in near real time so agents can reply, hide or delete content, starting with the last 20 days.

All NICE integrations →
Ometria (sends data to Meta Ads and reads from it)2 listings
Ometria → Meta Ads

Custom audiences. Keeps Facebook Custom Audiences in step with Ometria segments about every hour, sending details such as email and phone, and only opted-in contacts by default.

Meta Ads → Ometria

Lead Ads. Imports leads from a Facebook Lead Ads form into Ometria as contacts, mapping fields such as email, phone and opt-in status, with one connection per page and form.

All Ometria integrations →
Optimizely (sends data to Meta Ads and reads from it)2 listings
Optimizely → Meta Ads

Custom audiences. Uploads hashed emails from ODP standard audiences to Facebook as customer lists every day, for targeting on the news feed, Instagram and Audience Network, with optional lookalikes.

Meta Ads → Optimizely

Lead Ads. Collects new leads from Facebook lead ad forms into ODP profiles as they are submitted, mapping form questions to fields, opting in the email or phone and optionally adding them to a list.

All Optimizely integrations →
Oracle (sends data to Meta Ads)1 listing
Oracle → Meta Ads

Facebook. Delivers Oracle Unity segments to Facebook as Custom Lists keyed on hashed email, hashing plain addresses first, so matched audiences appear in Business Manager (new connector since September 2024).

All Oracle integrations →
Redpoint Global (sends data to Meta Ads)1 listing
Redpoint Global → Meta Ads

Creates, appends to or deletes from Facebook custom audiences with mapped Redpoint Interaction customer data, and uploads offline events to a Facebook dataset.

All Redpoint Global integrations →
RudderStack (sends data to Meta Ads and reads from it)5 listings
RudderStack → Meta Ads

Facebook Ads (custom audiences). Creates and updates Facebook custom audiences from your warehouse with RudderStack, matching people by hashed identifiers for ad targeting.

RudderStack → Meta Ads

Facebook App Events. Sends app events, screens and page views from RudderStack to Facebook App Events for ad measurement, in cloud mode or in device mode on mobile.

RudderStack → Meta Ads

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.

RudderStack → Meta Ads

Facebook Pixel. Sends RudderStack page views and events to Facebook Pixel for ad conversion tracking and audiences, in cloud mode or on the web in device mode.

Meta Ads → RudderStack

Facebook Lead Ads. Pulls leads from Facebook Lead Ads forms into RudderStack as they come in, through an OAuth connection (beta).

All RudderStack integrations →
Salesforce Data 360 (sends data to Meta Ads and reads from it)3 listings
Salesforce → Meta Ads

Audience activation. Sends segments built in Data 360 to Meta Ads Manager as custom audiences, hashing customer data with SHA-256 and updating incrementally (Ad Audiences add-on required).

Salesforce ⇄ Meta Ads

Campaign data. Brings Meta Ads data into Data 360 in batches, and Salesforce lists the connection as two-way.

Meta Ads → Salesforce

Facebook (Pages data). Brings Facebook Page posts, comments, events, videos and page and post insights into Data 360 in batches or through Zero Copy query federation (beta).

All Salesforce Data 360 integrations →
SAP Engagement Cloud (sends data to Meta Ads)1 listing
SAP Engagement Cloud → Meta Ads

Matches SAP Emarsys contacts to profiles on Facebook and Instagram for retargeting, CRM ads and lookalike audiences in automated, real-time ad campaigns.

All SAP Engagement Cloud integrations →
SAS (sends data to Meta Ads)1 listing
SAS → Meta Ads

Facebook. Uploads custom audiences built in SAS Customer Intelligence 360 to Facebook Ads through Facebook's marketing APIs when a task runs, to reach people on Facebook, Instagram, Messenger and WhatsApp.

All SAS integrations →
Segment (sends data to Meta Ads and reads from it)7 listings
Segment → Meta Ads

Facebook App Events. Sends track calls from Segment to Facebook App Events for advertising and analytics in cloud or device mode.

Segment → Meta Ads

Facebook Conversions API (Actions). Sends Segment data to Facebook Conversions API for advertising through Actions such as Custom Event, Purchase and Search.

Segment → Meta Ads

Facebook Custom Audiences (Actions). Syncs Segment audiences to Facebook Custom Audiences, using Actions such as Sync Audience (beta).

Segment → Meta Ads

Facebook Pixel. Sends identify, track and page calls from Segment to Facebook Pixel for advertising in device mode.

Segment → Meta Ads

Personas Facebook Custom Audiences. Sends track calls from Segment to Personas Facebook Custom Audiences for advertising in cloud mode.

Meta Ads → Segment

Facebook Ads (source). Pulls Facebook Ads objects into Segment on a schedule for syncing to a warehouse.

Meta Ads → Segment

Facebook Lead Ads. Sends Facebook Lead Ads events into Segment as they happen, ready to route to other tools (beta).

All Segment integrations →
Simon Data (sends data to Meta Ads)1 listing
Simon Data → Meta Ads

Facebook. Creates and updates Facebook custom and value-based audiences from Simon Data segments over OAuth, adding multi-key contact fields to raise match rates, for lookalikes and retargeting.

All Simon Data integrations →
Snowplow (sends data to Meta Ads)1 listing
Snowplow → Meta Ads

Meta Conversions API. 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.

All Snowplow integrations →
Spotler ActivatePro (sends data to Meta Ads)1 listing
Spotler ActivatePro → Meta Ads

Facebook. Requires a Business-type Facebook developer app with Ads Management Standard Access, approved through App Review, to link CrossEngage with Facebook Custom Audiences.

All Spotler ActivatePro integrations →
Tealium (sends data to Meta Ads and reads from it)9 listings
Tealium → Meta Ads

Facebook (App Analytics tag). Adds Facebook App Events through Tealium iQ to measure app performance, Facebook ad conversions and audiences.

Tealium → Meta Ads

Facebook (App Events connector). Sends app events to Facebook through the Marketing API from AudienceStream or EventStream, for app ad measurement and optimization.

Tealium → Meta Ads

Facebook (Buttons tag). Adds Facebook Like and share buttons through Tealium iQ.

Tealium → Meta Ads

Facebook (Conversions connector). Sends web, advanced measurement and CRM events to the Facebook Conversions API from AudienceStream or EventStream, with deduplication against the Facebook pixel.

Tealium → Meta Ads

Facebook (Custom Audiences connector, customer credentials). Adds users to or removes them from Facebook Custom Audiences, or opts them out of all of them, from AudienceStream, using your own Facebook credentials.

Tealium → Meta Ads

Facebook (Custom Audiences connector). Adds users to or removes them from Facebook Custom Audiences, or opts them out of all of them, from AudienceStream, in batches.

Tealium → Meta Ads

Facebook (Mobile Remote Command). Hands app events from Tealium's Android and iOS SDKs to the Facebook SDK through a remote command that logs purchases, product items and standard events and sets user data.

Tealium → Meta Ads

Facebook (Pixel). Adds the Facebook (Meta) pixel through Tealium iQ to track custom-audience and conversion events, with several events per page.

Tealium ⇄ Meta Ads

Facebook (Lead Ads via Data Connect). Imports new Facebook Lead Ads leads into Tealium with a Data Connect recipe and sends lead events back to Facebook through the Facebook Conversions connector.

All Tealium integrations →
Treasure AI (sends data to Meta Ads and reads from it)6 listings
Treasure AI → Meta Ads

Custom audiences. Writes Treasure Data job results to Facebook Custom Audiences, normalizing and SHA-256 hashing customer identifiers unless already prepared, over OAuth or a system user token.

Treasure AI → Meta Ads

Meta Conversions API (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.

Meta Ads → Treasure AI

Facebook (Page Insights import). Imports Facebook Page, post and video insights, comments, and conversation messages and participants into Treasure Data over an OAuth connection.

Meta Ads → Treasure AI

Ads Insights import. Imports Facebook ad results at the campaign, ad set or ad level from Ads Insights into Treasure Data over OAuth, with breakdowns, attribution windows and incremental date ranges.

Meta Ads → Treasure AI

Lead Ads import. Imports leads from Facebook Lead Ads forms on a Page or ad account into Treasure Data over OAuth or an access token, by ad ID or form ID, with optional incremental loads.

Meta Ads → Treasure AI

Meta Conversions API (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.

All Treasure AI integrations →
Upland BlueVenn (sends data to Meta Ads)1 listing
Upland BlueVenn → Meta Ads

Facebook. Sends BlueVenn Engage audiences to Facebook for Business for saved ad campaigns and custom audiences (add, remove or sync), and uploads offline sales for attribution, covering Instagram ads too.

All Upland BlueVenn integrations →
Zeotap (sends data to Meta Ads)6 listings
Zeotap → Meta Ads

Custom audiences, OAuth. Activates Zeotap audiences as Custom Audiences in a Facebook ad account after a one-time OAuth sign-in rather than a pasted access token, for targeting or suppression in Meta campaigns.

Zeotap → Meta Ads

Custom audiences. Pushes Zeotap segments into Meta as Custom Audiences, matched on hashed emails or phones, MAIDs or external IDs, using a System User or Page access token, and removes users who drop out.

Zeotap → Meta Ads

MAID audiences. Sends Zeotap audiences of mobile advertising IDs to a Facebook ad account linked to Business Manager for targeting, once the Custom Audience terms have been accepted.

Zeotap → Meta Ads

Offline conversions. Sends offline conversions, such as in-store purchases or offline leads, with hashed customer identifiers from Zeotap audiences to Meta for better ad attribution and optimization.

Zeotap → Meta Ads

Product catalog. Sends Zeotap product records, such as IDs, titles, prices and availability, into a Facebook Product Catalog held in Commerce Manager, so dynamic ads can promote them.

Zeotap → Meta Ads

Meta Conversions API. 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.

All Zeotap integrations →
Zeta Global (sends data to Meta Ads and reads from it)1 listing
Zeta Global ⇄ Meta Ads

Sends Zeta's customer and prospect segments to Meta as hashed Custom Audiences by export or Experience action, and brings Facebook and Instagram Lead Ads submissions back as Zeta events.

All Zeta Global integrations →

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 Ads, so listings can outnumber platforms; a platform that both sends data to Meta Ads and reads from it is counted once, as doing both. The rank orders all 2,243 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 Ads or any platform listed.

Connecting Meta Ads to a CDP?

Vendor-neutral help choosing the CDP that fits how you use Meta Ads, and getting the connection running in your stack.

Talk to CdpHub →

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Read our cookie policy