Campaign Monitor to ClickHouse Integration
AI-first ETL from Campaign Monitor into ClickHouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Campaign Monitor into ClickHouse
Datrise syncs Campaign Monitor's subscribers, campaigns, lists, segments, email events, and automations into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.
Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.
Ideal for high-volume event analytics that need sub-second aggregation.
Endpoints
Campaign Monitor: Email campaign delivery and subscriber management.
ClickHouse: Columnar OLAP engine for fast aggregations.
How Campaign Monitor entities map to ClickHouse
| Campaign Monitor entity | ClickHouse object | Notes |
|---|---|---|
| subscribers | campaign_monitor_subscribers | id PK · custom fields → JSON or Map 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 ClickHouse?
Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.
How does the Campaign Monitor to ClickHouse sync stay up to date?
It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.
Related pipelines
More destinations for Campaign Monitor
- Campaign Monitor → DuckDB
- 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
Early access
Connect Campaign Monitor to ClickHouse 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.