Campaign Manager 360 to Azure Data Lake Storage Integration
AI-first ETL from Campaign Manager 360 into Azure Data Lake Storage. Governed entities, incremental sync, typed landing tables.
How Datrise loads Campaign Manager 360 into Azure Data Lake Storage
Datrise syncs Campaign Manager 360's campaigns, placements, creatives, impressions, clicks, and conversions into Azure Data Lake Storage as partitioned Parquet in ADLS Gen2 per source entity. Flexible or custom fields land in nested struct/map fields in Parquet, and timestamps such as created, updated, and status changes are typed as ISO-8601 timestamp columns.
Sync is incremental: Datrise uses writes new date partitions to the container and compacts on a schedule, so re-runs update only what changed. Hive-style partitioning by load date, readable by Synapse and Databricks. ADLS hierarchical namespace makes folder layout matter, so Datrise keeps a predictable entity/date path your Azure engines mount directly.
Ideal for Azure lakehouse storage shared across Synapse and Databricks.
Endpoints
Campaign Manager 360: Ad serving and campaign measurement for display.
Azure Data Lake Storage: ADLS Gen2 object storage for analytics workloads.
How Campaign Manager 360 entities map to Azure Data Lake Storage
| Campaign Manager 360 entity | Azure Data Lake Storage object | Notes |
|---|---|---|
| campaigns | doubleclick_campaign_manager_campaigns | id PK · custom fields → nested struct/map fields in Parquet |
| 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 Azure Data Lake Storage?
Flexible values are stored as nested struct/map fields in Parquet, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Data Lake Storage types.
How does the Campaign Manager 360 to Azure Data Lake Storage sync stay up to date?
It runs incrementally — Datrise uses writes new date partitions to the container and compacts on a schedule.
Related pipelines
More destinations for Campaign Manager 360
- 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
- Campaign Manager 360 → PlanetScale
- Campaign Manager 360 → Amazon DynamoDB
- Campaign Manager 360 → Looker
- Campaign Manager 360 → Looker Studio
- Campaign Manager 360 → Microsoft Power BI
More sources for Azure Data Lake Storage
- Dremio → Azure Data Lake Storage
- Drift → Azure Data Lake Storage
- Drip → Azure Data Lake Storage
- Elasticsearch → Azure Data Lake Storage
- Eloqua → Azure Data Lake Storage
- EmailOctopus → Azure Data Lake Storage
- Everhour → Azure Data Lake Storage
- Excel File → Azure Data Lake Storage
- Exchange Rates API → Azure Data Lake Storage
- Facebook Pages → Azure Data Lake Storage
- Fastbill → Azure Data Lake Storage
- Fauna → Azure Data Lake Storage
Early access
Connect Campaign Manager 360 to Azure Data Lake Storage 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.