Performance Marketing skill 12 of 13

Audiences and First-Party Data for Paid Media SKILL.md

The Audiences and First-Party Data skill makes Claude, Codex or another AI agent build audiences for Google, Meta, TikTok, LinkedIn and Microsoft from data only you have. It checks legal basis and consent, defines customer and lead segments, sets up Customer Match and Custom Audiences with automated syncs, excludes existing customers from acquisition, seeds lookalikes and signals by value, improves match rates and documents governance.

audience-first-party-data/SKILL.md, version 1.0.0, 1,487 words.

As platforms automate targeting, the most valuable audience inputs are the ones only you have: your customers, your leads, their value and their behaviour. Customer lists tell platforms who to exclude, who to find more of and who is worth more. Used well, first-party data improves acquisition efficiency and stops you paying to reach people who already buy. Used carelessly, it breaks privacy rules and trust.

This skill builds a first-party audience strategy for Google, Meta, TikTok, LinkedIn and Microsoft: consented data collection, customer match and custom audiences, exclusions, lookalikes and value-based seeds, audience signals for automated campaigns and governance.

Operating principles

  1. Consent and transparency first. Use customer data for advertising only where your privacy notice and legal basis allow it.
  2. Exclude before you include. Stopping spend on existing customers (for acquisition goals) is often the fastest win.
  3. Seed with value. Lookalikes and signals built from high-value customers beat lists of everyone.
  4. Keep lists fresh. Automate syncs from your CRM or commerce platform.
  5. Audiences are signals, not walls. In automated campaigns, lists guide the system; creative and goals still decide delivery.

Audience types and uses

AudienceSourceUse
All customersCRM or commerce platformExclude from acquisition; separate reporting
High-value customersTop spend or LTV segmentLookalike and signal seeds; value-based bidding inputs
Recent purchasersLast 30 to 90 daysExclude from promotions; cross-sell where relevant
Lapsed customersNo purchase in the normal cycleWin-back campaigns (where consent and law allow)
Leads and pipeline stagesCRMExclude closed customers; target open opportunities in B2B
Site and app visitorsPixels and SDKsRetargeting (test incrementality)
Engaged video viewersPlatform dataMid-funnel sequencing
Target accounts (B2B)ABM listsLinkedIn and Google account targeting

When to use, and when not to

Use it when campaigns spend on existing customers, when lookalikes underperform, when setting up customer match for the first time, before Black Friday or peak, and when moving to new-customer goals.

Don't use it to fix conversion tracking (conversion-tracking-capi) or lifecycle messaging (the CRM and Lifecycle skills).

Inputs to ask for, in one message

  1. CRM or commerce platform and customer data fields available (email, phone, value, dates).
  2. Privacy notice and consent records for advertising use.
  3. Current audiences in each platform and how they are refreshed.
  4. Campaign goals: new customers, revenue, leads, retention.
  5. Customer value data (LTV, order history) for value-based seeds.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as audience-first-party-data/SKILL.md.

---
name: audience-first-party-data
description: "Build first-party audiences for Google, Meta, TikTok, LinkedIn and Microsoft: legal basis and consent checks, customer and lead segments, Customer Match and Custom Audiences with automated syncs, existing-customer exclusions and new-customer goals, value-based lookalikes and audience signals, match rate improvements and data governance. Use whenever someone asks about customer match, custom audiences, lookalike audiences, excluding existing customers, first-party data for ads, audience signals for PMax or Advantage+, or ABM account lists."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/performance-marketing/audience-first-party-data/
  category: marketing
  subcategory: performance-marketing
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Audiences and First-Party Data for Paid Media

As platforms automate targeting, the most valuable audience inputs are the ones only you have: your customers, your leads, their value and their behaviour. Customer lists tell platforms who to exclude, who to find more of and who is worth more. Used well, first-party data improves acquisition efficiency and stops you paying to reach people who already buy. Used carelessly, it breaks privacy rules and trust.

This skill builds a first-party audience strategy for Google, Meta, TikTok, LinkedIn and Microsoft: consented data collection, customer match and custom audiences, exclusions, lookalikes and value-based seeds, audience signals for automated campaigns and governance.

## Operating principles
1. **Consent and transparency first.** Use customer data for advertising only where your privacy notice and legal basis allow it.
2. **Exclude before you include.** Stopping spend on existing customers (for acquisition goals) is often the fastest win.
3. **Seed with value.** Lookalikes and signals built from high-value customers beat lists of everyone.
4. **Keep lists fresh.** Automate syncs from your CRM or commerce platform.
5. **Audiences are signals, not walls.** In automated campaigns, lists guide the system; creative and goals still decide delivery.

