mbfinotti/advertising-skills / skills/lookalike-audience-seeds
lookalike-audience-seeds
VerifiedSelect and size the seed customer list behind a lookalike, similar, or value-based audience - which customers to upload, how many, and whether the matched count (not the row count) clears the platform floor - with RFM and value-based selection, a negative-selection pass, a privacy and consent gate before any customer list upload, and a fallback ladder when the floor cannot be cleared. Use whenever the user mentions a lookalike or similar audience, a seed list, a customer list upload, match rate, an audience that is too small, or says their lookalike isn't working - even if they never say 'seed'. Covers B2B and B2C. Do NOT use to design the whole targeting tier structure - use mbfinotti/advertising-skills@ad-audience-targeting instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 33.7 KB |
| evals/evals.json | config | 40.4 KB |
| references/examples.md | markdown | 6.4 KB |
| references/platform-floors.md | markdown | 14.4 KB |
| references/seed-selection.md | markdown | 14.3 KB |
references/platform-floors.md
View on GitHub# Platform Floors, Match Rates, and Refresh Behavior
Figures verified against official documentation or attributed practitioner sources as of **August 2026**. These numbers move - Google cut Customer Match from 1,000 to 100 in 2025, and Demand Gen reach tiers convert to signals around March 2026 - so verify against the platform's live documentation before finalizing any spec. Where a platform's own pages disagree, both figures are shown. **Plan against the stricter one**.
## Floors and recommended sizes
All floors apply to the **matched** count, not uploaded rows.
| Platform | Matched floor | Recommended seed | Expansion tiers | Notes |
| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Meta | 100 matched people (customer list); 100 unique conversions (conversion-based) | 1,000-5,000 (Meta developer docs and Business Help Center); 200+ converters for conversion-based seeds | 1%-10% of a chosen country (API allows up to 20% in 1-point steps) | Country-scoped by construction. "Advantage+ lookalike" replaced lookalike expansion; inclusions behave as suggestions. The widely repeated 1,000-50,000 sweet spot is practitioner guidance, not Meta's figure. |
| Google Customer Match | 100 members (cut from 1,000 in 2025) | 1,000+ for a usable optimization signal (practitioner) | Similar Audiences REMOVED Aug 1, 2023 (new segments stopped generating May 2023) | SHA-256 hashing. Members not added/refreshed within 540 days drop out of eligibility (official). |
| Google Demand Gen lookalike | 1,000 active matched (API docs); Help Center also cites 100 - **take 1,000** | - | Narrow 2.5% / Balanced 5% / Broad 10% of target location | Country-scoped; refreshes every 1-2 days; reach tiers become signals ~March 15, 2026. |
| LinkedIn Matched Audiences / Predictive Audiences | 300 matched members to serve | Contact list: upload 10,000+ emails; company list: 1,000+ companies (LinkedIn recommendation) | Lookalikes SUNSET Feb 29, 2024 -> Predictive Audiences (300 min, max 30 per ad account) | Contact list 300-300,000 rows, 20MB cap. Company lists dedupe on match, so padding rows is harmless. |
| TikTok | 1,000 for custom audience/lookalike source (Help Center); FAQ mentions 100 after mapping - **take 1,000** | 10,000 (practitioner) | Narrow / Balanced / Broad (~1% / 5% / 10%) | 24-48h processing; one Help article says a lookalike cannot be built directly from an email list. |
| Pinterest | 100 (Actalike source and customer list) | 1,000+ (practitioner) | Actalike 1%-10% (API caps at 10%; countries US/CA/GB) | Auto-refreshes as the source changes. |
| Reddit | 1,000 matched (25 via LiveRamp); max 1 million | - | Native reach expansion via automated targeting | Native CSV match ~2% (pseudonymous accounts); enrichment vendors claim 50-70%. Accepts hashed email and hashed mobile-ad-ID. |
| X | 100 matched to target (lowered from 500); audiences under 500 not shown in the interface | - | Follower look-alikes; custom-audience lookalikes | Match rate defined as 90-day active users / provided (official). |
| Amazon DSP / AMC | AMC lookalike seed 500 user IDs; rule-based audiences 2,000; DSP activation floors ~1,000 | 10,000+ for stable retargeting; 100,000+ for prospecting reach (practitioner) | AMC/DSP lookalike expansion | Matched counts below ~1,000 are rounded or hidden for privacy (documented by sync-tool vendors). |
| Snapchat | 1,000 to run an ad | - | Similarity / Balance / Reach | Lookalike updates as the seed updates. |
| Microsoft Ads | ~1,000 historical Customer Match minimum; Similar Audiences deprecated | - | - | Consistent with the industry-wide similar-audience deprecation trend. |
## Deprecations - stale-playbook markers
- **Google Similar Audiences**: removed from all ad groups and campaigns starting August 1, 2023. Any plan citing them is outdated. First-party lists now act as signals for optimized targeting and Demand Gen lookalikes.
- **LinkedIn Lookalike Audiences**: sunset February 29, 2024, replaced by Predictive Audiences (300-member minimum, max 30 per ad account).
- **Meta detailed-targeting exclusions**: removed March 31, 2025. Only custom-audience exclusions under Audience Controls remain hard suppression rules. Custom-audience inclusions became suggestions.
## Expected match rates
Use these to compute the effective seed. Adjust down for old lists and single-identifier rows.
| Platform | Typical match rate | Source type |
| ------------------------------------------------ | -------------------------------------------------------------------------------- | ----------------------------------------- |
| Google Customer Match | 29-62% "most advertisers"; 70-90% clean lists; phone-only 30-50% | Official (Google Ads Help) + practitioner |
| Meta | 50-80% good lists; below 40% signals a poor/outdated list; 30-60% commonly cited | Practitioner, attributed to Meta guidance |
| LinkedIn | ~30-40% on work-email contact lists; higher for company lists | Practitioner + LinkedIn Help |
| TikTok / consumer platforms with B2B work emails | Under ~5% on raw CRM work-email exports; ~40-85% after identity enrichment | Practitioner (enrichment vendors) |
| Reddit | ~2% native CSV; 50-70% after enrichment | Practitioner |
| Amazon DSP | 40-70% hashed email | Practitioner |
**What lifts match rate**, ordered by efficiency - `normalize formats > join identifiers already held > drop rows past 18 months > buy identity enrichment`:
- **Normalize the formats already in hand**: minutes, a transform in the export query, reversible, no approvals, and it lifts every row at once. The most common single cause of a rate below the platform's documented band, so always first.
- Emails lowercased and trimmed.
- Phone as digits with country code, no plus sign, no leading zero (E.164-style, e.g. 14155552671).
- Never pre-hash a UI upload, since platforms hash on ingest and a salted hash never matches.
- **Join identifiers the business already holds** - phone, name, location sitting in another table. Multiple identifiers per row beating email alone is the documented multiplier, and here it costs about an hour of joining and no procurement. Email stays the anchor identifier.
- **Drop rows past 18 months** - minutes, but a trade rather than a gain: the rate rises partly because the denominator shrinks. Never run it on a list already near its floor, and never let it flatter a spec whose effective seed then fails.
- **Buy identity enrichment** - a week or more of coordination (vendor selection, security review, sign-off, match test), plus a DPA, a lawful-basis re-check that covers enrichment and not only upload, and the hardest reversal of the four once contracted. Lowest ratio in general; unbeatable in exactly one case, a B2B work-email list on a consumer platform, where the three levers above cannot move a ~5% native match anywhere near a floor.
Meta exposes an Event Match Quality (EMQ) score with a practitioner target of 6.0+. Re-rank against the user: an enrichment contract already signed moves the last lever to the top, since both its setup and its DPA are already paid for. A warehouse holding no second identifier anywhere removes the second lever entirely.
## Refresh behavior
| Mechanism | Auto-refreshes? | Guidance |
| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Pixel/engagement-sourced audiences | Yes (Meta lookalikes roughly every 3-7 days; Demand Gen every 1-2 days; Pinterest as the source changes) | Keep the source rule healthy; nothing manual needed |
| Static CSV uploads (LinkedIn lists, manual Meta customer lists) | No | Practitioner cadence: weekly for active customer-list campaigns, bi-weekly to monthly for lookalike seeds, weekly for suppression lists |
| Google Customer Match membership | No - members expire | Members not added or refreshed within 540 days become ineligible (official) |
| Warehouse/CDP automated sync (reverse ETL) | Yes - adds and removes continuously | The dominant modern pattern; manual CSV is a stale-list risk with a named-owner maintenance burden |
Choosing between the two mechanisms the advertiser controls: `automated warehouse sync > static CSV` on efficiency, even though the CSV wins on effort - roughly a day or two of engineering once, against near-zero to start and then a standing job forever. The sync also wins on compliance cost, which is the argument that usually settles it: it propagates opt-outs and deletion requests continuously, while a manual CSV re-uploads yesterday's opt-outs every cycle and puts the lawful basis back in question each time. The ordering flips only where no engineering capacity exists at all, and there the honest answer is a CSV on a shorter cadence, not a sync that never ships.
Data older than 12-18 months produces both lower match rates and worse performance - decay both ways.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |