Campaign Manager 360 to Amazon S3 Data Lake Integration
AI-first ETL from Campaign Manager 360 into Amazon S3 Data Lake. Governed entities, incremental sync, typed landing tables.
How Datrise loads Campaign Manager 360 into Amazon S3 Data Lake
Datrise syncs Campaign Manager 360's campaigns, placements, creatives, impressions, clicks, and conversions into Amazon S3 Data Lake as columnar Parquet objects partitioned 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 and compacts small files on a schedule, so re-runs update only what changed. Hive-style path partitioning (entity/date) for engine-agnostic reads. A lake has no schema enforcement, so Datrise writes a schema manifest alongside the data to keep downstream engines consistent.
Ideal for an open, engine-neutral storage layer for Spark, Athena, Trino, or DuckDB.
Endpoints
Campaign Manager 360: Ad serving and campaign measurement for display.
Amazon S3 Data Lake: Object storage landing zone for parquet and snapshots.
How Campaign Manager 360 entities map to Amazon S3 Data Lake
| Campaign Manager 360 entity | Amazon S3 Data Lake 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 Amazon S3 Data Lake?
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 Amazon S3 Data Lake types.
How does the Campaign Manager 360 to Amazon S3 Data Lake sync stay up to date?
It runs incrementally — Datrise uses writes new date partitions and compacts small files on a schedule.
Related pipelines
More destinations for Campaign Manager 360
- 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
- Campaign Manager 360 → PlanetScale
- Campaign Manager 360 → Amazon DynamoDB
- Campaign Manager 360 → Looker
- Campaign Manager 360 → Looker Studio
More sources for Amazon S3 Data Lake
- Dremio → Amazon S3 Data Lake
- Drift → Amazon S3 Data Lake
- Drip → Amazon S3 Data Lake
- Elasticsearch → Amazon S3 Data Lake
- Eloqua → Amazon S3 Data Lake
- EmailOctopus → Amazon S3 Data Lake
- Everhour → Amazon S3 Data Lake
- Excel File → Amazon S3 Data Lake
- Exchange Rates API → Amazon S3 Data Lake
- Facebook Pages → Amazon S3 Data Lake
- Fastbill → Amazon S3 Data Lake
- Fauna → Amazon S3 Data Lake
Early access
Connect Campaign Manager 360 to Amazon S3 Data Lake 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.