Use Facebook events cannot verify domain

In this guide

Why it matters The three ways to verify Steps Problems and fixes With server-side tagging A worked example Terms you will see Before you ask Meta support Frequently asked questions

Check these first

Meta wants proof that you own the domain your events come from. Without it, some features, such as event configuration, are limited.
Verify the root domain (yourstore.com) in Business Settings, Brand Safety, Domains with a DNS TXT record, a meta tag or an HTML file.
A tagging subdomain does not replace verification of the main domain. Verify the domain your visitors see.

Meta uses domain verification to stop people from sending events or setting up ads for a website that is not theirs. If you see that a domain cannot be verified, or that events are limited because the domain is not verified, the fix is a one-time change in Business Settings and your site. This page covers the steps and the traps, including how it interacts with a server-side tagging subdomain.

Why it matters

Event configuration and some conversion settings are tied to a verified domain.
Link and event attribution settings depend on knowing who owns the website.
Verification protects you if a lookalike domain tries to use your pixel.

Live view

Watch events arrive, live

A sample feed. In Open Tracked you see the same stream for your own store.

The three ways to verify

Method	What you do	Good for
DNS TXT record	Add a TXT record that Meta gives you at your DNS provider	Most sites. Works for the whole domain and does not depend on the page.
Meta tag	Add a `facebook-domain-verification` meta tag in the `<head>` of your home page	Sites where you edit the theme but not DNS.
HTML file	Upload a file Meta gives you to your site's root	Static or custom sites.

Steps

Open Business Settings

Brand Safety, then Domains.

Add your root domain

For example yourstore.com, without https:// or www.

Choose a method

DNS TXT is the most reliable.

Add the record or tag

At your DNS provider, or in your site's head.

Press Verify

DNS changes can take minutes to hours.

Trusted

Brands that grow on cleaner data

Stores and agencies use Open Tracked to see which ads earn the sale.

Problems and fixes

SymptomVerification fails with the meta tag

Likely causeThe tag is not on the home page, or a cache serves the old page.

FixAdd it to the <head> of the home page, clear the cache and verify again.

SymptomDNS record not found

Likely causeThe record was added at the wrong place or has not propagated.

FixAdd it at the DNS provider that is authoritative for the domain. Wait and retry.

SymptomVerified, but events still say unverified

Likely causeEvents come from a domain other than the one you verified.

FixCheck the event_source_url of your events. It should be the visitor-facing domain, not the tagging subdomain.

SymptomAnother business already claimed the domain

Likely causeA past agency or account holds it.

FixAsk them to remove it, or contact Meta support to resolve the claim.

SymptomMany subdomains

Likely causeYou verified a subdomain, not the root.

FixVerify the root domain. It covers its subdomains.

With server-side tagging

When events go through a tagging subdomain, the browser talks to track.yourstore.com but the website is yourstore.com. Meta still wants the website domain verified, because that is the domain people see and the one set in event_source_url. In Open Tracked, send event_source_url as the page URL from the data layer, and verify the root domain in Meta. The tagging subdomain needs no separate verification for this purpose.

0 of 5 done

The root domain is added in Business SettingsA verification method is in place and Meta shows Verifiedevent_source_url is the visitor-facing pageOnly one Business account owns the domainThe pixel and the dataset belong to the same account

Domain verification is separate from consent and from the Conversions API. Fixing it does not change your event counts, but it unlocks settings.

A worked example

A store verifies track.yourstore.com, the tagging subdomain, and Meta still says the website is unverified. The website itself is yourstore.com. Adding the root domain in Business Settings and verifying it with a DNS TXT record fixes it within the hour. The tagging subdomain needed nothing.

Terms you will see

Root domain: Your main website domain, such as yourstore.com.
TXT record: A DNS record that holds text, used for proof of ownership.
Business Settings: The admin area of your Meta business account.
Event source URL: The page address sent with a server event.
Brand Safety: The section of Business Settings where domains are listed.

Before you ask Meta support

0 of 5 done

The domain is typed without https and without wwwThe record or tag is on the live site, not on a staging copyA cache or CDN is not showing an old pageNo other business account has claimed the domainYou waited long enough for DNS to propagate

Set up in minutes

Connected in minutes

Add your domain, install the pixel, connect your ad platforms and watch the first events land.

Frequently asked questions

How do I verify my domain in Meta?

Go to Business Settings, Brand Safety, Domains, add your root domain and use a DNS TXT record, a meta tag or an HTML file.

Should I verify the tagging subdomain?

No separate verification is needed for that. Verify the main website domain, and send the page URL as the event source.

How long does verification take?

A meta tag or file is usually immediate. DNS can take minutes to hours.

Why does Meta say another account owns my domain?

A previous account or agency verified it. Ask them to release it or contact Meta support.

Does verification affect tracking accuracy?

It does not change counts, but it is needed for some event configuration features.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Troubleshooting →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...