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

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 dclid identifier is used for attribution instead of gclid in 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 dclid is 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.

Add Integration to Pipeline

Once you've configured the starter kit:

1. Go to Pipelines > Select your Pipeline
2. Click the right drop-down > Add Integration
3. Select your DV360 integration and revision > Deploy

Event Mappings

Event mappings for DV360 align with the CM360 - Floodlights starter kit exactly, with one change in the Global mapping: the conversion identifier is switched from gclid to dclid.

Global Mapping Change

In the current CM360 - Floodlights playbook, the click, device, and match identifiers are not separate mappings. They are all produced by a single Global expression named "Click, Mobile Device and Match ID(s)", which returns one identifier per conversion in priority order — gclid → dclid → mobileDeviceId → matchId — or every available identifier when IDENTIFIER_FAN_OUT is true.

To make the integration use dclid for DV360 attribution, edit that expression so dclid is selected ahead of gclid:

1. Navigate to Global events.
2. Expand the "Click, Mobile Device and Match ID(s)" expression.
3. In the single-identifier return line, move dclid ahead of gclid so dclid is returned first:

return (dclid and { dclid = dclid })
  or (gclid and { gclid = gclid })
  or (mobileDeviceId and { mobileDeviceId = mobileDeviceId })
  or (matchId and { matchId = matchId })

If your DV360 traffic never carries a gclid, no edit is required — the stock priority already falls through to dclid when gclid is absent.

All other event mappings follow the CM360 - Floodlights event mappings exactly.

Required Identifiers

The dclid is captured by the Google Tag sync and enriched into server-side events via context.providers.CM360.dclid or context.providers.googleGtag.data.dclid.

Additional Documentation

• CM360 - Floodlights Integration
• CM360 Conversion API Overview
• CM360 Conversion API Reference