---
title: Lookalike Audience Seeds Skill for Claude Code
canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/lookalike-audience-seeds
content_type: text/markdown
description: "lookalike-audience-seeds by mbfinotti - This skill selects and sizes the seed customer list behind a lookalike, similar or value-based audience."
---

# Lookalike Audience Seeds Skill

Title: Lookalike Audience Seeds Skill for Claude Code

> lookalike-audience-seeds by mbfinotti - This skill selects and sizes the seed customer list behind a lookalike, similar or value-based audience.

Canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/lookalike-audience-seeds

This skill selects and sizes the seed customer list behind a lookalike, similar or value-based audience. It covers which customers to upload, how many, whether the matched count clears the platform floor, and a privacy and consent gate. A solo founder reaches for it before uploading a customer list to an ad platform.

## Key facts

- Installs: 26,696
- GitHub stars: 2
- Author: mbfinotti
- Repository: mbfinotti/advertising-skills
- Install command: `npx skills add https://github.com/mbfinotti/advertising-skills --skill lookalike-audience-seeds`
- Last updated: October 26, 2026

## What Lookalike Audience Seeds does

Chooses and sizes the customer seed list behind a lookalike audience, checking that matched users clear the platform minimum.

Lookalike seeds are too small or unrepresentative to work.

A seed list sized to clear the platform floor.

Best for: Founders with a customer list to seed paid lookalikes.

Not for: Brands with too few customers to match.

- RFM and value-based seed selection
- Matched count must clear platform floor
- Privacy and consent gate before upload

## SKILL.md

## Lookalike Seeds

Select, size, and validate the seed customer list that a lookalike, similar, or value-based audience will be built from. Three principles govern every step below:

- **Match count, not row count** - every uploaded list shrinks by its match rate before it reaches the platform's minimum. A 40% match on 5,000 rows is a 2,000-person seed, and the platform floor applies to that matched number - upload 2-3x the target.
- **Homogeneity and value concentration beat size** - Meta's own guidance holds that a seed's homogeneity affects audience effectiveness more than its size. Practitioner consensus (Stackmatix, Grow With Sakib - directional, not audited) is that a few hundred high-value customers outperform thousands of undifferentiated subscribers.
- **Inclusion is a suggestion, exclusion is a rule** - on Meta (Advantage+) and Google (Demand Gen, where lookalike reach tiers now function as signals rather than hard segments), the delivery algorithm may override an inclusion audience. Only exclusion/suppression audiences remain hard rules.

The seed's job is feeding the algorithm the cleanest signal, not fencing an audience - which raises the quality bar rather than removing it.

This skill ends at a specified, validated seed definition plus its export/handoff spec. It never walks through creating or uploading the audience inside any ad platform's interface.

Where each adjacent concern lives:

- Overall targeting plan (interest, behavioural, lookalike, and retargeting tier layering) - seed mechanics live here, tier architecture lives in `mbfinotti/advertising-skills@ad-audience-targeting`.
- Retargeting sequence design, audience windows per funnel stage, and frequency caps - `mbfinotti/advertising-skills@retargeting-funnel`.
- B2B buying-committee and persona mapping - `mbfinotti/advertising-skills@ad-buyer-group-mapper`.
- Root-causing broad account underperformance - `mbfinotti/advertising-skills@ad-account-diagnostic`.
- Pixel/CAPI instrumentation feeding engagement-based seed sources - `mbfinotti/advertising-skills@ad-conversion-tracking`.
- Reconciling conflicting performance reads on a seed across attribution sources - `mbfinotti/advertising-skills@ad-attribution-gap`.

### Interview

Ask before selecting anything. One question per message; offer multiple-choice answers where possible; skip anything already answered or visible in supplied data.

