Doubleclick Campaign Manager → Azure Data Lake Storage
AI-first ETL from Doubleclick Campaign Manager into Azure Data Lake Storage. Governed entities, incremental sync, typed landing tables.
How Datrise loads Doubleclick Campaign Manager into Azure Data Lake Storage
Datrise syncs Doubleclick Campaign Manager's records, events, and configuration objects 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
Doubleclick Campaign Manager: SaaS or API data source for analytics and warehouse sync.
Azure Data Lake Storage: ADLS Gen2 object storage for analytics workloads.
How Doubleclick Campaign Manager entities map to Azure Data Lake Storage
| Doubleclick Campaign Manager entity | Azure Data Lake Storage object | Notes |
|---|---|---|
| records | doubleclick_campaign_manager_records | id PK · custom fields → nested struct/map fields in Parquet |
| events | doubleclick_campaign_manager_events | ISO-8601 timestamp columns events |
| configuration objects | doubleclick_campaign_manager_configuration_objects | id PK · linked to doubleclick_campaign_manager_records |
FAQ
How does Datrise handle Doubleclick Campaign Manager'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 Doubleclick Campaign Manager 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 Doubleclick Campaign Manager
- Doubleclick Campaign Manager → Azure Synapse
- Doubleclick Campaign Manager → Spreadsheets
- Doubleclick Campaign Manager → Airtable
- Doubleclick Campaign Manager → CSV Files
- Doubleclick Campaign Manager → MongoDB
- Doubleclick Campaign Manager → Supabase
- Doubleclick Campaign Manager → Neon
- Doubleclick Campaign Manager → PlanetScale
- Doubleclick Campaign Manager → Amazon DynamoDB
- Doubleclick Campaign Manager → Looker
- Doubleclick Campaign Manager → Looker Studio
- Doubleclick Campaign Manager → 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 Marketing → Azure Data Lake Storage
- Facebook Pages → Azure Data Lake Storage
- Fastbill → Azure Data Lake Storage
Early access
Connect Doubleclick Campaign Manager 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.