How domain verification protects measurement

Why verification gates everything#

Unverified domains cannot configure AEM, cannot prioritise the 8 conversion slots, and risk event conflicts where multiple businesses claim overlapping measurement on shared or agency-touched domains. Verification is the deed to the measurement house: everything structural, from ranking to reporting rights, hangs off it. Start at the Meta Ads hub for the family view.

Verify before spending, not after breakage: retroactive verification cannot recover misattributed history, and conflict resolution mid-flight pauses optimisation while ownership is settled. It costs minutes and protects months. Meta own domain verification guide lists the current routes.

Three routes to verified#

DNS TXT records suit teams with registrar access and survive site rebuilds untouched; HTML file upload suits developers with server access but breaks when themes or migrations drop the file; meta-tag insertion suits tag-manager workflows but needs care that the tag persists on every template. All three prove the same ownership, so choose the route your team will keep alive rather than the fastest click.

Confirm verification in Business Manager before touching events: a green status there, not a hopeful assumption, is the gate. Document which route was used and where, because year-two debugging starts from that note. Developer reference for the tag route is at verification docs.

Claiming plus assigning#

Verification proves ownership; claiming assigns control. Claim the domain into the correct Business Manager, assign the Pixel dataset and the conversion events that belong to it, and confirm one owner where agencies and clients both touch the account. Shared or unclaimed domains breed conflicting event sets that corrupt optimisation quietly.

Map each domain to its dataset explicitly: one domain, one dataset, one ranked event set. Multi-brand portfolios should verify every trading domain separately rather than inheriting assumptions from the primary. Event vocabulary is set in standard events, and the Pixel side in Pixel setup.

Conflicts and how to clear them#

Conflicts surface as greyed-out events, uneditable AEM slots, or diagnostics naming another business: signs that an agency, a former partner or a sibling brand holds a competing claim. Resolution runs through Business Manager ownership transfers and claim releases, never through duplicate datasets, which multiply the corruption instead of settling it.

Audit claims quarterly: list every domain, its verifier, its claimant and its assigned events, and release stale agency claims the moment engagements end. Offboarding checklists should name domain claims beside ad account access. AEM ranking can only be trusted once conflicts clear.

The AEM handoff#

Verified and claimed, the domain graduates to AEM configuration: rank the 8 slots by revenue, attach value sets, and match campaign optimisation events to ranked slots. Verification without ranking is a deed to an empty house; ranking without verification is impossible. Do both in one session and allow the propagation window before judging.

Freeze domain and ranking changes through peak trading, since propagation pauses plus volatility punish December reconfigurations. Log the ranking beside the verification record with dates. Attribution windows then decide how counted events credit.

Keeping verification green#

Verification lapses when DNS records are tidied away, files are lost in migrations, or tags are dropped in theme rebuilds; each lapse silently downgrades measurement until someone notices the red status. Monitor status monthly and after every site migration, registrar change or theme rebuild, and keep the proof redundant where possible with two routes live.

Pair the routine with broader signal reviews: CAPI cover, clean dedup, and our team for a pre-peak measurement audit.

Frequently asked questions#