Customer File Custom Audiences
Keep Meta Custom Audiences aligned with the audiences your team defines in the warehouse. Use it for suppression lists, retargeting pools, and high-value customer segments.
// META AUDIENCE SYNC
Use Condor RETL to send first-party customer audiences and conversion events from your warehouse to Meta for targeting, suppression, lookalikes, and campaign optimization.
// DESTINATION CAPABILITIES
The Meta connector turns warehouse-defined customer data into paid media activation workflows. Keep Custom Audiences fresh, send conversion events, and operate every sync with planning and delivery evidence.
Create and refresh Meta Customer File Custom Audiences from customer lists, suppression segments, retargeting pools, and high-value cohorts defined in your warehouse.
Send selected conversion events to Meta so campaign optimization can use customer activity prepared by your data team.
Refresh Meta audiences and events on a repeatable cadence with dry-run planning, receipts, and outcomes for every activation run.
// WHAT YOU CAN SEND
Turn warehouse-defined customer data into activation-ready audiences, events, and campaign signals.
Turn warehouse customer records into first-party audience lists for Meta Ads Manager.
Exclude existing customers, recent buyers, or ineligible users from acquisition campaigns.
Build audiences around recent activity, lifecycle state, product interest, or campaign engagement.
Use high-value customers, loyal buyers, or predicted best customers as stronger lookalike seeds.
Activate CLV, churn, affinity, lifecycle, and next-best-action segments in paid media workflows.
Send selected purchase, signup, lifecycle, or campaign events into Meta Conversions API.
// WHAT YOU CAN ACTIVATE
Use the Meta connector to keep paid media audiences current and send conversion events from warehouse-shaped customer data.
Keep Meta Custom Audiences aligned with the audiences your team defines in the warehouse. Use it for suppression lists, retargeting pools, and high-value customer segments.
Send selected conversion events to Meta Conversions API so event-based optimization can use customer activity prepared by your data team.
// USE CASES
Paid media workflows that depend on current customer audiences, campaign signals, and repeatable delivery.
Keep acquisition campaigns focused by excluding customers who already purchased, subscribed, or entered an ineligible state.
Refresh retargeting audiences from product interest, cart behavior, lifecycle state, or recent engagement modeled in the warehouse.
Send high-value customer segments to Meta as seed audiences for prospecting and expansion campaigns.
Route selected conversion events into Meta Conversions API so optimization has better server-side customer signals.
Run recurring audience updates so Meta campaigns use current warehouse data without manual uploads.
Use dry-run planning, receipts, and outcomes to understand what was sent and how each activation run completed.
// RELATED
Sync Snowflake audiences to Meta Custom Audiences for targeting, suppression, and lookalike workflows.
Activate warehouse-defined audiences from Snowflake into Meta and other marketing destinations.
Read the developer docs for Condor RETL concepts, examples, and runtime commands.
Schedule a demo and see how Condor RETL can connect your source rows to downstream activation.