---
name: "Use customer lists, custom audiences and lookalikes"
description: "Decides how first-party customer data can be used in Google Customer Match and Meta custom and lookalike audiences, and prepares compliant, well-matched uploads that stay current and respect opt-outs. Used when you have a customer or lead list and want to target, exclude or find similar people."
version: 2
verified_on: 2026-10-22
reverify_by: 2027-01-20
sources:
  - id: t1-google-cm-policy
    title: "Customer Match policy"
    url: https://support.google.com/adspolicy/answer/6299717
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-google-cm-about
    title: "About Customer Match"
    url: https://support.google.com/google-ads/answer/6379332
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-google-cm-api
    title: "Customer Match (Google Ads API) get started"
    url: https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-google-cm-format
    title: "Format user data (Data Manager API)"
    url: https://developers.google.com/data-manager/api/devguides/concepts/formatting
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-google-personalized-ads
    title: "Personalized advertising policy"
    url: https://support.google.com/adspolicy/answer/143465
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-meta-sac
    title: "Special Ad Category"
    url: https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/special-ad-category
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-meta-ca-types
    title: "About custom audiences"
    url: https://www.facebook.com/business/help/744354708981227
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-meta-ca-file
    title: "Customer file custom audiences"
    url: https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/guides/custom-audiences
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-meta-lookalike
    title: "Lookalike audiences"
    url: https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/guides/lookalike-audiences
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-meta-adv-audience
    title: "Advantage+ audience (Marketing API)"
    url: https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/reference/targeting-expansion/advantage-audience
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-meta-adv-lookalike
    title: "About Advantage+ lookalike"
    url: https://www.facebook.com/business/help/1212225059146059
    tier: T1
    accessed_on: 2026-10-22
  - id: t1-meta-audience-settings
    title: "Choose audience settings in Advantage+ campaigns"
    url: https://www.facebook.com/business/help/25941857932125812
    tier: T1
    accessed_on: 2026-10-22
---

> **How to use this file:** attach it to ChatGPT, Claude, Gemini or Copilot, replace every [PLACEHOLDER] with your details, and add any data or Deepstory evidence files the method needs.

**Best with:** A chat AI for the plan, using a small fake sample of the file. Do the upload yourself, or through your CRM connector after approving it.

## Quick start

1. Only use customer data you collected yourself.
2. For people in Europe, the UK or Switzerland, upload only those who agreed to advertising use. A newsletter sign-up is not enough.
3. Give each list one job: keep customers out, win them back, or find similar people.
4. Make a separate clean file for each platform: Google wants phone numbers with a +, Meta wants digits only.
5. On Meta, customer lists and lookalikes are hints unless you choose "Further limit the reach of your ads". Exclusions are real limits, but only for the people Meta can match.
6. Small Google accounts can use lists to exclude people, but not to target them.
7. Every month, add new customers and remove anyone who unsubscribed.

## Before you start

