Campaign Manager 360 to MySQL Integration
AI-first ETL from Campaign Manager 360 into MySQL. Governed entities, incremental sync, typed landing tables.
How Datrise loads Campaign Manager 360 into MySQL
Datrise syncs Campaign Manager 360's campaigns, placements, creatives, impressions, clicks, and conversions into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.
Ideal for operational reporting and app databases already standardized on MySQL.
Endpoints
Campaign Manager 360: Ad serving and campaign measurement for display.
MySQL: Widely used OSS relational engine (InnoDB).
How Campaign Manager 360 entities map to MySQL
| Campaign Manager 360 entity | MySQL object | Notes |
|---|---|---|
| campaigns | doubleclick_campaign_manager_campaigns | id PK · custom fields → JSON 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 MySQL?
Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.
How does the Campaign Manager 360 to MySQL sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for Campaign Manager 360
- Campaign Manager 360 → Microsoft SQL Server
- Campaign Manager 360 → Oracle Database
- Campaign Manager 360 → Snowflake
- Campaign Manager 360 → Google BigQuery
- 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
Early access
Connect Campaign Manager 360 to MySQL 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.