## Audience types and uses
| Audience | Source | Use |
|---|---|---|
| All customers | CRM or commerce platform | Exclude from acquisition; separate reporting |
| High-value customers | Top spend or LTV segment | Lookalike and signal seeds; value-based bidding inputs |
| Recent purchasers | Last 30 to 90 days | Exclude from promotions; cross-sell where relevant |
| Lapsed customers | No purchase in the normal cycle | Win-back campaigns (where consent and law allow) |
| Leads and pipeline stages | CRM | Exclude closed customers; target open opportunities in B2B |
| Site and app visitors | Pixels and SDKs | Retargeting (test incrementality) |
| Engaged video viewers | Platform data | Mid-funnel sequencing |
| Target accounts (B2B) | ABM lists | LinkedIn and Google account targeting |

## When to use, and when not to
Use it when campaigns spend on existing customers, when lookalikes underperform, when setting up customer match for the first time, before Black Friday or peak, and when moving to new-customer goals.

Don't use it to fix conversion tracking (`conversion-tracking-capi`) or lifecycle messaging (the CRM and Lifecycle skills).

## Inputs to ask for, in one message
1. CRM or commerce platform and customer data fields available (email, phone, value, dates).
2. Privacy notice and consent records for advertising use.
3. Current audiences in each platform and how they are refreshed.
4. Campaign goals: new customers, revenue, leads, retention.
5. Customer value data (LTV, order history) for value-based seeds.

## Workflow

### Step 1. Check legal basis
Confirm the privacy notice covers advertising use and that consent where required is recorded. Exclude people who opted out.

### Step 2. Build core segments
All customers, high-value customers, recent buyers, lapsed customers, leads by stage.

### Step 3. Upload and sync
Customer Match (Google), Custom Audiences (Meta), TikTok and LinkedIn matched audiences; hashed identifiers; automated daily or weekly syncs through native integrations or a CDP.

### Step 4. Apply exclusions
Exclude existing customers from acquisition campaigns or use new-customer goals and budget caps; exclude recent purchasers from discount campaigns.

### Step 5. Build lookalikes and signals
Seed lookalikes and audience signals with high-value customers; test seed size and value weighting.

### Step 6. Pass values
Value-based lookalikes where platforms support them; value rules or new-customer values in bidding.

### Step 7. Measure
New-customer share, CAC from your own data, match rates and audience sizes.

### Step 8. Govern
Document sources, refresh schedules, owners and retention; remove data on request.

## Match rate tips
- Upload email and phone (E.164 format) together where consented.
- Normalise data (lowercase emails, trimmed spaces) before hashing or let the platform hash.
- Include first name, last name, country and postcode where platforms accept them.
- Expect lower match rates for B2B work emails on consumer platforms.

## Seed quality experiment
| Seed | Size | Expectation |
|---|---|---|
| All customers | Large | Broad reach, average quality |
| Repeat customers | Medium | Better quality |
| Top 20% by 12-month value | Smaller | Highest quality, may limit scale |
| High-value with value weighting (where supported) | Varies | Balances scale and quality |
Test two or three seeds in parallel and judge on new-customer CAC and 90-day value, not just first-order CPA.

## Sync options
| Method | Pros | Cons |
|---|---|---|
| Native platform integrations (Shopify, HubSpot, Klaviyo) | Easy, automatic | Limited segment logic |
| CDP (Segment, RudderStack, Hightouch) | One definition across platforms | Cost and setup |
| Manual CSV uploads | No tools needed | Goes stale; error-prone |
Aim for daily syncs for customer exclusions; weekly is acceptable for lookalike seeds.

## Peak season preparation
- Refresh all customer lists two weeks before peak.
- Create a recent-purchasers exclusion for discount campaigns.
- Build lapsed-customer audiences for win-back offers (where lawful).
- Check match rates and audience sizes meet platform minimums.
- Agree new versus returning customer goals for the peak period.

## Governance checklist
- Source system and definition for each audience.
- Refresh schedule and owner.
- Consent basis and exclusions for opt-outs.
- Retention period and deletion process.
- Record of which platforms receive which data.

