Campaign Monitor to DuckDB Integration
AI-first ETL from Campaign Monitor into DuckDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads Campaign Monitor into DuckDB
Datrise syncs Campaign Monitor's subscribers, campaigns, lists, segments, email events, and automations into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.
Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.
Ideal for local and notebook analytics without standing up a server.
Endpoints
Campaign Monitor: Email campaign delivery and subscriber management.
DuckDB: In-process analytics database for fast local OLAP.
How Campaign Monitor entities map to DuckDB
| Campaign Monitor entity | DuckDB object | Notes |
|---|---|---|
| subscribers | campaign_monitor_subscribers | id PK · custom fields → JSON or STRUCT columns |
| campaigns | campaign_monitor_campaigns | id PK · linked to campaign_monitor_subscribers |
| lists | campaign_monitor_lists | id PK · linked to campaign_monitor_subscribers |
| segments | campaign_monitor_segments | id PK · linked to campaign_monitor_subscribers |
FAQ
How does Datrise handle Campaign Monitor's custom fields in DuckDB?
Flexible values are stored as JSON or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native DuckDB types.
How does the Campaign Monitor to DuckDB sync stay up to date?
It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.
Related pipelines
More destinations for Campaign Monitor
- Campaign Monitor → Amazon Athena
- Campaign Monitor → Amazon S3 Data Lake
- Campaign Monitor → Azure Data Lake Storage
- Campaign Monitor → Azure Synapse
- Campaign Monitor → Spreadsheets
- Campaign Monitor → Airtable
- Campaign Monitor → CSV Files
- Campaign Monitor → MongoDB
- Campaign Monitor → Supabase
- Campaign Monitor → Neon
- Campaign Monitor → PlanetScale
- Campaign Monitor → Amazon DynamoDB
Early access
Connect Campaign Monitor to DuckDB the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.