Facebook "Domain Verification Failed"

Quick Answer

Use DNS TXT record verification — it's the most reliable method. Add the TXT record Meta provides to your domain's DNS, wait 24 hours for propagation, and click verify. The other two methods (meta tag and file upload) often fail for caching or path reasons.

Step-by-step fix

Open Business Settings → Brand Safety → Domains.
Click Add and enter your root domain (without www, without https://).
Choose DNS TXT Record as the verification method.
Copy the TXT record value Meta provides (it starts with facebook-domain-verification=).
Open your domain registrar's DNS panel (Cloudflare, GoDaddy, Namecheap, etc.).
Add a new TXT record:

- Type: TXT - Host/Name: @ (or leave blank for root) - Value: paste the value Meta gave you - TTL: default (1 hour or 3600)

Save the DNS record.
Wait 5 minutes for fast registrars (Cloudflare) or up to 24 hours for slow ones.
Click Verify in Business Settings. The domain should now show as verified.
If verify fails, try the dig command to check propagation: dig TXT yourdomain.com should show your facebook-domain-verification value.

Why it happens

Domain verification proves to Meta that you control the domain you're advertising. It fails for these reasons:

DNS hasn't propagated yet. Some registrars take up to 48 hours.
TXT record added to wrong host — "www" instead of "@" or root.
Multiple TXT records conflict — if you have other facebook-domain-verification records (from old setups), they confuse Meta.
Meta tag method failed because of caching — Meta's crawler hits a cached version of your homepage that doesn't have the meta tag.
Meta tag wasn't in the <head> — it's in the body or a footer where Meta won't read it.
File upload method blocked — your server rewrites the URL, returns 404 for unknown files, or has security middleware blocking the verification file.
Redirects — your domain redirects to www or https before Meta can read the verification.
Wrong domain submitted — verifying example.com when your ads run on shop.example.com.

Domain verification is required for:

Aggregated Event Measurement (AEM) — without verification, you can't configure your 8 prioritised events.

Conversion event prioritisation.

Event configuration changes for iOS attribution.

Sharing ownership of a domain across multiple Business Managers.

How to prevent it

Always verify the root domain, not subdomains. Verifying example.com automatically covers shop.example.com.
Use DNS TXT verification as the default — it's robust and survives caching.
Add the record to the apex domain (host: @ or blank), not www.
Wait 24 hours after adding before clicking verify. DNS propagation is unpredictable.
Don't delete old facebook-domain-verification records unless you're sure they're not used.
Verify the domain in only one Business Manager at a time. Sharing requires explicit ownership transfer.
Document which Business Manager owns each domain so your team doesn't try to verify the same domain twice.

When to escalate to Meta support

Escalate if:

DNS propagation is confirmed (dig shows the record), but Meta still says verification failed.
The domain shows as verified in one Business Manager but unavailable in another despite ownership transfer.
You see ghost verifications (domain shows as verified but features still locked).

Use Pro Team Chat with the domain name, the Business Manager ID, and a screenshot of your DNS panel showing the TXT record.

Pix-Vu mention

Domain verification is foundational — without it, you can't run modern Meta campaigns properly. While you wait for DNS to propagate, refresh your creative library. Pix-Vu helps you upgrade ad imagery so you launch with stronger creative once verification is complete.