// DUCKDB LOCAL ACTIVATION
Build and test activation workflows with DuckDB
Use DuckDB as a local, embedded source for shaping audience, event, and profile rows before sending planned syncs to supported marketing destinations.
// SOURCE CAPABILITIES
Use DuckDB for local and embedded activation inputs
The DuckDB source is built for local development, examples, QA, and embedded workflows where activation rows can be shaped in an inspectable database file. It is not positioned as a cloud warehouse replacement; use it to prototype, validate, and operate smaller local RETL jobs.
Local audience shaping
Build customer lists, suppression audiences, retargeting pools, and high-value segments from local DuckDB tables or files.
Inspectable RETL development
Use a local database to test SQL, dry-run plans, receipts, and destination payloads before moving the workflow to a larger source system.
Embedded activation inputs
Prepare audience membership, selected event rows, and profile or list fields for destinations that support those sync surfaces.
// ACTIVATION DESTINATIONS
Where DuckDB audiences can go
Use DuckDB as the source of truth for audience membership, customer traits, predictive segments, and conversion events that need to reach marketing destinations.
Meta
Sync Custom Audiences and conversion events for paid media activation.
Klaviyo
Send customer profiles and list membership into lifecycle marketing workflows.
Google Ads Data Manager
Activate Customer Match audiences and conversion events through Google Ads Data Manager.
Bing Ads
Sync Microsoft Advertising Customer Lists for acquisition, retargeting, and suppression.
TikTok Ads
Keep TikTok Ads Custom Audiences current from DuckDB-defined segments.
File
Export activation-ready CSV files with manifests for partners, QA, or downstream systems.
// USE CASES
DuckDB activation use cases
Common workflows for using this source connector in customer activation syncs.
Prototype audience sync workflows
Use DuckDB to develop and inspect audience logic for Meta, Google Ads, TikTok Ads, Bing Ads, or file-based exports.
Test lifecycle profile and list sync
Shape local customer attributes and list membership for destinations such as Klaviyo when profile or list sync is supported.
Validate event sync inputs
Prepare selected purchase, signup, campaign, or lifecycle event rows locally before routing them to supported event destinations.
Run local reverse ETL examples
Use DuckDB for demos, development fixtures, QA checks, and embedded workflows where a local database is the right source.
Create activation-ready file exports
Pair DuckDB with the File destination to generate CSV outputs and manifests for local inspection or partner handoff.
Review dry runs and receipts
Inspect planned destination changes and recorded outcomes from a local source before scaling the workflow elsewhere.
// RELATED
Related DuckDB sync links
File destination
Export DuckDB-shaped activation rows to CSV files and manifests for inspection, QA, or handoff.
Meta destination
Use local DuckDB rows to test audience and event activation workflows for Meta.
Condor RETL docs
Read the developer docs for Condor RETL concepts, examples, and runtime commands.
Build DuckDB sync workflows
Schedule a demo and see how Condor RETL can support source-to-destination activation.