Amperity and Google Ads: Google Customer Match

Q: What is Google Customer Match?

Customer Match uses eligible first-party customer data to match audience members to Google users for supported advertising use. Amperity defines the audience from your available customer context; Google applies its account, policy, matching, and campaign requirements.

Q: Which Amperity connector should a new setup use?

Current Amperity documentation directs new Customer Match setups to Google Customer Match (GDM), which is in beta. Check eligibility with your representative. The older Google Ads and Google Customer Match connectors are separate routes, with distinct configuration and behavior.

Q: Can GDM send several identifiers for each customer?

No. Choose one match identifier for every member of the destination: email, phone, or mobile-id. Changing it requires recreating the audience. Additional customer context can define membership in Amperity without becoming additional identifiers in the outbound payload.

Q: Does GDM replace the entire Customer Match list?

No. Amperity tracks membership changes and sends additions and removals incrementally. Unchanged members stay in place. The connector can update only an audience it created, so an audience shared into the account cannot be used as its update target.

Q: How do I confirm an audience is ready?

Check Google Ads after background processing, which can take minutes to days. A successful Amperity run means Google accepted members, not that they already appear in the audience. Review failed rows and confirm the receiving audience count.

Q: Does Amperity send consent signals with each GDM audience member?

No. The GDM audience connector does not send per-member consent signals. Your audience must already exclude customers who denied ad personalization or ad user data. Apply those criteria before delivery and follow Google’s Customer Match policies.

Send first-party audiences from Amperity to Google Customer Match for eligible Google Ads campaigns, with the beta Google Customer Match (GDM) connector using the Google Data Manager API to add and remove audience members.

Get a demo Customer Match docs

Customer Match • GDM beta • Incremental membership

Use customer context to define eligible Google audiences

Reach eligible Google Ads audiences defined by customer purchase history.

Reconnect with lapsed customers selected in Amperity.

Build cross-sell audiences from available product and customer context.

Prepare recent-purchaser exclusions for supported campaign settings.

Keep GDM list membership aligned with audience entries and exits.

Review failed members alongside Google’s audience counts before relying on a sync.

How Amperity connects to Google Customer Match

Choose the connector. For new Customer Match setups, review the GDM route and its beta eligibility with your Amperity representative.
Define eligible members. Apply consent exclusions and return the single configured match-identifier column.
Validate membership changes. Send a sample, check the receiving list in Google Ads, and schedule the approved audience workflow.

GDM sends one identity field; consent criteria are applied before delivery.

Match on the identifier your GDM destination expects

The GDM connector uses one selected identifier per member: email, phone, or mobile-id. Amperity hashes email and phone values automatically; mobile advertising IDs are sent as-is. A richer Amperity profile does not mean this connector sends multiple identifiers, and the audience must already exclude customers who denied ad personalization or ad user data.

What the Google Customer Match connection supports

Capability	Supported behavior
Current route	Google Customer Match (GDM), in beta, uses the Google Data Manager API; older connectors remain distinct.
Identifier	One configured email, phone or mobile-id column; changing the identifier requires recreating the audience.
Membership	Incremental additions and removals; unchanged members remain in place.
Ownership	Only audiences created by this connector can be updated; shared-in audiences are unsupported.
Timing	Google processes membership changes in the background, from minutes to days; acceptance is not final membership.
Access and consent	Direct administration of the receiving account; no MCC-only access. Per-member consent signals are not sent.

Use customer context for the next media decision

Build a purchase-informed retention audience

Select customers whose purchase recency or repeat-order history makes them relevant for a retention campaign. After applying the required consent exclusions, send the configured identifier to a connector-owned Customer Match list. The media team can use that list in eligible Google Ads campaigns and choose the appropriate message. Validate Google’s processed membership before assuming every qualifying Amperity customer is reachable.

Refresh a cross-sell audience as customers qualify

Use available product history in Amperity to define customers for a complementary offer. With GDM, new qualifiers are added and customers who leave the audience are removed individually on later runs. The audience logic stays in Amperity while Google Ads handles matching and campaign use. Agree on refresh timing that includes both the Amperity schedule and Google’s background processing.

Prepare exclusions for an acquisition campaign

Build a recent-purchaser or existing-customer audience to use as an exclusion where the selected Google campaign allows it. Check the account’s Customer Match eligibility and campaign controls before activation. GDM reports members as delivered when Google accepts them, so verify the receiving member count after processing rather than treating delivery status alone as confirmation that every exclusion is already effective.

Set up and validate the connection

For a new destination, ask your Amperity representative about the beta Google Customer Match (GDM) connector. Authorize Google Data Manager access with an account that directly administers the receiving Customer ID; a manager-account-only login is unsupported.

Set the audience name and one fixed match identifier. Return exactly the matching email, phone or mobile-id column, apply consent exclusions, and validate the receiving list before scheduling. Older Google Ads and Customer Match destinations have different behavior; their audiences are not shared with GDM.

Amperity and Google Ads: Google Customer Match

Use customer context to define eligible Google audiences

How Amperity connects to Google Customer Match

Match on the identifier your GDM destination expects

What the Google Customer Match connection supports

Use customer context for the next media decision

Build a purchase-informed retention audience

Refresh a cross-sell audience as customers qualify

Prepare exclusions for an acquisition campaign

Set up and validate the connection

Google Customer Match FAQs

What is Google Customer Match?

Which Amperity connector should a new setup use?

Can GDM send several identifiers for each customer?

Does GDM replace the entire Customer Match list?

How do I confirm an audience is ready?

Does Amperity send consent signals with each GDM audience member?

Bring your customer audience strategy into eligible Google Ads campaigns