CDPGuidesSupport

Google Customer Match

Sync an Ours Privacy audience to Google Ads Customer Match using your own Google OAuth client and the hashed identifiers you choose to send.

Use this page to sync an Ours Privacy audience to a Customer Match list in Google Ads. Ours Privacy submits a membership update daily for Google to process.


Before you start

  • A Google Ads account eligible for Customer Match, and its Customer ID. If it is managed through an MCC, also the Manager Account ID.
  • A Google Cloud project with the Google Data Manager API enabled and your own OAuth client in it, with https://app.oursprivacy.com/integrations added to its authorized redirect URIs.
  • An audience of roughly 5,000 matchable members. Google may accept less, but the list may not serve.

You do not need a Google Ads developer token.


Set up the destination

  1. In Destinations, add Google Customer Match.
  2. Enter your OAuth Client ID and Client Secret.
  3. Select Connect Google Data Manager and complete the sign-in.
  4. Enter the Customer ID, and the Manager Account ID if you use one.
  5. Turn on the identifiers you want to send: email, phone, postal address. All start off.
  6. Save and publish.

If Google reports a missing permission, reconnect the destination.


Sync behavior

Each enabled identifier is hashed before upload. Phone numbers need a country code, or a US or Canadian format Ours Privacy can infer one for; others are skipped. Members with none of the enabled identifiers are skipped. Google never receives your conditions or internal name.

Ours Privacy creates one list per attached audience and refreshes it daily. Membership expires a day after its last refresh, so people who leave the audience age out after the next cycle, and a missed run can temporarily shrink the list.

Google processes uploads on its own schedule and decides when a list becomes usable and how many members it matched. Ours Privacy surfaces submission errors, including eligibility and terms errors. The Export Name is visible in Google Ads and must not describe a sensitive characteristic. For EEA audiences, make sure your setup meets Google's consent requirements.


Next Steps

Need help? Contact support@oursprivacy.com.

How is this guide?

On this page