Skip to main content
OpenAIAnthropicGooglePerplexityMetaMicrosoft
Meta Domain Verification native
Meta Domain VerificationMeta Domain Verification·Site verification

meta domain verification on every wordpress site.

paste your `facebook-domain-verification` token, save, and the meta tag renders in `<head>` for every visitor — no consent gate. required for Meta Ads attribution under iOS 14.5+ and Aggregated Event Measurement.

free trial. no credit card. all 30 integrations included on every plan.

includedYovale WordPress Hosting — Meta Domain Verification
yovale.com/en/integrations/meta-domain-verification
Meta Domain Verification · no consent gate

Meta verification layers inside every wordpress site.

Apple's iOS 14.5 App Tracking Transparency forced Meta to introduce Aggregated Event Measurement (AEM). AEM requires that the domain be verified in Meta Business Manager — without verification, conversion attribution falls back to severely limited modeling.

01
save-time validation
regex `^[a-z0-9]{20,40}$` enforced in dashboard
02
render-time mirror
same regex re-checked in PHP
03
no consent gate
fires for every visitor (necessary)
04
head meta tag
emitted in `wp_head` priority 1
01
Meta verification meta tag injector
02
iOS 14.5+ attribution requirement covered
03
no consent gate (necessary)
04
no plugin needed
status panel
iOS 14.5+
AEM attribution requirement
no cookies
no consent gate needed
<1 min
verifies in minutes
iOS 14.5+ AEM

verified domains attribute 3× more iOS conversions.

since iOS 14.5 App Tracking Transparency, Meta Ads attribution depends on Aggregated Event Measurement. AEM only reports conversions from verified domains. unverified sites lose attribution silently.

32-char hex token validated at save and at render
no consent gate — verification meta tag, not a tracker
survives SEO-plugin swaps; lives at the platform layer
unverified domain
32%attribution rate
conv. modeled, not measured−68%
verified · AEM enabled
94%attribution rate
conv. measured directly+62pp
iOS 14.5 ATT prompt

users who decline lose cookie-level tracking — only AEM remains

AEM event priority

8 events per domain, ranked — verification unlocks the slots

DTC routinely sees

30–50% MORE attributed iOS conversions on verified vs not

the problem

paste your token. AEM unlocks.

Yovale validates the token at save. the meta tag renders in `<head>` for every visitor — no consent gate because it's a verification meta tag, not a tracker.

  • 1
    Open Tracking → Site Verification

    Find Meta Domain Verification in the dashboard's verification panel.

  • 2
    Paste your verification token

    From Meta Business Manager → Brand Safety → Domains → Add domain → Meta tag method. Copy the `content=` value (32 lowercase hex characters).

  • 3
    Toggle on, save, verify in Meta

    Click Verify Domain in Meta Business Manager. Verification completes within minutes — AEM attribution starts working immediately.

view-source: https://your-site.com
<head>
<meta charset="UTF-8">
<meta name="facebook-domain-verification" content="b3a48e1c2d9f4506ea7c8531ebd9472f" />
<title>...</title>
</head>
Meta Business Manager
verified
AEM events
8 / 8 prioritized
why bother

verification = post-iOS Meta Ads — working.

iOS 14.5+ AEM

unlocks Aggregated Event Measurement — the only attribution path Meta has post-ATT.

Token validated

32-char hex enforced at save and at render. typos can't ship.

DTC conversion lift

verified domains routinely see 30–50% more attributed iOS conversions.

No consent gate

verification meta tag, not a tracker — fires for every visitor.

faq

questions before you switch hosts for Meta Verify.

Why does Meta Domain Verification matter so much for iOS attribution?

Apple's iOS 14.5 App Tracking Transparency forced Meta to introduce Aggregated Event Measurement (AEM). AEM only works for verified domains. Without verification, iOS Meta Ads conversion attribution falls back to limited modeling — DTC brands routinely see 30–50% attribution loss.

Does Meta verification need a consent banner?

No. Verification meta tags don't drop cookies and aren't trackers. No consent gate needed.

Do I need Meta Domain Verification AND Meta Pixel?

Yes — they're separate. Verification claims your domain (unlocks AEM + iOS attribution). The Pixel is for actual conversion tracking. Both are needed for Meta Ads to work properly post-iOS 14.5.

Will the page cache strip the verification meta tag?

No. The meta tag is part of the cached HTML. There's no consent state involved.

How quickly does Meta verify after save?

Verification typically completes within a few minutes. AEM attribution starts working immediately for new conversions.

ready when you are

Meta domain verified for iOS 14.5+ attribution by day one.

free trial. no credit card. paste a verification token, save, and AEM attribution unlocks.