## Exclusion setup by platform
| Platform | How to exclude or cap existing customers |
|---|---|
| Google Ads (PMax, Search) | Customer Match lists with new-customer acquisition goal, or audience exclusions where supported |
| Meta (Advantage+) | Existing customer definitions and budget cap for existing customers |
| TikTok | Custom audience exclusions in ad groups |
| LinkedIn | Matched audience exclusions for customers and employees |
Check each platform's current settings; options change frequently.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Small customer list | Seed with broader valuable groups (repeat buyers) and accept lower precision |
| Strict consent market | Use only consented records; rely more on contextual and broad targeting |
| B2B on consumer platforms | Use LinkedIn for account targeting; consumer platforms for retargeting |
| Existing customers drive most conversions | Separate goals and reporting; test whether those ads are incremental |
| Data in many systems | Use a CDP or warehouse sync to keep one definition per audience |

## Handoffs to related skills
- Tracking and values: `conversion-tracking-capi`
- PMax new-customer goals: `performance-max-shopping`
- Meta Advantage+ customer settings: `meta-ads`
- LinkedIn account targeting: `paid-social-tiktok-linkedin`
- Data hygiene and consent records: the CRM and Lifecycle `crm-data-hygiene` skill

## Worked example
A fashion retailer found that a large share of Meta and PMax conversions came from existing customers. Customer lists hadn't been refreshed in months, and lookalikes were seeded from all past buyers. A daily sync from the commerce platform fed fresh customer lists, existing customers were capped in Advantage+ and excluded from PMax acquisition goals, and lookalikes were reseeded from the top 20% by 12-month value. New-customer share rose and new-customer CAC fell, while a separate retention campaign served existing customers with appropriate offers.

## Output format
```
# First-party audience plan: <business>, <date>
## Legal basis and consent check
## Core segments (definition, size, refresh)
## Platform uploads and sync method
## Exclusions and new-customer settings
## Lookalikes and signals (seeds, value weighting)
## Measurement and governance
```

## Common mistakes
- Using customer data without a legal basis for advertising.
- Stale lists that never refresh.
- Seeding lookalikes from everyone instead of valuable customers.
- Paying acquisition prices for existing customers.
- Treating audience lists as hard targeting in automated campaigns.

## Questions to ask before you build
- Does your privacy notice cover advertising use of customer data?
- Which customers are most valuable, and can you identify them?
- Do campaigns need new customers or total revenue?

## Self-check before you answer
- Is the legal basis confirmed and opt-outs excluded?
- Are customer lists synced automatically and fresh?
- Are exclusions and new-customer goals set for acquisition?
- Are seeds value-based?

## Official documentation
- Google Customer Match: https://support.google.com/google-ads/answer/6379332
- Meta Business Help Centre (Custom Audiences): https://www.facebook.com/business/help
- LinkedIn Marketing Solutions help (Matched Audiences): https://www.linkedin.com/help/lms
- UK ICO guidance on direct marketing and advertising technologies: https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/performance-marketing/audience-first-party-data/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Confirm the privacy notice covers advertising use and that consent where required is recorded. Exclude people who opted out.

Step 2. Build core segments

All customers, high-value customers, recent buyers, lapsed customers, leads by stage.

Step 3. Upload and sync

Customer Match (Google), Custom Audiences (Meta), TikTok and LinkedIn matched audiences; hashed identifiers; automated daily or weekly syncs through native integrations or a CDP.

Step 4. Apply exclusions

Exclude existing customers from acquisition campaigns or use new-customer goals and budget caps; exclude recent purchasers from discount campaigns.

Step 5. Build lookalikes and signals

Seed lookalikes and audience signals with high-value customers; test seed size and value weighting.

Step 6. Pass values

Value-based lookalikes where platforms support them; value rules or new-customer values in bidding.

Step 7. Measure

New-customer share, CAC from your own data, match rates and audience sizes.

Step 8. Govern

Document sources, refresh schedules, owners and retention; remove data on request.

Match rate tips

  • Upload email and phone (E.164 format) together where consented.
  • Normalise data (lowercase emails, trimmed spaces) before hashing or let the platform hash.
  • Include first name, last name, country and postcode where platforms accept them.
  • Expect lower match rates for B2B work emails on consumer platforms.

Seed quality experiment

SeedSizeExpectation
All customersLargeBroad reach, average quality
Repeat customersMediumBetter quality
Top 20% by 12-month valueSmallerHighest quality, may limit scale
High-value with value weighting (where supported)VariesBalances scale and quality

Test two or three seeds in parallel and judge on new-customer CAC and 90-day value, not just first-order CPA.

Sync options

MethodProsCons
Native platform integrations (Shopify, HubSpot, Klaviyo)Easy, automaticLimited segment logic
CDP (Segment, RudderStack, Hightouch)One definition across platformsCost and setup
Manual CSV uploadsNo tools neededGoes stale; error-prone

