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.
Why route Google DV360 through Datafly Signal
- Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Google DV360 optimises against are not filtered by the browser.
- Email and phone number are hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Google DV360 receives match keys rather than raw personal data.
- Click identifiers are captured and replayed. Signal stores
dclid,gclidfirst-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired. - Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Google DV360 rate limit, and retries on 429 or transient failure rather than dropping the event.
- Token lifecycle is handled for you. Signal obtains and refreshes the OAuth credentials Google DV360 requires, so nothing expires quietly in the middle of a campaign.
- Presets for Retail and Automotive. The mapping starts from a working configuration for your vertical instead of a blank field map.
- One consent decision governs every destination. Google DV360 is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
- No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.
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.
API endpoint
POST https://dfareporting.googleapis.com/dfareporting/v5/userprofiles/{{profile_id}}/conversions/batchinsertAllow egress to dfareporting.googleapis.com from the network your delivery workers run on.
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.