Campaign Manager 360 to Google BigQuery Integration
AI-first ETL from Campaign Manager 360 into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads Campaign Manager 360 into Google BigQuery
Datrise syncs Campaign Manager 360's campaigns, placements, creatives, impressions, clicks, and conversions into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.
Ideal for Google-stack analytics and ML on serverless infrastructure.
Endpoints
Campaign Manager 360: Ad serving and campaign measurement for display.
Google BigQuery: Serverless analytics warehouse on GCP.
How Campaign Manager 360 entities map to Google BigQuery
| Campaign Manager 360 entity | Google BigQuery object | Notes |
|---|---|---|
| campaigns | doubleclick_campaign_manager_campaigns | id PK · custom fields → JSON or nested/repeated (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 Google BigQuery?
Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.
How does the Campaign Manager 360 to Google BigQuery sync stay up to date?
It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.
Related pipelines
More destinations for Campaign Manager 360
- Campaign Manager 360 → Amazon Redshift
- Campaign Manager 360 → Databricks SQL Warehouse
- 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
More sources for Google BigQuery
- Dremio → Google BigQuery
- Drift → Google BigQuery
- Drip → Google BigQuery
- Elasticsearch → Google BigQuery
- Eloqua → Google BigQuery
- EmailOctopus → Google BigQuery
- Everhour → Google BigQuery
- Excel File → Google BigQuery
- Exchange Rates API → Google BigQuery
- Facebook Pages → Google BigQuery
- Fastbill → Google BigQuery
- Fauna → Google BigQuery
Early access
Connect Campaign Manager 360 to Google BigQuery 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.