- Do this first: if conversion tracking is not set up and recording real leads or sales, start with the conversion tracking task. See: Set up conversion tracking with GA4, Consent Mode and Meta CAPI (https://deepstoryresearch.com/method/conversion-tracking-ga4-consent-capi)
- The data was bought, scraped or collected by someone else; platform policies only allow data you collected directly.
- The ads promote housing, jobs or financial products to the US, Canada or Europe on Meta, where lookalikes are not available. See: Set location targeting for Google and Meta ads (https://deepstoryresearch.com/method/geo-targeting-google-meta)

## Intake questions

Ask me these first:

1. **Which privacy laws apply where your customers live (for example GDPR in Europe, the UAE PDPL, India's DPDP Act), and is any of the data health-related?**
   Why: Consent rules outside Europe still apply, and health data is usually treated as sensitive. This task is not legal advice.
   If unknown, assume: Ask the user to confirm with their privacy adviser before any upload; never upload patient or health data.
2. **Did you collect this data directly, and does your privacy notice say you share it with advertising partners?**
   Why: Google Customer Match only allows first-party data with a privacy policy that discloses sharing with service providers.
   If unknown, assume: Do not upload until the user confirms. Draft the privacy-notice wording for their adviser to check.
3. **For people in the EEA, UK or Switzerland, is consent for advertising use recorded per person (not just a newsletter opt-in)?**
   Why: Google does not process EEA records without consent, and EU consent rules apply on both platforms.
   If unknown, assume: Treat the list as containing EEA people; upload only records with recorded advertising consent, and confirm with the privacy lead.
4. **Which identifiers do you have (email, phone, name and postcode, app ID), and is it B2B or B2C?**
   Why: More identifiers raise the match rate; work emails match poorly, so phone numbers matter more for B2B.
   If unknown, assume: Plan for email and phone.
5. **What is each list for: exclusion, re-engagement, lookalike seed, or observation and bidding?**
   Why: Each use has different eligibility rules and size needs.
   If unknown, assume: Start with excluding existing customers.
6. **How old is the Google Ads account, its lifetime spend, and its policy and payment history?**
   Why: Google needs a good compliance and payment history for any use, and 90 days plus more than USD 50,000 lifetime spend for targeting and bid adjustments.
   If unknown, assume: Assume observation and exclusion only.
7. **Do the ads touch health, finance, housing, jobs or other sensitive topics?**
   Why: Google sensitive categories cannot use advertiser-curated audiences, Meta Special Ad Categories remove lookalikes, and Meta blocks audiences suggesting health conditions or financial status.
   If unknown, assume: Ask before building any audience.
8. **Who in the business can accept Meta's Custom Audience Terms, and which campaign types are live (Performance Max, Demand Gen, Advantage+ sales)?**
   Why: Uploads fail until the terms are accepted by an authorised person, and each campaign type uses lists differently.
   If unknown, assume: Ask the business owner to accept the terms themselves; plan for Search and Advantage+ sales.
9. **Which CRM or shop platform holds the data, and is there an unsubscribe or deletion list?**
   Why: Connectors make syncing easier, and opt-outs must be removed from audiences on every refresh.
   If unknown, assume: Plan a manual monthly export with opt-outs removed.

## Decision rules

| If | Then | Threshold | Type | Source |
|---|---|---|---|---|
| The data was not collected directly by the business, or includes people under 13. | Do not upload it to Google Customer Match. | - | Platform rule | [t1-google-cm-policy] |
| You use Google Customer Match at all. | The account (or its manager account) needs a good policy-compliance and payment history. Targeting and bid adjustments also need 90 days of history and more than USD 50,000 lifetime spend; otherwise use observation and exclusion only. | - | Platform rule | [t1-google-cm-policy] |
| A Google upload includes EEA, UK or Swiss people. | Send consent for ad_user_data and ad_personalization with the upload, and leave out records without consent. Google does not process EEA data without consent for Customer Match. | - | Platform rule | [t1-google-cm-api] |
| You build a new automated Customer Match upload. | Use Google Data Manager or the Data Manager API. Since 1 April 2026 Google Ads API Customer Match uploads fail unless there was Customer Match activity between 1 October 2025 and 31 March 2026. | - | Platform rule | [t1-google-cm-api] |
| A Customer Match list has not been refreshed for a long time. | Refresh it. Membership lasts at most 540 days, and at least 100 members must be added or updated in that window to keep the list eligible. | - | Platform rule | [t1-google-cm-about] |
| You prepare a hashed file for Google. | Trim and lowercase emails; for gmail.com and googlemail.com remove dots and plus-suffixes; phones in E.164 with the plus sign (+4915112345678). Hash with SHA-256. | - | Platform rule | [t1-google-cm-format] |
| You prepare a hashed file for Meta. | Trim and lowercase emails (no gmail dot removal); phones as digits only with the country code, no plus sign, symbols or leading zero (4915112345678). Hash with SHA-256. Keep separate files per platform, or upload unhashed through each interface and let it hash. | - | Platform rule | [t1-meta-ca-file] |
| You add a custom audience or lookalike to a Meta Advantage+ audience. | Treat it as a suggestion; Meta can deliver beyond it. Only locations, minimum age, languages and custom audience exclusions are hard limits. | - | Platform rule | [t1-meta-adv-audience] |
| You use a lookalike in a new Meta ad set. | Expect Advantage+ lookalike to be on by default, which lets delivery go beyond the chosen percentage. | - | Platform rule | [t1-meta-adv-lookalike] |
| You build a Meta lookalike. | Use a seed of at least 100 matched people from at least one country. One lookalike can cover several countries. The API size range is 1% to 20%; in Ads Manager use the sizes offered. | - | Platform rule | [t1-meta-lookalike] |
| The ads are for housing, employment or financial products on Meta (US-based advertiser, or reaching the US, Canada or Europe). | Declare the Special Ad Category: lookalikes are not available, but custom audience inclusions and exclusions still are, within the category's audience limits. | - | Platform rule | [t1-meta-sac] |
| The ads fall in a Google sensitive interest category. | Do not use Customer Match or other advertiser-curated audiences. For US and Canada housing, employment and consumer finance ads, Customer Match is allowed, but age, gender, parental status, marital status and ZIP targeting are not. | - | Platform rule | [t1-google-personalized-ads] |
| A Meta win-back campaign must reach only people on the list. | Use "Further limit the reach of your ads" to make the custom audience inclusion a control; this may turn Advantage+ audience off, which is expected. | - | Platform rule | [t1-meta-audience-settings] |
| You need existing customers kept out of acquisition ads on Meta. | Use the customer list as a custom audience exclusion; exclusions are always controls. They only remove people Meta could match, so some customers will still see the ads. | - | Platform rule | [t1-meta-audience-settings] |
| A Meta list is under about 1,000 matched people. | Use it for exclusion or as a lookalike seed, not as the only targeting. On Google, check the list size per network in Audience manager. | about 1,000 matched people (rule of thumb) | Heuristic (rule of thumb) | - |

## Procedure

Copyable checklist:

- [ ] Check data and consent: First-party only. Privacy notice names ad partners. Recorded advertising consent for EEA, UK and Swiss records; a newsletter opt-in alone is not enough. Confirm with the privacy lead.
- [ ] Give each list one job: Exclude buyers, re-engage lapsed buyers, seed lookalikes, or observe for bidding.
- [ ] Check eligibility: Google: good history for any use; 90 days and USD 50,000 lifetime spend for targeting. Meta: lookalike seeds of 100 or more matched people. Regulated categories: no lookalikes on Meta Special Ad Categories; no advertiser-curated audiences in Google sensitive categories.
- [ ] Prepare files: Remove duplicates, test records and opt-outs. Normalise per platform (phones with + for Google, digits only for Meta). Hash with SHA-256, or upload unhashed through the interface.
- [ ] Upload: Google: Audience manager > Customer list, or Data Manager, with consent fields for EEA records. Meta: Audiences > Create audience > Custom audience > Customer list.
- [ ] Wait for processing: Do not launch campaigns that depend on an exclusion until the list shows as ready with a size.
- [ ] Attach to campaigns: Exclusions as controls. Inclusions as suggestions under Advantage+ or as Performance Max audience signals, after confirming the account may use the list that way.
- [ ] Refresh and remove: At least monthly (rule of thumb): add new consented customers and remove anyone who unsubscribed, withdrew consent or asked to be deleted. Never only append.

## Output template

```
## First-party audience plan: [BUSINESS]

### Data and consent
Source: [how collected] | Privacy notice names ad partners: [yes/no] | Advertising consent recorded: [n of total] | Confirmed by: [privacy lead]

### Lists
List | Job | Size | Platforms | Exclusion or suggestion

### Eligibility
Google: [exclusion and observation only / targeting allowed], because [history, spend]
Regulated categories: [none / ...]
Meta: lookalike seed size: [n matched], countries: [..]

### File preparation
Google: emails [rules], phones E.164 with + | Meta: emails [rules], phones digits only | Hash: SHA-256

### Upload route
Google: [Data Manager / Audience manager], consent fields: [set] | Meta: [Customer list custom audience]

### Suggestions vs controls
Setting | Google | Meta

### Refresh
[Cadence], opt-outs removed: [yes], next date: [date]
```

## Failure modes

| Mistake | Symptom | Fix |
|---|---|---|
| Uploading a purchased or event-partner list. | Policy breach risk and possible loss of Customer Match access. | Upload only data you collected directly, with a privacy notice that covers ad partners. |
| Treating a newsletter opt-in as consent for advertising. | GDPR risk; Google drops EEA records without consent. | Collect and record advertising consent separately. |
| One hashed file for both platforms. | Phone matches lost on one platform. | Normalise and hash per platform. |
| Expecting a Meta lookalike or custom audience to limit who sees the ad. | Delivery to people outside the list. | Under Advantage+ these are suggestions; use exclusions for hard limits. |
| Expecting an exclusion to remove every customer. | Existing customers still appear in "new customer" results. | Compare matched size with list size and add more identifiers. |
| Only ever appending to lists. | People who unsubscribed keep being targeted. | Remove opt-outs and deletion requests on every refresh. |
| Building a new Google Ads API Customer Match job. | Requests fail with CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE. | Use the Data Manager API. |
| Naming or building audiences around a health condition or income. | Meta flags the audience and blocks it. | Build audiences around behaviour with the business, such as purchase recency. |

## Verification

- [ ] Every uploaded record is first-party and has recorded advertising consent where required.
- [ ] Each list has one stated job.
- [ ] Google eligibility (exclusion only vs targeting) and regulated-category limits are stated.
- [ ] Files were normalised per platform before hashing.
- [ ] EEA uploads carry consent fields.
- [ ] A refresh schedule exists that removes opt-outs and fits the 540-day Google window.

## Agent mode

If an AI agent is operating a browser or API on your behalf:

**May do without asking:**
- Write the file preparation rules and check a small fake sample for formatting problems.
- Draft privacy-notice wording for the user to check with their adviser.
- Explain which audience settings are suggestions and which are controls.

**Must stop before (the user decides and does these):**
- Uploading any customer list or personal data to Google or Meta.
- Setting up or approving a CRM connector or automatic sync, which uploads personal data on an ongoing basis.
- Downloading or exporting customer lists from ad platforms or the CRM into chat.
- Attaching an audience to, or removing an exclusion from, a live campaign in a way that changes who you spend money on.
- Publishing or enabling any campaign or ad set.
- Accepting Custom Audience or Customer Match terms, or changing billing.

**Setup advice:**
- Never paste raw customer data into a chat AI. Use a small, fake sample to check the format.
- Do the upload yourself, from a trusted computer, through the platform or an approved CRM connector.

## Worked example

The figures below are illustrative. Never reuse them: use only the user’s own numbers and facts, and label anything they have not given as an ASSUMPTION.

**Scenario:** An EEA D2C brand selling in Germany, France and the Netherlands with 4,200 customer emails and phones.

**Input:** Checkout has a separate, unticked-by-default option to use the customer's details for personalised advertising on Google and Meta; 2,900 customers ticked it. The privacy notice names both. Goals: exclude buyers from prospecting, and seed a lookalike. Google account: 14 months old, EUR 30,000 lifetime spend, clean history.

**Output excerpt:** Upload only the 2,900 records with recorded advertising consent, with ad_user_data and ad_personalization granted on the Google upload. Google: lifetime spend is under USD 50,000, so use the list for exclusion and observation only. Meta: a separate file with phones as digits only; use it as an exclusion in prospecting ad sets, knowing unmatched customers will still see ads; build one 1% lookalike covering DE, FR and NL. Expect Advantage+ lookalike on by default. Monthly refresh from the CRM, removing anyone who unsubscribed or withdrew consent.

## References

### Platform settings

| Platform | Path | Setting | Note | Source |
|---|---|---|---|---|
| Google Ads | Tools > Shared library > Audience manager > Segments > Customer list | Customer Match list upload or Data Manager connection | Google recommends Data Manager for Customer Match workflows. | [t1-google-cm-about] |
| Google Data Manager API | Audience member ingestion with consent fields | Customer Match uploads with ad_user_data and ad_personalization consent | Replaces Google Ads API uploads since 1 April 2026 for developers without recent activity. | [t1-google-cm-api] |
| Meta Ads Manager | Audiences > Create audience > Custom audience > Customer list | Customer list custom audience, or exclusion-only customer list | - | [t1-meta-ca-types] |
| Meta Ads Manager | Ad set > Audience > Controls > Show more controls | Custom audience exclusion (always a control) | - | [t1-meta-audience-settings] |
| Meta Ads Manager | Ad set > Audience > Add suggestions | Custom audience inclusion as a suggestion; Advantage+ lookalike | - | [t1-meta-adv-lookalike] |

### Sources

| ID | Title | Tier | Accessed on | URL |
|---|---|---|---|---|
| t1-google-cm-policy | Customer Match policy | T1 | 2026-10-22 | https://support.google.com/adspolicy/answer/6299717 |
| t1-google-cm-about | About Customer Match | T1 | 2026-10-22 | https://support.google.com/google-ads/answer/6379332 |
| t1-google-cm-api | Customer Match (Google Ads API) get started | T1 | 2026-10-22 | https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started |
| t1-google-cm-format | Format user data (Data Manager API) | T1 | 2026-10-22 | https://developers.google.com/data-manager/api/devguides/concepts/formatting |
| t1-google-personalized-ads | Personalized advertising policy | T1 | 2026-10-22 | https://support.google.com/adspolicy/answer/143465 |
| t1-meta-sac | Special Ad Category | T1 | 2026-10-22 | https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/special-ad-category |
| t1-meta-ca-types | About custom audiences | T1 | 2026-10-22 | https://www.facebook.com/business/help/744354708981227 |
| t1-meta-ca-file | Customer file custom audiences | T1 | 2026-10-22 | https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/guides/custom-audiences |
| t1-meta-lookalike | Lookalike audiences | T1 | 2026-10-22 | https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/guides/lookalike-audiences |
| t1-meta-adv-audience | Advantage+ audience (Marketing API) | T1 | 2026-10-22 | https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/reference/targeting-expansion/advantage-audience |
| t1-meta-adv-lookalike | About Advantage+ lookalike | T1 | 2026-10-22 | https://www.facebook.com/business/help/1212225059146059 |
| t1-meta-audience-settings | Choose audience settings in Advantage+ campaigns | T1 | 2026-10-22 | https://www.facebook.com/business/help/25941857932125812 |

---
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment matters need a qualified professional.
