Skip to main content

Domain Verification

Prove to Meta that you own your store's domain so you can use Aggregated Event Measurement and the Conversion API — the module injects the verification tag automatically, so you never need to touch your theme files.

Available since v2

Overview​

Meta requires merchants to verify ownership of their domain before enabling Aggregated Event Measurement (AEM). AEM is Meta's measurement framework for tracking ad performance under iOS 14.5+ privacy restrictions — without a verified domain, event priority settings and conversion reporting through AEM are unavailable.

Meta offers three ways to verify a domain:

  1. Upload an HTML file to your web server — requires FTP/SFTP access.
  2. Add a DNS TXT record — requires access to your domain registrar or DNS provider.
  3. Add a meta tag to the page <head> — requires editing your theme, or using this module.

This module automates method 3. You paste the verification code (or the full meta tag) from Meta into the module's configuration, save, and the module adds <meta name="facebook-domain-verification" content="..."> to the <head> of every page on your store. No file uploads, no DNS changes, no theme edits required.

The meta-tag method is the most accessible option for most merchants. It takes about two minutes to set up and works on any PrestaShop theme.

Configuration​

Step 1: Get Your Verification Code from Meta​

  1. Go to Meta Business Settings.
  2. In the left sidebar, navigate to Brand Safety > Domains.
  3. Click Add and enter your store's domain (e.g. yourdomain.com), then click Add.
  4. Select your domain and choose the Meta-tag verification method.
  5. Meta displays a meta tag that looks like: 
    <meta name="facebook-domain-verification" content="abc123def456xyz" />
  6. Copy the entire meta tag (or just the alphanumeric string inside content="...").

Step 2: Enter the Code in the Module​

  1. Go to Modules > Module Manager > Pixel Plus for Facebook > Configure.
  2. Scroll to the Conversion API panel.
  3. Find the Domain verification field.
  4. Paste the meta tag or just the content value into the field.
  5. Click Save.

Step 3: Verify in Meta​

  1. Return to Meta Business Settings > Brand Safety > Domains.
  2. Select your domain and click Verify.
  3. Meta crawls your store to find the tag. Verification usually completes within a few minutes, though it can occasionally take up to a few hours.

Configuration Fields​

FieldValuesDefaultDescription
Domain verificationMeta tag or alphanumeric code—Paste the full <meta name="facebook-domain-verification" ...> tag from Meta, or just the alphanumeric content value. The module extracts the code and injects the tag into every page.

You can paste either the full meta tag or just the bare code — for example, abc123def456xyz. Both work. The module is smart enough to extract the code either way.

How It Works​

Tag Injection​

Once you save a verification code, the module adds the verification tag to every front-office page through the displayHeader hook. The tag appears in the <head> of your HTML, which is exactly where Meta's crawler looks for it. No theme files are modified — the module injects it automatically at runtime.

Smart Paste Handling​

The module handles two input formats so you don't have to worry about which one to paste:

  • Full meta tag — if the pasted value contains the word content, the module parses out the alphanumeric code from inside content="..." automatically.
  • Bare code — if the pasted value has no content keyword, the module treats the entire value as the code directly.

In both cases, only the alphanumeric code ends up stored and injected.

Validation​

The extracted code must contain only letters and numbers. If the module cannot extract a valid alphanumeric code from what you pasted — for example, if the tag is malformed or the content attribute is missing — it shows an error and asks you to re-enter the verification key. Correct the tag in Meta's interface and paste it again.

Multi-Shop​

The verification code is stored per shop. In a multi-shop setup, each shop can have its own domain verification code. Switch to the appropriate shop context in your Back Office before configuring the field, so the code is saved for the correct shop.

Usage Examples​

Example: Standard single-domain store You want to use Aggregated Event Measurement to improve your Meta ad reporting after iOS 14.5 reduced browser-based attribution. You go to Meta Business Settings > Domains, add your domain, choose the meta-tag method, and copy the tag Meta provides. You paste it into the Domain verification field in the module and save. You click Verify in Meta, which checks your store's <head> within minutes and confirms the domain. AEM is now available for your pixel.

Example: Pasting just the code string Meta shows you <meta name="facebook-domain-verification" content="xk9abc123def456" />. You're on a mobile device and it's easier to copy just the content value. You paste xk9abc123def456 into the field. The module stores it and injects the correct full tag automatically — you don't need to reconstruct the HTML.

Example: Multi-shop with two brands on different domains Your PrestaShop installation runs two shops: brand-a.com and brand-b.com. You verify each domain separately in Meta and get two different codes. You switch to Shop A's context in your Back Office, paste Brand A's code, and save. Then you switch to Shop B, paste Brand B's code, and save. Each domain now has its own verification tag injected on its respective storefront.

