CSV state operation exports
Export audience membership changes as CSV state operations for local inspection, manual upload, suppression lists, and partner delivery.
Audience membershipState exports
// ACTIVATION DATA EXPORT
Export activation data to CSV files
Use Condor RETL to write audience CSV exports, event CSV exports, generic payload files, and manifests for local inspection, partner handoff, QA, and file-based activation.
// DESTINATION CAPABILITIES
Create file-based activation exports
The File connector is a local export destination, not a SaaS marketing destination. It writes activation-ready CSV outputs and manifests so teams can inspect, share, archive, or route audience and event data outside an API sync.
Audience CSV export
Write state-based audience membership changes to CSV files for manual upload, partner workflows, QA, or downstream activation systems.
Event CSV export
Export selected event rows to CSV for campaign measurement, partner delivery, local testing, or file-based event activation.
Manifest-backed delivery
Produce CSV outputs with manifests so each activation data export is easier to inspect, reconcile, and operationalize.
// WHAT YOU CAN SEND
What you can send to File
Turn warehouse-defined customer data into activation-ready audiences, events, and campaign signals.
Audience membership changes
Export upserts and removals as CSV state operations for audience upload and local activation workflows.
Suppression lists
Create audience CSV exports for customer exclusions, ineligible users, or campaign suppression segments.
Retargeting segments
Write retargeting pools from lifecycle state, product interest, recent engagement, or model scores.
Event rows
Export purchase, signup, lifecycle, campaign, or measurement events as CSV event imports.
Generic activation payloads
Write flexible payload exports for destinations, partners, or workflows that need file-based activation data.
Export manifests
Include manifest files that describe CSV outputs for inspection, reconciliation, and operational handoff.
// WHAT YOU CAN ACTIVATE
What you can sync to File
Use the File connector to export activation-ready audience CSVs, event CSVs, generic payloads, and manifests for local or file-based delivery workflows.
Audience sync
Conversion events
File exports
CSV event exports
Export selected event rows as CSV files for measurement, lifecycle activation, partner ingestion, or local QA workflows.
Event exports
Generic payload export
Write flexible activation payloads with CSV outputs and manifests for destinations or workflows that need file-based delivery.
Generic payload exportCSV plus manifest
// USE CASES
Common File activation workflows
Paid media workflows that depend on current customer audiences, campaign signals, and repeatable delivery.
Create audience CSV exports
Turn warehouse-defined audience logic into CSV files for manual uploads, partner delivery, or file-based marketing activation.
Export event data for activation
Write event CSV exports for campaign measurement, lifecycle workflows, local QA, or downstream event ingestion.
Preview activation jobs locally
Use file exports to inspect exactly what an activation workflow will send before connecting to an API destination.
Hand off data to partners
Package audience, event, or generic payload exports for vendors and partners that still use CSV-based delivery.
Archive activation outputs
Preserve manifests and CSV files for audit, reconciliation, repeatability, and operational review.
Bridge non-API destinations
Use reverse ETL file export when a destination requires local files, batch ingestion, or manual upload instead of direct SaaS sync.
// RELATED
File source options
Snowflake source
Export activation-ready audience and event data shaped from Snowflake.
Meta destination
Use a direct paid media destination when you are ready to sync audiences and events through an API.
Condor RETL docs
Read the developer docs for Condor RETL concepts, examples, and runtime commands.
Deliver syncs to File
Schedule a demo and see how Condor RETL can connect your source rows to downstream activation.