Meta Ads Lookalikes: A Source-Quality Decision
What makes a good lookalike audience source?
Source fitness gates on unique size, recency, valid event quality, behavioural homogeneity and consent status. A large source that mixes discount buyers with full-price repeat customers is heterogeneous, and the resulting audience optimises toward whichever group dominates rather than toward your best customers.
For the surrounding account decisions, compare Meta Catalog Data Quality: An Identity and Availability Diagnostic and use Meta Ads Campaign Structure: A Decision Framework as the next diagnostic.
In short
This guide owns one decision artifact: the filled, auditable structure below. Reader-supplied thresholds stay explicit; missing evidence stays missing.
Lookalike source-fitness checklist
| Gate | Reader threshold | Fit | Not fit |
|---|---|---|---|
| Source size | Minimum eligible unique records required for the planned build, copied from current account requirements | Reconciled uniques meet threshold | Duplicates/invalids reduce source below threshold |
| Recency | Maximum age chosen from the business’s current offer and customer cycle | Required share falls inside cutoff | Source is dominated by records older than cutoff |
| Event quality | Minimum valid join/parameter coverage | Valid source events ÷ eligible source events meets threshold | Event meaning, value, identity, or dedup remains unresolved |
| Homogeneity | Maximum tolerated mix across declared value/intent states | Source contains the one stated seed outcome or approved stratification | Purchasers, leads, refunds, tests, and low-intent events are mixed without labels |
| Consent | Required permitted-purpose coverage | Permitted eligible IDs ÷ eligible IDs equals the reader’s required threshold | Missing, expired, withdrawn, or incompatible purpose records remain |
All five gates must say fit. Platform creation or delivery does not validate source quality, and source fitness does not promise performance.
Interpretation boundary
Use the lookalike source-fitness gates only for its stated decision. Require reader thresholds for unique source size, recency, valid event quality, outcome homogeneity, and permitted-purpose coverage. Platform acceptance or delivery cannot turn a mixed, stale, duplicated, or unconsented seed into a fit source. Reader-supplied thresholds remain inputs, not universal standards.
Documented thresholds
Meta publishes the figures below; they are reproduced here with the article they come from. Retrieved 2026-09-22 — Meta revises this documentation without notice, so verify anything load-bearing against the current version before you act on it.
- Lookalike source size. Meta requires at least 100 people and generally recommends 1,000–5,000. The hard floor is 10% of the bottom of that range and 2% of the top, so an audience can be technically valid and practically useless.
- How small is too small. Meta lists audience size first among the six documented causes of a learning limited ad set, and the operative test is whether the audience can generate about 50 optimisation events a week — at 30 a week you are at 60% of the threshold.
- Overlap is a documented cause. Meta lists high auction overlap among the six conditions that produce a learning limited ad set. Three ad sets each capped at 2 impressions a week can still deliver 6 to someone in all three audiences — a 200% overshoot.
Source: Meta Business Help Centre — https://www.facebook.com/business/help/465262276878947, https://www.facebook.com/business/help/1474662202748341, https://www.facebook.com/business/help/269269737396981.
Can software help?
Bach.ai audits your connected Meta account, estimates the revenue impact of what it finds, and proposes specific fixes. It applies a change only after you approve it. Think of it as an automated audit layer that surfaces issues and proposed fixes for your review — not a replacement for your team’s judgment, and creative production is not its core job, though the Pro and Agency plans can generate a limited number of variants.
FAQ
What makes a source audience fit for a Meta lookalike?
Require reader thresholds for unique source size, recency, valid event quality, outcome homogeneity, and permitted-purpose coverage.
Does Meta accepting a seed mean the source is high quality?
Platform acceptance or delivery cannot turn a mixed, stale, duplicated, or unconsented seed into a fit source.
What decision can lookalike source-fitness gates support?
It supports the bounded operating choice encoded by the lookalike source-fitness gates. It cannot replace missing source records or turn platform credit and observed association into incremental impact.
Method and sources
“Source fitness gates on unique size, recency, valid event quality, behavioural homogeneity and consent status.”
Source: Where this guide describes platform behaviour, it follows Meta’s published advertising and Marketing API documentation, which changes without notice — verify anything load-bearing against the current version before you act on it. Every threshold the guide asks you to supply is first-party, drawn from your own account exports and commerce ledger, because no external benchmark can stand in for your own margin structure.