---
schema_version: "1"
id: 095aaeb556985f7673ced7a669dbce2a7521631375e1c08c427c0f493b4f4bfa
title: Google DV360 Activation Connector
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-int/guides/googledv360adaudiences/c360-a-googledv360adaudiences-connector.md
canonical_url: https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-googledv360adaudiences-connector.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: c675ae7b3df9dd8ccb31d82459d61393b0db3118f587bb19696fc7211ee2906f
products:
  - Data 360 Integration Guide
  - Data 360 Developer Documentation
---
# ![GoogleDV360activation](https://developer.salesforce.com/media/data-cloud-int/icons/dv360.svg '{"class": "image-icon-lg", "title": "Google DV360 Connector"}') 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

## Data Type

- Structured

## Data Direction

The direction of available connection methods.

### Data Out

Create a connection to activate data to external platforms.

Supported connection method(s):

- Incremental
- Direct API

After the initial setup and segment activation, Google’s Audience Partner API activates the new and updated user records incrementally. This connection also supports a full refresh to reload all information.

## Connector Setup

Instructions for adding and configuring your connector.

1. [Set Up a Connection to Google DV360](/docs/data/data-cloud-int/guide/c360-a-googledv360adaudiences-setup.html)

## Restrictions and Requirements

- Minimum Match Count: 100 users accepted and matched by Google
  **note:** The Match count reflects the search match count. For detailed information, see [About Customer Match.](https://support.google.com/google-ads/answer/6379332?hl=en&ref_topic=10551292&sjid=15579004103581531-NC)
- 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.](https://help.salesforce.com/s/articleView?id=004577010&type=1)

## Considerations

- 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).
- For region-based rules for advertiser verification, see [Google’s political content requirements](https://support.google.com/adspolicy/answer/6014595#zippy=). For answers to common questions about the verification process, see [Advertiser Verification](https://support.google.com/adspolicy/answer/9703665).

## Attribute Keys and Encryption

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                  | 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.

**note:** To pass consent values from Data 360 to Google, make sure that their attribute value are 0 or 1, in text format. If the values of both consent attribute are 1, Data 360 passes them to Google as 'Granted'. If any consent value in a user record is 0, signifying that the consent is denied, the record isn’t activated. Data 360 passes any other combination of values, and any unmapped consent profiles, as 'unspecified'. In some regions, like the EEA, Google may reject all records that aren’t 'Granted'. For a detailed explanation of consent requirements, see Google's guidance on consent values or [New Consent Settings for Google Activations in the EEA.](https://help.salesforce.com/s/articleView?id=001040168&type=1)