How domain verification works
Meta will not let anybody control how conversions on a website are measured until it knows who owns that website. Verification is the proof. Inside Business settings you add the domain and then demonstrate control of it in one of three ways: adding a TXT record to the domain’s DNS, uploading a file Meta gives you to the web root, or placing a short meta tag in the site’s head.
Whichever route you take, the check is ownership of the domain itself rather than of any single page, so verifying the root covers what sits beneath it. The proof also has to stay in place — deleting the record or the tag during a later redesign quietly undoes the verification, and nothing announces it.
What verification unlocks is the right to decide which conversion events on that domain matter most. Meta measures a limited, ranked list of events per domain, and only the verified owner can set that order. Events left outside the list are not available to optimise towards.
Why domain verification matters
Two things depend on it and both tend to be discovered late. The first is event priority. If nobody sets the order, it gets decided for you, and a low-value action such as a page view can outrank the purchase you actually care about, so your most important conversion goes missing for part of your audience.
The second is control. A domain is claimed by one business account, and that account is very often an agency’s. When the relationship ends, a business can find that the ability to configure measurement for its own website belongs to somebody else. Verifying in your own Business Manager, then adding the agency as a partner, avoids an awkward conversation later.
Where domain verification goes wrong
Verifying at the wrong level is the usual technical error — attempting a single page or the wrong host name instead of the domain you genuinely own. It appears to succeed and then fails to cover the pages your ads point at.
The organisational error is worse: verified in a hurry, in whichever account happened to be open, with no note of where it was done. Add a DNS record dropped during a hosting migration and a business can advertise for months with its events quietly deprioritised. And verification on its own achieves nothing, because the event list still has to be configured afterwards. That is the step most often skipped.
How to act on it
Verify the root domain in the Business Manager the business itself owns, before any serious spend begins. Prefer the DNS method where you have access to the domain’s records, because it survives a rebuild; the meta tag is quicker but leaves with the next theme change. Ask your host or developer if the DNS side is unfamiliar, since it is a small job for anyone who does it regularly.
Then finish the work. Rank the events so the outcome that makes money sits at the top and the browsing steps sit below it, and revisit that order whenever a new conversion is added. Re-check verification after a domain move, a hosting change or a site migration. These settings belong beside the rest of your Meta pixel and Conversions API setup, and they are far easier to review together than one at a time.