Meta Ads Measurement: A Privacy-Constrained Signal Plan

For the surrounding account decisions, compare Meta Ads Ranking Diagnostics: How to Read the Signal and use After the Cookie: A Forward Measurement Plan for DTC 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.

Missingness worksheet

Keep modeled rows separate from directly observed rows. Populate counts from the named extracts; do not insert a benchmark loss percentage.

Class	Count definition	Source	Consent state	Numerator	Denominator	Exclusions
Observed	Valid event records directly received and joined to an eligible ledger outcome	Raw browser/server logs plus commerce ledger	Consent permitted for the declared purpose	Observed joined eligible outcomes	Eligible consented ledger outcomes	Test traffic, cancelled orders, invalid payloads
Modeled	Outcomes explicitly labelled modeled in the platform export	Frozen platform report	Platform-reported aggregate; do not relabel as observed consent	Modeled attributed outcomes	All attributed outcomes in that export	Observed rows and unlabeled estimates
Missing	Eligible consented ledger outcomes with no valid observed event by cutoff	Commerce ledger minus event join	Consented and eligible only	Unjoined eligible outcomes at cutoff	Eligible consented ledger outcomes	Non-consented outcomes and late rows still inside SLA
Late	Valid observed events received after the declared receipt SLA	Event transport log	Consent permitted at occurrence	Eligible events received after SLA	Eligible received events	Retries of an already accepted event
Rejected	Events failed by schema, consent, or validation rule	Collector rejection log	Record the precise state and failed rule	Rejected eligible submissions	Eligible submissions	Synthetic tests tracked separately
Unmatched	Valid received events that cannot join the ledger on the declared key	Event and ledger join output	Consent permitted	Valid unjoined events	Valid received events	Events that do not represent commerce outcomes

Observed coverage = (observed joined eligible outcomes) ÷ (eligible consented ledger outcomes). Modeled share = (outcomes explicitly labelled modeled) ÷ (all platform-attributed outcomes in the same export). Sources/windows are the worksheet extracts and one declared receipt cutoff. Neither formula measures incrementality.

Interpretation boundary

Use the observed/modelled missingness worksheet only for its stated decision. Count directly joined observed outcomes separately from rows explicitly labelled modeled, then classify missing, late, rejected, and unmatched records. Never infer a loss percentage when consent eligibility or the ledger denominator is unavailable. 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

How should observed, modeled, missing, and late events be separated?

Count directly joined observed outcomes separately from rows explicitly labelled modeled, then classify missing, late, rejected, and unmatched records.

When is an iOS signal-loss percentage unsupported?

Never infer a loss percentage when consent eligibility or the ledger denominator is unavailable.

What can a missingness worksheet show without proving incremental impact?

It supports the bounded operating choice encoded by the observed/modelled missingness worksheet. It cannot replace missing source records or turn platform credit and observed association into incremental impact.