- B2B, B2C/ecommerce, or both?
- Which platform(s) will consume the seed? (Meta / Google / LinkedIn / TikTok / other - floors and match mechanics differ)
- What customer data exists, and where does it live? (CRM / data warehouse / email platform / pixel-and-platform events only / almost none)
- Roughly how many total customers, and which identifiers exist per row? (email / phone / name / postal address / mobile ad ID - more identifier types per row lift match rate)
- Is there a usable value column - and what does it actually measure: cumulative lifetime revenue, margin, predicted LTV, or just order count? Provenance matters more than presence.
- How recent is the data - what share of the list purchased or converted within the last 90 and 180 days?
- Does the list contain EEA/UK residents or US state-privacy-covered consumers? Is there a documented consent or lawful basis for ad-platform upload, and are opt-outs, deletions, and do-not-contact records enforced before export?
- How will the list reach the platform - manual CSV or automated warehouse/CDP sync? Who owns the refresh?
- What acquisition outcome is the lookalike meant to drive - target new-customer CPA/CAC, and any LTV or margin expectation for acquired customers?
- What does the account currently average on those same two numbers - acquired-customer CPA, and acquired-customer cohort LTV at 90 days? The pass threshold grades the seed against this baseline, so an unknown baseline means the seed cannot be graded at all: say so and set the first cohort checkpoint as the baseline-building run.
- By what date must the audience be live and spending, and is that date hard? (Seed sources span minutes to a week of coordination, and the enrichment rung runs through procurement - the orderings in steps 3 and 6 cannot be picked without this.)
- Do you want the audience that can launch soonest, or a compounding asset - an automated warehouse sync, enriched identifiers, a reusable cohort definition - that keeps paying across every future audience?
- Effort ceiling: how many hours of data-team time are available, who owns the refresh afterwards, and can you actually get privacy sign-off and a vendor DPA? (A "no" deletes rungs rather than delaying them.)

### Workflow

Every ranking in this skill - steps 3, 6 and 9 here, and the ones in the references - is a default, not a law. Each assumes the common case: no enrichment vendor under contract, no in-house identity graph, no analyst free this week. Who executes it changes the ordering as much as what it is.

Re-rank first against the interview's deadline, durability, and effort-ceiling answers, naming which answer moved which rung:

- A hard near-term date promotes the platform-native engagement seeds.
- A compounding-asset mandate promotes the warehouse sync and the enrichment rung despite their setup.
- No route to privacy sign-off deletes every list-based rung outright.

Then re-rank against what this user actually owns - any of these collapses a rung's effort to near-zero and moves it up:

- A signed enrichment DPA.
- Identity resolution already built in the warehouse.
- An analyst who can write the cohort SQL today.
- A data team that owns the export job anyway.

1. Run the Interview; collect every answer before selecting a single row.
2. Run the privacy and consent gate - a hard stop, before any selection work. If any item below is unconfirmed, stop and say exactly what is missing. This skill is not legal advice: lawful basis varies by jurisdiction, so route open questions to the user's counsel.
   - Documented lawful basis or consent for uploading this list to an ad platform. Under GDPR, the Bavarian DPA position upheld by the Higher Administrative Court Munich (2018, Ref. 5 CS 18.1157) holds that customer-list custom audiences require prior consent, and hashing does not change that: SHA-256 output is pseudonymous, not anonymous, so consent obligations survive it.
   - For EEA use of Google Customer Match, consent signals passed per Consent Mode v2 with both ConsentStatus fields GRANTED (mandatory since March 2024).
   - CCPA/CPRA "sharing" opt-outs and Global Privacy Control signals (honored in twelve US states) propagated before export.
   - No seed built on sensitive categories: health, sexual orientation, religion, race, political affiliation, criminal history.
   - Platform customer-list terms accepted for the specific ad account (value-based audiences need a separate terms acceptance on Meta).
   - Suppression, opt-outs, and deletions enforced once, in the warehouse, before any sync - not per-platform afterwards.
