Google Customer Match

Google Customer Match is not yet available as an Audience Destination in Ours Privacy. You can save credentials in advance, but audiences attached to it do not deliver.

BetaThis is in beta. The basics are stable, and more capabilities are on the way.

Not available yet. Google Customer Match appears in the destinations list and accepts credentials, but it cannot sync audiences. Do not plan campaigns around it. To sync an audience today, use Vibe CTV Audiences.

Google Customer Match will let you send the members of an Ours Privacy audience to a Google Ads account as a Customer Match list. This page covers what you can do today and what to get ready in Google Ads.


What works today

You can add the destination and save its credentials, so the setup is ready in advance. That is the extent of it.

Attaching an audience to this destination has no effect in Google Ads: no Customer Match list is created, and nothing is uploaded. The attempted sync is recorded against the audience as failed, with a message saying the destination cannot sync yet, so it will not look like a healthy sync that quietly produced nothing.


Google-side prerequisites

Get these in place before you plan campaigns around the destination. Google enforces them, so a valid credential on its own is not enough.

  • Customer Match eligibility on the Google Ads account. Not every account qualifies. Google requires a good history of policy compliance and a good payment history, and the features available depend on which requirements the account meets. An ineligible account can accept a list and still never make it usable for targeting, so confirm eligibility with Google first. Google's Customer Match policy covers the requirements and restrictions.
  • Data you collected yourself. Google's Customer Match policy limits uploads to data you acquired directly, first-party, from the people in the list.
  • An audience large enough to be targetable. Google only serves against a Customer Match list once it has enough active users at the time the ad is served, and recommends uploading at least 5,000 members to have a reasonable chance of clearing that threshold. Lists also expire: membership older than 540 days stops counting, and a list needs at least 100 members added or refreshed inside that window to stay eligible. A daily sync keeps it refreshed.

Note: If your users are in the EEA, Google's EU user consent policy requires consent signals to accompany Customer Match uploads. Confirm what your account needs before relying on this destination for EEA audiences.


Credentials it will ask for

When you add the destination, the settings page asks for:

  • Customer ID the Google Ads account that will own the Customer Match lists, shown in the top right of the Google Ads interface. Digits only, no dashes.
  • Manager Account ID only needed if you reach that account through a manager (MCC) account. Leave it blank otherwise. Digits only, no dashes.
  • Refresh Token an OAuth2 refresh token for a user with access to the Google Ads account above.

What to expect when it ships

It will work the way the other Audience Destinations do, described on Audience Destinations: members re-sent daily, each run replacing the previous list so removals propagate on their own, and the audience's Export Name as the only label Google sees.

Two things worth knowing now, because they affect how you name and size an audience:

  • Google displays the Export Name in the Ads interface, so keep it meaningless rather than descriptive. Ours Privacy blocks Export Names carrying health context regardless of destination.
  • The matched list in Google will be smaller than the count in Ours Privacy. An address only matches if it is associated with a Google Account, and corporate accounts such as Google Workspace cannot be targeted. Google reports the match rate on the list once an upload succeeds, and rounds the list size it displays.

This page gets updated with the setup steps and the exact sync behavior when it goes live. To be told when that happens, contact your account representative.


Next Steps

Need help? Contact support@oursprivacy.com.

How is this guide?

On this page