Twitter/X Ads → ClickHouse
AI-first ETL from Twitter/X Ads into ClickHouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Twitter/X Ads into ClickHouse
Datrise syncs Twitter/X Ads's campaign metrics, spend, engagement, and ad conversion performance 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
Twitter/X Ads: Ad performance source for X campaign analytics.
ClickHouse: Columnar OLAP engine for fast aggregations.
How Twitter/X Ads entities map to ClickHouse
| Twitter/X Ads entity | ClickHouse object | Notes |
|---|---|---|
| campaign metrics | twitter_x_ads_campaign_metrics | id PK · custom fields → JSON or Map columns |
| spend | twitter_x_ads_spend | id PK · linked to twitter_x_ads_campaign_metrics |
| engagement | twitter_x_ads_engagement | id PK · linked to twitter_x_ads_campaign_metrics |
| ad conversion performance | twitter_x_ads_ad_conversion_performance | id PK · linked to twitter_x_ads_campaign_metrics |
FAQ
How does Datrise handle Twitter/X Ads'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 Twitter/X Ads 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 Twitter/X Ads
- Twitter/X Ads → DuckDB
- Twitter/X Ads → Amazon Athena
- Twitter/X Ads → Amazon S3 Data Lake
- Twitter/X Ads → Azure Data Lake Storage
- Twitter/X Ads → Azure Synapse
- Twitter/X Ads → Spreadsheets
- Twitter/X Ads → Airtable
- Twitter/X Ads → CSV Files
- Twitter/X Ads → MongoDB
- Twitter/X Ads → Supabase
- Twitter/X Ads → Neon
- Twitter/X Ads → PlanetScale
Early access
Connect Twitter/X Ads 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.