3. Choose the seed source: purchase data first, always. If purchase data is too thin, pick among the eight sourced alternatives - but never down the value ranking alone, because effort and compliance cost both run backwards to it. The axes disagree, so read all four:
   - value: `purchasers > checkout/add-to-cart initiators > high-intent page viewers > lead-form submitters > email clickers > video viewers > page engagers > all visitors`
   - effort: `video viewers == page engagers == all visitors > high-intent page viewers == lead-form submitters > checkout initiators > email clickers > purchasers` - the platform-native engagement audiences build inside the ad account in minutes off a rule the pixel already fires, and skip the customer-list upload and its step-2 consent gate entirely. A purchaser or CRM seed needs a warehouse export, an identity-resolution join, and the full gate. Both ties are real equalities: the first three are one blanket rule over an event already firing, and the next two are that same single rule pointed at a named URL set or a named form - minutes either way, by the same person.
   - compliance cost: `purchasers == checkout initiators == email clickers > lead-form submitters > high-intent page viewers == video viewers == page engagers == all visitors` - anything reaching the platform as a customer list runs the full step-2 gate (lawful basis, Consent Mode v2 in the EEA, opt-out propagation, a separate terms acceptance for value-based audiences), while a platform-native engagement audience never leaves the ad account and triggers none of it. Both ties are exact rather than approximate: the three list-based sources run the identical gate item for item, and the four native ones run none of it - this gate has no partial version to separate them by. The axis can decide the pick on its own: where consent for upload is unconfirmed, every list-based rung is unavailable, not merely expensive.
   - efficiency: `purchasers > high-intent page viewers > lead-form submitters > checkout initiators > email clickers > video viewers (75%+) > page engagers > all visitors`. Purchasers lead **when the customer export already exists**, the common case - a large value gap for one query. Where it doesn't, high-intent page viewers and lead-form submitters are the best ratio on the board: near-zero setup, no upload, no new exposure, still top-half on value. Those two are ordered rather than tied - their setup is the same single rule, so the value axis breaks it - except in B2B lead gen, where the form submission _is_ the conversion and submitters move ahead. Never let effort pull the choice below them: past that point per-row quality falls off faster than effort does. Per-source breakdown and the conditions that move this order: [references/seed-selection.md](references/seed-selection.md).

   What this efficiency order starves is the customer-identity asset itself: the purchaser or CRM seed, and the identity enrichment that makes it usable (fallback rung 1). It tops the value axis and sits last on both effort and compliance cost, so wherever the export does not already exist it loses every round to a pixel rule that ships in minutes - and the account still has no export the next time it asks.

   Promote it against the ratio when:
   - The interview answered "compounding asset" rather than "live soonest".
   - The seed is B2B and the native match rate cannot reach any floor without enrichment.
   - This same account has now lost the round twice.

   Delete it instead - by name, out of the menu - where there is no route to privacy sign-off or no vendor DPA available. A list-based source with no lawful basis is not a slow option, it is not an option, and one left ranked at the bottom reappears as scope after the audience is already live.

   Use email clickers, never openers - Apple Mail Privacy Protection (2021) inflated opens into noise. In B2B, seed from closed-won CRM opportunities, not all-MQL exports. SQL-only beats all-MQL.

4. Select the rows. [references/seed-selection.md](references/seed-selection.md) has the full cohort definitions, window guidance, and exclusion list.
   - Default selection: RFM Champions + Loyal cohorts, or the top 10-25% by predicted LTV or margin - never by cumulative lifetime revenue, which tracks tenure, not worth.
   - Recency window: 30-90 days as the starting point, up to 180 for pixel/CAPI-tracked buyers. Contact data older than 12-18 months materially degrades both match rate and performance.
   - Negative-selection pass (most teams forget this): strip refunders, chargebacks, serial returners, discount-only buyers, employees, and wholesale accounts. Keep existing customers in the seed, but suppress them from the acquisition campaign at delivery level.
