Google Display & Video 360
Datafly Signal delivers offline conversions to Google Display & Video 360 via the Campaign Manager 360 Conversions API (Floodlight). Conversions support gclid, dclid, match ID, and encrypted user ID matching.
This blueprint is currently in beta.
Prerequisites
Before configuring DV360 in Signal, you need:
- A Campaign Manager 360 account linked to your DV360 advertiser
- A Floodlight configuration and an activity for the conversion you want to track
- A GCP service account with the
https://www.googleapis.com/auth/ddmconversionsscope - The service account email added as a CM360 user with conversion-upload permissions
Get your DV360 credentials
- Sign in to Campaign Manager 360.
- Find your User Profile ID under Admin → User Profiles (or via the API
userProfiles.list). - Open Floodlight → Configuration and copy the Floodlight Configuration ID (advertiser-level).
- Open Floodlight → Activities, select or create the activity for your conversion, and copy the Floodlight Activity ID.
- In Google Cloud Console, create a service account, generate a JSON key, and enable the Campaign Manager 360 API.
- Back in CM360, go to Admin → User Profiles → Add user, add the service account email, and grant the Conversions upload permission.
See Google’s Conversions API overview for full details.
Configure the integration in Signal
- In the Management UI, go to Integrations → Add Integration.
- Select Google Display & Video 360 from the catalogue.
- Give the integration a name (for your reference).
- Fill in the required fields:
| Field | Required | Description |
|---|---|---|
profile_id | Yes | CM360 user profile ID. |
floodlight_activity_id | Yes | Floodlight activity ID for this conversion type. |
floodlight_config_id | Yes | Floodlight configuration ID (advertiser-level). |
service_account_json | Yes | GCP service account JSON key. |
match_type | No | How to match conversions: gclid (default), dclid, match_id, encrypted_user_id, mobile_device_id. |
- Choose which pipeline(s) this integration should run on.
- Select consent categories (defaults to marketing).
- Click Save.
Event mapping
| Signal event | DV360 Floodlight |
|---|---|
Order Completed | purchase (counter/sales activity) |
Lead Submitted | lead (counter activity) |
Other events can be mapped to additional activities by creating separate integrations (one per activity ID) and filtering events.
Identity
Signal sends the following identity signals to DV360, subject to consent and availability:
| Capability | Notes |
|---|---|
| Click ID | gclid or dclid from the URL |
| Hashed email | SHA-256 (lowercase, trimmed) |
| Client IP / User-Agent | Forwarded from the original request |
| Mobile device ID | Where available (IDFA/GAID) |
| Encrypted user ID | Where supplied via match-table sync |
Consent
This integration is gated on the marketing canonical consent category. The blueprint also forwards consent into the adUserDataConsent field on each conversion.
Verify it’s working
- In the Management UI, go to Pipelines → your pipeline → Live Events.
- Trigger a test event.
- The event appears in the live feed; click to see the exact payload sent to DV360.
- In CM360, check Reports → Conversions — uploaded conversions appear within a few hours.
Troubleshooting
Conversions rejected with PERMISSION_DENIED.
The service account is missing the CM360 user role. Add it as a CM360 user with conversion-upload permissions on the user profile you specified.
INVALID_FLOODLIGHT_ACTIVITY_ID.
Confirm the activity ID belongs to the configuration ID you specified. Each advertiser has its own Floodlight configuration.