Twitter/X Ads → Databricks SQL Warehouse
AI-first ETL from Twitter/X Ads into Databricks SQL Warehouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Twitter/X Ads into Databricks SQL Warehouse
Datrise syncs Twitter/X Ads's campaign metrics, spend, engagement, and ad conversion performance into Databricks SQL Warehouse as a Delta Lake table per source entity. Flexible or custom fields land in VARIANT or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses a Delta MERGE on stable id, with change history available via time travel, so re-runs update only what changed. Delta partitioning by load date with OPTIMIZE/Z-ORDER on query keys. Datrise writes Unity Catalog–governed Delta tables, so lineage and permissions are managed centrally rather than per-notebook.
Ideal for lakehouse analytics and ML feature tables on Databricks.
Endpoints
Twitter/X Ads: Ad performance source for X campaign analytics.
Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.
How Twitter/X Ads entities map to Databricks SQL Warehouse
| Twitter/X Ads entity | Databricks SQL Warehouse object | Notes |
|---|---|---|
| campaign metrics | twitter_x_ads_campaign_metrics | id PK · custom fields → VARIANT or STRUCT 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 Databricks SQL Warehouse?
Flexible values are stored as VARIANT or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Databricks SQL Warehouse types.
How does the Twitter/X Ads to Databricks SQL Warehouse sync stay up to date?
It runs incrementally — Datrise uses a Delta MERGE on stable id, with change history available via time travel.
Related pipelines
More destinations for Twitter/X Ads
- Twitter/X Ads → ClickHouse
- 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
More sources for Databricks SQL Warehouse
- LinkedIn Ads → Databricks SQL Warehouse
- Meta Ads → Databricks SQL Warehouse
- SAP → Databricks SQL Warehouse
- Amplitude → Databricks SQL Warehouse
- MoEngage → Databricks SQL Warehouse
- Auth0 → Databricks SQL Warehouse
- Attio → Databricks SQL Warehouse
- Bigin by Zoho → Databricks SQL Warehouse
- BambooHR → Databricks SQL Warehouse
- Workday → Databricks SQL Warehouse
- Pipeliner CRM → Databricks SQL Warehouse
- Kommo → Databricks SQL Warehouse
Early access
Connect Twitter/X Ads to Databricks SQL Warehouse 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.