Important Notes​

  • Domain verification is required by Meta before you can configure Aggregated Event Measurement (AEM) priority events. Without a verified domain, AEM settings in Meta Events Manager are unavailable.
  • The verification tag is injected on every front-office page. Meta's crawler only needs to find it on any publicly accessible page — the home page is the most common target.
  • Meta re-checks domain verification periodically. If your domain is flagged as unverified after some time, check that the module is enabled and the field is still filled in.
  • This setting is per shop in multi-shop setups. Each shop domain must be verified separately.
  • This is one of three verification methods Meta offers. If you prefer to verify via DNS TXT record or file upload (methods that don't require the module), you can do so directly in Meta Business Settings without using this field.

Troubleshooting​

ProblemSolution
Meta still shows the domain as unverified after savingOpen your store's home page, view the page source (right-click > View Page Source), and search for facebook-domain-verification. If the tag isn't there, check that you saved the module configuration and that the Domain verification field is not empty.
Domain verification fails with an error in the moduleThe code you pasted could not be parsed. Make sure you copied the full meta tag from Meta (including the <meta ... /> wrapper) or just the alphanumeric string from inside content="...". Avoid extra spaces or line breaks.
Meta verification check times out or takes a long timeMeta's crawler may take up to a few hours on the first check. Wait and try clicking Verify again. Make sure your store is publicly accessible (not behind a maintenance page or HTTP authentication).
The tag appears in the source but Meta still shows unverifiedConfirm the code in the module exactly matches what Meta issued. If you regenerated the verification code in Meta, paste the new one into the module and save again.
I have multiple shops — which domain should I verify?Verify each shop's domain separately. Switch to each shop context in your Back Office, enter that shop's verification code, and save. Then verify each domain individually in Meta Business Settings.

Frequently Asked Questions​

Q: Do I need to verify my domain if I'm only using the browser pixel? A: Meta recommends domain verification for all advertisers, but it becomes required when you want to use Aggregated Event Measurement — which is the framework Meta uses for reporting under iOS 14.5+ privacy restrictions. If you run Facebook ads and care about conversion attribution, verifying your domain is strongly advised.

Q: Can I paste the full meta tag or do I need to extract just the code? A: Either works. Paste the full <meta name="facebook-domain-verification" content="..." /> tag, or just the alphanumeric string from inside content="...". The module detects which format you used and handles it automatically.

Q: How do I know if the tag is being injected correctly? A: Open your store's home page in a browser, right-click the page, and choose View Page Source (or Inspect). Search the source for facebook-domain-verification. You should see a line like <meta name="facebook-domain-verification" content="your-code-here" /> inside the <head> section.

Q: Does this module method work the same as the DNS or file-upload methods? A: Yes. All three methods achieve the same result — they prove to Meta that you control the domain. The meta-tag method is simply the most convenient for most PrestaShop merchants because it requires no server access or DNS changes.

Q: My verification passed, but Meta is now showing the domain as unverified again. What happened? A: Meta periodically re-crawls verified domains. If it can no longer find the tag, it marks the domain as unverified. Check that the module is enabled, the Domain verification field still contains your code, and your store is publicly accessible. If you recently migrated to a new theme or changed your hosting, clear your PrestaShop cache and verify the tag appears in the page source again.

Q: Can the same domain verification code be used across all shops in a multi-shop setup? A: Only if all shops share the same domain. If each shop has a different domain, each needs its own verification code from Meta. If multiple shops share one domain (for example, different subfolders of the same domain), you may be able to use the same code — but verify this with Meta's domain verification documentation for your specific setup.

Q: Is there any SEO or performance impact from adding this tag? A: No. The meta tag is a single short line in the <head> and has no impact on your search engine rankings or page load speed. Meta's crawler reads it passively.

Do I need to verify my domain if I'm only using the browser pixel?

Meta recommends domain verification for all advertisers, but it becomes required when you want to use Aggregated Event Measurement — which is the framework Meta uses for reporting under iOS 14.5+ privacy restrictions. If you run Facebook ads and care about conversion attribution, verifying your domain is strongly advised.

Can I paste the full meta tag or do I need to extract just the code?

Either works. Paste the full `<meta name="facebook-domain-verification" content="..." />` tag, or just the alphanumeric string from inside `content="..."`. The module detects which format you used and handles it automatically.

How do I know if the tag is being injected correctly?

Open your store's home page in a browser, right-click the page, and choose **View Page Source** (or **Inspect**). Search the source for `facebook-domain-verification`. You should see a line like `<meta name="facebook-domain-verification" content="your-code-here" />` inside the `<head>` section.

Does this module method work the same as the DNS or file-upload methods?

Yes. All three methods achieve the same result — they prove to Meta that you control the domain. The meta-tag method is simply the most convenient for most PrestaShop merchants because it requires no server access or DNS changes.

My verification passed, but Meta is now showing the domain as unverified again. What happened?

Meta periodically re-crawls verified domains. If it can no longer find the tag, it marks the domain as unverified. Check that the module is enabled, the **Domain verification** field still contains your code, and your store is publicly accessible. If you recently migrated to a new theme or changed your hosting, clear your PrestaShop cache and verify the tag appears in the page source again.

Can the same domain verification code be used across all shops in a multi-shop setup?

Only if all shops share the same domain. If each shop has a different domain, each needs its own verification code from Meta. If multiple shops share one domain (for example, different subfolders of the same domain), you may be able to use the same code — but verify this with Meta's domain verification documentation for your specific setup.

Is there any SEO or performance impact from adding this tag?

No. The meta tag is a single short line in the `<head>` and has no impact on your search engine rankings or page load speed. Meta's crawler reads it passively.

  • Conversion API Setup — Domain verification is configured in the same Conversion API panel; a verified domain is required for Aggregated Event Measurement to work alongside CAPI.
  • Pixel Setup — Your Pixel ID must be configured before domain verification has any effect on AEM event priority settings in Meta.