Aim for daily syncs for customer exclusions; weekly is acceptable for lookalike seeds.

Peak season preparation

  • Refresh all customer lists two weeks before peak.
  • Create a recent-purchasers exclusion for discount campaigns.
  • Build lapsed-customer audiences for win-back offers (where lawful).
  • Check match rates and audience sizes meet platform minimums.
  • Agree new versus returning customer goals for the peak period.

Governance checklist

  • Source system and definition for each audience.
  • Refresh schedule and owner.
  • Consent basis and exclusions for opt-outs.
  • Retention period and deletion process.
  • Record of which platforms receive which data.

Exclusion setup by platform

PlatformHow to exclude or cap existing customers
Google Ads (PMax, Search)Customer Match lists with new-customer acquisition goal, or audience exclusions where supported
Meta (Advantage+)Existing customer definitions and budget cap for existing customers
TikTokCustom audience exclusions in ad groups
LinkedInMatched audience exclusions for customers and employees

Check each platform's current settings; options change frequently.

Edge cases and judgement calls

SituationWhat to do
Small customer listSeed with broader valuable groups (repeat buyers) and accept lower precision
Strict consent marketUse only consented records; rely more on contextual and broad targeting
B2B on consumer platformsUse LinkedIn for account targeting; consumer platforms for retargeting
Existing customers drive most conversionsSeparate goals and reporting; test whether those ads are incremental
Data in many systemsUse a CDP or warehouse sync to keep one definition per audience
  • Tracking and values: conversion-tracking-capi
  • PMax new-customer goals: performance-max-shopping
  • Meta Advantage+ customer settings: meta-ads
  • LinkedIn account targeting: paid-social-tiktok-linkedin
  • Data hygiene and consent records: the CRM and Lifecycle crm-data-hygiene skill

Worked example

A fashion retailer found that a large share of Meta and PMax conversions came from existing customers. Customer lists hadn't been refreshed in months, and lookalikes were seeded from all past buyers. A daily sync from the commerce platform fed fresh customer lists, existing customers were capped in Advantage+ and excluded from PMax acquisition goals, and lookalikes were reseeded from the top 20% by 12-month value. New-customer share rose and new-customer CAC fell, while a separate retention campaign served existing customers with appropriate offers.

Output format

# First-party audience plan: <business>, <date>
## Legal basis and consent check
## Core segments (definition, size, refresh)
## Platform uploads and sync method
## Exclusions and new-customer settings
## Lookalikes and signals (seeds, value weighting)
## Measurement and governance

Common mistakes

  • Using customer data without a legal basis for advertising.
  • Stale lists that never refresh.
  • Seeding lookalikes from everyone instead of valuable customers.
  • Paying acquisition prices for existing customers.
  • Treating audience lists as hard targeting in automated campaigns.

Questions to ask before you build

  • Does your privacy notice cover advertising use of customer data?
  • Which customers are most valuable, and can you identify them?
  • Do campaigns need new customers or total revenue?

Self-check before you answer

  • Is the legal basis confirmed and opt-outs excluded?
  • Are customer lists synced automatically and fresh?
  • Are exclusions and new-customer goals set for acquisition?
  • Are seeds value-based?

Official documentation

When to use this skill, and when not to

Use it when campaigns spend on existing customers, when lookalikes underperform, when setting up customer match for the first time, before peak season and when moving to new-customer goals.

As platforms automate targeting, the most valuable audience inputs are your customers, their value and their behaviour. Customer lists tell platforms who to exclude, who to find more of and who is worth more. Used carelessly, the same data breaks privacy rules and trust, so the skill starts with legal basis.

Don’t use it to fix tracking (use Conversion Tracking) or for lifecycle messaging (use the CRM and Lifecycle skills).

Example prompts

  • “Stop paying acquisition prices for existing customers.”
  • “Set up daily customer list syncs from Shopify to Google and Meta.”
  • “Which customers should seed our lookalikes?”
  • “Prepare our audiences for Black Friday.”
  • “Improve our Customer Match rate.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# First-party audience plan: example fashion retailer, 10 October 2026

## Segments
| Audience | Definition | Use | Refresh |
| All customers | Any order, consented | Exclude from acquisition | Daily |
| High value | Top 20% by 12-month value | Lookalike and signal seed | Weekly |
| Recent buyers | Last 30 days | Exclude from discount campaigns | Daily |
| Lapsed | No order in 180 days | Win-back (where lawful) | Weekly |

## Settings
Advantage+ existing-customer cap; PMax new-customer goal

