Meta Ads Lookalikes: A Source-Quality Decision

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.

Can software help?

Bach.ai audits your connected Meta account against 100+ checks, ranks what it finds by estimated impact, and proposes specific fixes. It stays read-only until you approve a change, then executes the approved change on Meta; connected Google Ads data is used for intelligence only. 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 it does not generate your creative.

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.