5. Compute the effective seed: `effective seed = uploaded rows x expected match rate`. Pull the expected match rate from the platform's documented range in [references/platform-floors.md](references/platform-floors.md), adjusted for the list's identifier density and age - for example:
   - Google Customer Match: 29-62% for most advertisers (per Google's own docs).
   - Meta: 50-80% on good lists.
   - LinkedIn: ~30-40% on work-email contact lists.
   - Reddit: ~2% native CSV.

   Compare the result to the platform's matched-count floor and size the upload at 2-3x the target. If your harness can read the customer export, compute the counts directly. Otherwise, emit the exact filter definitions (source table, filter conditions, recency bounds, value threshold) for the user's data team to run, and wait for the counts before proceeding.

6. If the effective seed cannot clear the floor, walk the fallback ladder - never by loosening selection quality first. Rung numbers are stable IDs used by the spec block and the worked examples; each rung carries its own value, effort, and compliance cost:
   - **Rung 1, enrich identifiers** - identity resolution appending personal emails/phones. Value: the only rung that adds matched people without changing what the model learns, and on a B2B work-email list against a consumer platform the only rung that reaches any floor at all from a ~5% native match. Effort: the outlier the ladder's numbering hides - vendor selection, security review, budget sign-off, then a match test, so a week or more of coordination before a single row moves. Compliance: a new processor in the chain - DPA, counsel sign-off, and a lawful-basis re-check covering enrichment and not just upload; the hardest rung to reverse once contracted.
   - **Rung 2, widen the recency window one notch** (90 to 180, 180 to 365). Value: moderate, paid for in signal freshness. Effort: near-zero - a query edit, minutes, fully reversible. Compliance: none new.
   - **Rung 3, stack an adjacent segment of the same homogeneity** - add Loyal to Champions, or a second product line's buyers if behaviour is genuinely similar. Value: moderate, and homogeneity is what's at risk. Effort: about an hour, plus the judgment call that is the actual work. Compliance: none new.
   - **Rung 4, switch to the next non-purchase seed source down the step-3 ranking.** Value: lowest - the only rung that changes what the model learns. Effort: about an hour if the event source is already instrumented. Compliance: **lower**, not higher - a platform-native source needs no upload and no consent gate.
     Efficiency by default: `rung 1 > rung 2 > rung 3 > rung 4`. Stop at the first rung that clears, and record it in the spec.

     One documented flip: `rung 2 > rung 1`, when no enrichment vendor is contracted **and** there is recency left to widen - an afternoon may end the problem before procurement starts, and rung 1 stays available if it doesn't. The flip does not apply on the standard B2B case, where the cheap rungs are structurally empty: an all-time closed-won list has no recency left, no adjacent segment that isn't lost deals, and a native match too low for rungs 2-4 to reach any floor.

     Rung 1 is also the rung to delete rather than demote. No procurement route, no DPA, or no owner for a vendor budget takes it off the ladder entirely - say it is deleted and run rungs 2-4. A rung nobody can execute, left sitting at the top of an efficiency order, is how the spec ends up assuming it.

     On the standard B2B case that leaves no ladder at all: report that as the finding instead of filling it with a looser seed.
7. If the seed is value-based:
   - Feed margin or predicted LTV.
   - Positive values only.
   - Values must not be all identical.
   - One currency per list.
   - Cap or winsorize whale outliers so a few large accounts don't skew the model.
   - Confirm the value column is mapped at upload. An unmapped value column makes the platform silently build a standard, not value-based, lookalike - if the value-based option doesn't appear at audience-build time, the column didn't map.
8. Specify identifier preparation:
   - Multiple identifiers per row beat email alone.

Excerpt. The rest of the file is on the canonical page and in the source repository.

## Lookalike Audience Seeds FAQ

### Is Lookalike Audience Seeds safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

## Machine access

- [Sitemap](https://skillselion.com/sitemap.xml)
- [llms.txt](https://skillselion.com/llms.txt)
- [llms-full.txt](https://skillselion.com/llms-full.txt)
- [Developer resources](https://skillselion.com/developers)
- [OpenAPI spec](https://skillselion.com/openapi.json)
- [MCP handshake](https://skillselion.com/.well-known/mcp)
- [API catalog](https://skillselion.com/.well-known/api-catalog)
- [AI catalog](https://skillselion.com/.well-known/ai-catalog.json)
- [Pricing](https://skillselion.com/pricing.md)
- [Auth](https://skillselion.com/auth.md)
- [AGENTS.md](https://skillselion.com/AGENTS.md)
- [Contact](https://skillselion.com/contact)
- [Home](https://skillselion.com/)
