Google Display & Video 360
This integration is currently in beta. Contact your MetaRouter support team to get started.
What Is Display & Video 360?
DV360, or Display & Video 360, is a comprehensive programmatic advertising platform developed by Google. It offers advertisers a unified solution for planning, executing, and measuring digital display and video campaigns across multiple channels and formats. With features such as audience targeting, real-time bidding, and advanced measurement capabilities, DV360 empowers marketers to reach their target audiences effectively, optimize campaign performance, and drive meaningful results.
Product Type: Advertising
Integration Type: Starter Kit & ID Sync
Event Source Type: Web and Mobile Browser
Event Scope: Conversion Events Only
Capabilities
- Sends server-side conversion events to DV360 via the CM360 Offline Conversions API v5
- Supports conversion attribution using the Display Click ID (
dclid) for DV360 attribution - Supports custom Floodlight variables
- Enables Floodlight tag removal
Considerations
- Built on CM360 — The DV360 integration uses the same CM360 - Floodlights starter kit and credentials. The only difference from a standard CM360 setup is that the
dclididentifier is used instead ofgclidin the Global mapping. If you have an active CM360 integration, you can reuse the same credentials and IDs. - Shared Floodlight Activities Required — Your CM360 account must share Floodlight activities with DV360 before this integration can function.
- DCLID Cookie Lifetime — Set the DCLID cookie lifetime in your Google Tag sync to align with your DV360 attribution/lookback window. The default is 90 days.
- Processing Delay — Google recommends delaying conversion uploads by ~1 hour after click to ensure
dclidis available for matching. Contact your MetaRouter Customer Support Rep to configure a delay.
Getting Started — From Your CM360 Account
The DV360 integration relies on an active CM360 account that shares Floodlight activities with DV360. Follow the full prerequisite and credential setup steps in the CM360 - Floodlights documentation.
If you have already completed CM360 setup, you can proceed using the same credentials and IDs — no need to repeat that process.
Getting Started — From Your MetaRouter Account
Adding a DV360 Integration
From the integration library, add a "Google CM360 - Floodlights" integration. If you have an existing CM360 integration, consider creating a separate instance and renaming it to reflect the DV360 connection (e.g., "Campaign Manager - DV360").
Fill out the connection parameters as documented in the CM360 - Floodlights integration.
Adding a Google Tag Sync (ID Sync Configuration)
To capture the dclid value required for DV360 attribution, you must configure a Google Tag sync.
| Architecture | Documentation |
|---|---|
| CM360 Sync - Decoupled | CM360 as a separate sync under parent Google Tag Settings |
| Google Tag Sync - Coupled (Legacy) | CM360 bundled with GA4/Google Ads in single Google GTag sync |
Add Integration to Pipeline
Once you've configured the starter kit:
- Go to Pipelines > Select your Pipeline
- Click the right drop-down > Add Integration
- Select your DV360 integration and revision > Deploy
Event Mappings
Event mappings for DV360 align with CM360 with one key change: the identifier is switched from gclid to dclid in the Global mapping.
Global Mapping Change
- Navigate to Global events
- Expand the
gclidparameter - Update the output key from
gclidtodclid - Update the expression from:
return SPLIT(input.context.providers.googleGtag.data.gclid, ".", 3)[3]to:
return SPLIT(input.context.providers.googleGtag.data.dclid, ".", 3)[3]All other event mappings follow the CM360 - Floodlights event mappings exactly.
Required Identifiers
| Attribute | Example | Sync Required? |
|---|---|---|
dclid Required | CKDdz-fE_IUDFYtTCQkdbyMOPg | Yes |
The dclid is captured by the Google Tag sync and enriched into server-side events via context.providers.googleGtag.data.dclid.
Additional Documentation
Updated 23 days ago