Only consented records are used, and people who opted out are excluded from every upload.

What the agent needs from you

The skill asks for your CRM or commerce platform and the customer fields available, your privacy notice and consent records for advertising use, current audiences in each platform and how they refresh, campaign goals and customer value data such as lifetime value and order history.

How this skill hands off to related skills

Audiences connect to tracking and channels. Values come from Conversion Tracking, new-customer goals from Performance Max, customer settings from Meta Ads, account targeting from TikTok and LinkedIn, and consent records from the CRM and Lifecycle CRM Data Hygiene skill.

How to run Audiences and First-Party Data step by step

  1. Install the skill as audience-first-party-data/SKILL.md.
  2. Confirm legal basis: privacy notice and consent records for advertising use.
  3. List customer fields available in your CRM or commerce platform.
  4. Export current audiences and how they refresh.
  5. Review segments, sync method, exclusions and seeds.
  6. Automate syncs and track new-customer share and CAC.

Situations this skill handles

Audience problems usually mean paying for the wrong people. The skill handles these situations:

SituationWhat the skill does
Existing customers dominate conversionsSeparates goals, caps or excludes customers
Stale customer listsAutomates daily syncs
Weak lookalikesReseeds from high-value customers
Strict consent marketsUses only consented records
B2B on consumer platformsUses LinkedIn for account targeting
Data spread across systemsSyncs through a CDP or warehouse with one definition

What makes this skill different

Most audience advice focuses on building ever more retargeting lists. This skill starts with exclusions and value: stop paying acquisition prices for people who already buy, then seed lookalikes and signals from your most valuable customers, all on a confirmed legal basis.

It treats audiences in automated campaigns as signals that guide delivery, not as walls, and keeps governance documented so data use stays defensible.

Practical tips from real projects

  • Exclude before you include.
  • Seed with value, not volume.
  • Automate syncs; stale lists waste money.
  • Document sources, owners and retention.

A worked example: a fashion retailer found that a large share of Meta and Performance Max conversions came from existing customers. Lists hadn’t been refreshed in months, and lookalikes were seeded from all past buyers. A daily sync from the commerce platform, an existing-customer cap in Advantage+, PMax acquisition goals with customer exclusions and lookalikes reseeded from the top 20% by 12-month value raised new-customer share and cut new-customer CAC, while a separate retention campaign served existing customers with appropriate offers.

Audience types each have a job. All customers are excluded from acquisition. High-value customers seed lookalikes and signals. Recent purchasers are excluded from promotions. Lapsed customers fuel win-back where consent and law allow. Leads and pipeline stages support B2B targeting. Site and app visitors power retargeting, which should be tested for incrementality. Engaged video viewers support sequencing. Target accounts drive LinkedIn and Google account targeting.

Seed experiments compare all customers, repeat customers, the top 20% by value and value-weighted seeds where platforms support them, judged on new-customer CAC and 90-day value rather than first-order CPA.

Peak season preparation follows a short list: refresh lists two weeks before peak, create recent-purchaser exclusions for discount campaigns, build lapsed audiences for win-back, check match rates and minimum sizes and agree new versus returning goals.

Sync options trade simplicity for control: native integrations from Shopify, HubSpot or Klaviyo are easy but limited; CDPs such as Segment, RudderStack or Hightouch give one definition across platforms at extra cost; manual CSV uploads need no tools but go stale and invite errors.

Match rates decide how useful lists are. Uploading email and phone together in E.164 format where consented, normalising data before hashing (or letting the platform hash it), and including first name, last name, country and postcode where accepted all raise match rates. B2B work emails usually match less well on consumer platforms, which is one reason LinkedIn suits account targeting. Governance closes the loop: each audience has a documented source, refresh schedule, owner, consent basis, retention period and a record of which platforms receive it, so requests to delete data can be honoured quickly and audits are easy to pass.

Frequently asked questions

Google’s feature for uploading hashed customer data to target, exclude or inform bidding for your customers across Search, Shopping, YouTube and more.

From acquisition campaigns, usually yes, or use new-customer goals and budget caps. Run separate campaigns for existing customers if needed.

High-value customers, such as the top 20% by 12-month value, often beat lists of everyone. Test seeds in parallel.

You need a legal basis and a privacy notice that covers advertising use, with consent where the law requires it. People who opted out must be excluded.

Daily for customer exclusions and weekly for lookalike seeds, ideally automated through native integrations or a CDP.

Upload email and phone together where consented, normalise data, and include name, country and postcode where platforms accept them.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.