Google DV360 Activation Connector
Create activation targets and activate your Data 360 segments to Google Display & Video 360 (DV360) for targeted advertising.
- Available with add-on license: Ad Audiences
- Structured
The direction of available connection methods.
Create a connection to activate data to external platforms.
Supported connection method(s):
- Incremental
- Direct API
After the initial segment activation, a direct API updates data incrementally. This connection also supports a full refresh to reload all information.
- Minimum Match Count: 100 users
The Match count reflects the search match count. For detailed information, see About Customer Match.
- Audience Time to Live (TTL): 540 days TTL is a requirement implemented by certain platforms to update or refresh all records in a segment within a specific time. If the records aren’t refreshed within the designated window, the system flags them as inactive and automatically deletes them. See Google’s Updated Customer Match Retention Policy.
- When you set up the connection, you can authenticate at the partner or advertiser level. To activate segments across multiple accounts or for an automated, broader integration, authenticate at the partner level. If you manage activation for an individual account only, authenticate at the advertiser level.
- According to Google policy, Google DV360 activations at the Partner level don't match users in the European Economic Area (EEA).
Here are the attributes that you can activate to Google DV360, along with related details.
| Attribute Display Name | Description | Recommended DMO Mapping | Data Type | Data Ingestion Format | Encryption State for Activation | Optional or Required |
|---|---|---|---|---|---|---|
| Email address of the user | ContactPointEmail > EmailAddress | String | Standard Email | Encrypted with SHA256 | Required | |
| phone | Phone number of the user | ContactPointPhone > FormattedE164PhoneNumber | String | ISO E164 | Encrypted with SHA256 | Optional |
| ad_user_data | Consent status for sending user data to Google for advertising purposes. | ConsentStatus | String (1=Granted, 0=Denied) | Optional (See Note) | ||
| ad_personalization. | Consent status for ad personalization. | ConsentStatus | String (1=Granted, 0=Denied) | Optional (See Note) |
- The Data Ingestion Format specifies the required format for ingesting the attribute into Data 360.
- The Encryption State for Activation shows the state and type of encryption applied to each attribute in Data 360.
The consent field must have a value of 0 or 1 in text format. Any other value is interpreted as unspecified. If the consent value for a user record is 0, signifying that consent is denied, the record isn’t activated. However, if the consent value is mapped as ‘unspecified’, in EEA regions, it's counted as denied, while in non-EEA regions, it's counted as granted. For a detailed explanation of consent requirements, see New Consent Settings for Google Activations in the EEA.