Search documentation...

K

Google Display & Video 360

Sync customer segments to Display & Video 360

Overview

With the Google Display & Video 360 integration, Hightouch can sync first and third party audiences directly from your warehouse.

This allows you to:

  1. Create ad target groups for your own users, using email, physical address or mobile device id.
  2. Create target groups from users shared with a partner.

Setup via OAuth

Select the Google Display & Video 360 destination option. Hightouch will prompt you to authorize our app with your Google account with the following a scope to create and update audiences on your DV360 accounts.

After authorizing, you will have successfully connected Hightouch to DV360.

Syncing data

Currently Hightouch allows to create and update first and third party audiences as customer match user lists. These lists support adding members using the mobile device id, or an array of email, phone numbers, and physical addresses.

When creating the audience, make sure the source of the data is properly selected, between First or Third party sources.

PII data and Hashing

Hightouch will automatically hash all the PII data before it gets send to Google. If the data is already hashed, this option can be disabled. More information about hashing here.

Google's Personalized Ads Policy, Customer Match Policy and Platforms program policies include requirements for advertisers to show sufficiently established Google Ads or Display & Video 360 account history before accessing certain features. To enable uploading data to DV360, please fill this form before you create the sync.

User identifiers

Mobile device IDs and other user identifiers can not be mixed. Also, if providing the user's physical address, the zip code, country code, first and last name must be provided.

Phone numbers must be in E.164 format.

    Need help?

    Our team is relentlessly focused on your success. We're ready to jump on a call to help unblock you.

    • Connection issues with your data warehouse?
    • Confusing API responses from destination systems?
    • Unsupported destination objects or modes?
    • Help with complex SQL queries?

    Feature Requests?

    If you see something that's missing from our app, let us know and we'll work with you to build it!

    We want to hear your suggestions for new sources, destinations, and other features that would help you activate your data.

On this page

OverviewSetup via OAuthSyncing dataPII data and HashingUser identifiers

Was this page helpful?