Google Customer Match

Google Customer Match sends the members of an Ours Privacy audience to a Customer Match list in Google Ads. Ours Privacy submits each daily membership update for Google to process.

---

Before you start

• A Google Ads account eligible for Customer Match and authorized to use customer data.
• A Google Cloud project with the Google Data Manager API enabled.
• Your own Google OAuth client in that project. The client must be configured for the Google Data Manager sensitive permission that Ours Privacy requests during connection.
• The Ours Privacy production redirect URI, https://app.oursprivacy.com/integrations, added to the OAuth client's authorized redirect URIs.
• A Customer ID for the Google Ads account that owns the list. If it is managed through an MCC, you also need the Manager Account ID.
• An audience with about 5,000 matchable members. Google may accept a smaller upload, but it may not be usable for targeting.

You do not need a Google Ads developer token for this destination. Ours Privacy does not reuse an Ours-owned Google Ads token.

---

Set up the destination

1. In Destinations, add Google Customer Match.
2. Enter your Google OAuth Client ID and Google OAuth Client Secret. Ours Privacy does not use an Ours-owned OAuth app or Google Ads developer token for this destination.
3. Select Connect Google Data Manager and complete the Google sign-in flow.
4. Enter the Google Ads Customer ID. Add the Manager Account ID only when the account is accessed through an MCC.
5. Choose the identifier groups you authorize Ours Privacy to send. Every group starts off.
6. Save and publish the destination.

Ours Privacy stores the OAuth client secret as a secret setting and does not display it again after save. If you connected this destination before the Data Manager migration, reconnect it so Google can grant the required permission.

---

Identifier choices

You choose whether to send:

• Email
• Phone
• Postal address: first name, last name, country, and postal code

Each enabled value is normalized for Google and hashed with SHA-256 before upload. Members with no usable enabled identifier are skipped. Google does not receive your audience conditions or internal audience name.

---

Sync behavior and eligibility

Ours Privacy creates one Customer Match list for each attached audience and submits membership updates daily. List membership is configured to expire one day after its last refresh, so members who leave the audience age out after the next daily cycle. A missed sync can temporarily reduce the active list.

Google processes Customer Match asynchronously. Ours Privacy reports submission errors, including common eligibility and terms errors, but Google Ads determines when the list becomes usable and how many members it matches.

Keep the Export Name neutral. It is visible in Google Ads and must not describe a sensitive characteristic. For EEA audiences, ensure your setup and audience criteria meet Google's consent requirements.

---

Next Steps

• Audience Destinations for how audience syncing works.
• Syncing to destinations to attach this destination to an audience.
• Audience Builder to build and export audiences now.

Need help? Contact support@oursprivacy.com.