Skip to content
Customer lists

Magento Customer Match lists in Google Ads

Create six Customer Match lists in Google Ads and keep them filled from Magento, from first-time buyers to lapsed customers.

Product Metrics creates six Customer Match lists in your Google Ads account and keeps them up to date from your Magento orders, moving each customer to the right lists after every paid order (for example from First-time buyers to Second-time buyers). You choose where to use them: Product Metrics never changes your campaigns.

Prerequisites

  • Workspace admin in Product Metrics, with Pro (Full Signal Tracking). Google Ads needs Merchant Center connected.
  • Your Magento store view connected: the Product Metrics module installed by your developer, verified, and linked to your property. See Magento.
  • Google Ads connected to your property, with its conversion actions created and conversion tracking on in Google Ads, and a Google login allowed to manage the account, to accept the Customer Match terms. See Google Ads.

Set it up with AI

Connect your assistant

First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.

In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:

https://www.productmetrics.io/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Paste the prompt into your assistant.

Create the six Product Metrics customer lists for my Magento store in Google Ads and keep them filled. Check my setup status first, walk me through each open step, and give me the link when I need to click something.
Create the six Product Metrics customer lists for my Magento store in Google Ads and keep them filled. Check my setup status first, walk me through each open step, and give me the link when I need to click something.
Create the six Product Metrics customer lists for my Magento store in Google Ads and keep them filled. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser.
Create the six Product Metrics customer lists for my Magento store in Google Ads and keep them filled. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser.

In the app

1. Check your Magento store view recognises customers

Running several store views? Each one is its own connection with its own customers. Create the lists for each property its store view feeds.

To check a recent order, ask your assistant: “Are my last five Magento orders from new or returning customers?”

You should see: whether your test order’s customer was recognised, as new or returning.

In Tracking → Configure consent, choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. With another banner, your developer passes the visitor’s choices to Product Metrics. A customer joins a list only when the visitor allowed both ad user data and ad personalisation. Leaving a list never needs consent: Product Metrics always removes a customer who no longer qualifies. See Consent.

The Configure consent step with the consent platform list open: Not configured, Shopify Customer Privacy, OneTrust, Cookiebot, Usercentrics and Osano.The Configure consent step with the consent platform list open: Not configured, Shopify Customer Privacy, OneTrust, Cookiebot, Usercentrics and Osano.
Configure consent: choose the banner your store shows visitors.

Magento’s cookie restriction notice grants nothing. Without a supported banner or your developer passing the choices, visitors count as not having consented, and their customers get no list membership.

You should see: Configure consent names the banner your Magento store view actually shows.

3. Accept the Customer Match terms

Google Ads only accepts customer lists once the account has accepted its Customer Match terms. You do this yourself in the Google Ads web interface.

You should see: creating the lists in the next step doesn’t fail with a Customer Match terms error.

4. Create the lists

Product Metrics creates the six lists (who joins each), or adopts matching ones it already manages, and tags each with its Google Ads customer type.

In Product Metrics, select Tracking → Google Ads → Customer lists → Create 6 customer lists.

You should see: all six lists created. If some lists exist already, the button reads Create 2 missing customer lists or Set up 1 customer list.

5. Use the lists in your campaigns

In Google Ads, the lists appear with your other audience lists as Product Metrics - [list] - [your store]. For example:

  • Exclude All customers from a campaign that should only find new customers.
  • Use Lapsed customers to win back customers who haven’t ordered in six months.
  • Tell Performance Max who your High-value customers are.

Customers join with their next paid order after the lists exist; the lists fill up from there.

You should see: the lists show members in Google Ads.

Troubleshooting

Creating the lists fails with a Customer Match terms error

Accept the Customer Match terms in the Google Ads web interface, then create the lists again.

FAQ

Are my existing Magento customers added to the lists?

No. Customers join with their next paid order after the lists exist, and the lists fill up from there.

No. Use OneTrust, Cookiebot, Usercentrics or Osano, or have your developer pass the visitor’s choices to Product Metrics. Otherwise visitors count as not having consented and their customers get no list membership.

How are customers counted across Magento store views?

Per store view: each store view is its own connection, so the same person buying in two store views counts as two customers. Create the lists for each property a store view feeds.

Do cancelled Magento orders count?

No. Only paid Magento orders count towards a customer’s orders.

Where next

Developers: do the same with the CLI or the API.