Campaign Manager 360 to Databricks SQL Warehouse Integration
AI-first ETL from Campaign Manager 360 into Databricks SQL Warehouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Campaign Manager 360 into Databricks SQL Warehouse
Datrise syncs Campaign Manager 360's campaigns, placements, creatives, impressions, clicks, and conversions 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
Campaign Manager 360: Ad serving and campaign measurement for display.
Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.
How Campaign Manager 360 entities map to Databricks SQL Warehouse
| Campaign Manager 360 entity | Databricks SQL Warehouse object | Notes |
|---|---|---|
| campaigns | doubleclick_campaign_manager_campaigns | id PK · custom fields → VARIANT or STRUCT columns |
| placements | doubleclick_campaign_manager_placements | id PK · linked to doubleclick_campaign_manager_campaigns |
| creatives | doubleclick_campaign_manager_creatives | id PK · linked to doubleclick_campaign_manager_campaigns |
| impressions | doubleclick_campaign_manager_impressions | id PK · linked to doubleclick_campaign_manager_campaigns |
FAQ
How does Datrise handle Campaign Manager 360'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 Campaign Manager 360 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 Campaign Manager 360
- Campaign Manager 360 → ClickHouse
- Campaign Manager 360 → DuckDB
- Campaign Manager 360 → Amazon Athena
- Campaign Manager 360 → Amazon S3 Data Lake
- Campaign Manager 360 → Azure Data Lake Storage
- Campaign Manager 360 → Azure Synapse
- Campaign Manager 360 → Spreadsheets
- Campaign Manager 360 → Airtable
- Campaign Manager 360 → CSV Files
- Campaign Manager 360 → MongoDB
- Campaign Manager 360 → Supabase
- Campaign Manager 360 → Neon
More sources for Databricks SQL Warehouse
- Dremio → Databricks SQL Warehouse
- Drift → Databricks SQL Warehouse
- Drip → Databricks SQL Warehouse
- Elasticsearch → Databricks SQL Warehouse
- Eloqua → Databricks SQL Warehouse
- EmailOctopus → Databricks SQL Warehouse
- Everhour → Databricks SQL Warehouse
- Excel File → Databricks SQL Warehouse
- Exchange Rates API → Databricks SQL Warehouse
- Facebook Pages → Databricks SQL Warehouse
- Fastbill → Databricks SQL Warehouse
- Fauna → Databricks SQL Warehouse
Early access
Connect Campaign Manager 360 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.