Meta Compliance: Setup Popsixle Domain Masking

Connect Popsixle to Meta the right way so every checkout event looks like it came from your clean landing-page domain.

 

Note: this content is informational only and not legal advice.

Why Domain Masking + Session Stitching Matter

Without masking, Meta sees checkout events from your main, potentially non-compliant store and may flag or re-categorise your pixel. Popsixle rewrites those events so Meta thinks every action happened on the clean landing-page domain, while session-stitching keeps the Browser and Server copies of each event identical so they deduplicate perfectly.

blocked-site schematic


Prerequisites (you should already have)

  • One-page compliant landing site live on clean-domain.com (Link)

  • Domain verified in Business Manager › Brand Safety

  • Brand-new Meta Pixel firing PageView browser events

  • Admin access to your full Shopify store (the non-compliant site)


Install & Configure Popsixle

Step Action Why
3a Install the Popsixle app in your Shopify store (Apps › Add App › search “Popsixle”). Popsixle runs from the store that handles checkout.
  ⚠︎ Do NOT connect Popsixle to Meta yet—skip the wizard’s data-link step for now. Prevents early data leakage.
3b In Popsixle Shop Settings › Domains, add clean-domain.com as an extra domain your account can accept data from Tells Popsixle which domain to mask to.
3c Still in Shop Settings, click Copy Code Snippet. Snippet fires both Browser & Server events.
3d On clean-domain.com, remove the any Meta pixel code and paste the Popsixle snippet into the <head>. Prevents duplicate Browser events.
3e In Popsixle Health Data Settings › Domain Override, toggle Domain Masking = On and Session Stitching = OnSave.
enter clean-domain.com as your domain for masking.
Masks every server event to clean-domain.com.
 

Enable & Verify Server-Side Events (Masked)

Step Action
4a In Popsixle › Data Connections, choose Meta/Facebook → enter your Pixel ID, CAPI Access Token, and Test Event Code.
4b Toggle Send Browser Events and Send Server EventsSave & Restart.
4c Turn OFF Shopify’s built-in data sharing so only Popsixle sends events: Shopify › Sales Channels › Facebook & Instagram › Settings › Data Sharing › Data sharing off. info.popsixle.com
4d Visit clean-domain.com → click through to your full Shopify store → complete a test checkout (use Shopify test payment).
4e Wait ≈ 20 min, then in Events Manager check Test Events and Overview:
 
In Meta Events Manager:
  • Purchase (Server) appears.

  • Domains shows clean-domain.com/… (not your main store). |

  • In Events Manager › Settings › Data Categories, confirm no Restricted/Health/Financial flags.

Troubleshoot: If you see duplicate warnings, make sure the old pixel script is gone from the landing page and Session Stitching is on.

compliant site schematic


Health Checklist

☐ Popsixle app installed in Shopify (non-compliant store)
☐ Domain Masking + Session Stitching toggled ON
☐ Popsixle snippet live on clean-domain (old pixel removed)
☐ Shopify → Facebook data sharing = OFF
☐ Purchase (Server) shows event_source_url = clean-domain.com
☐ No flags under Events Manager › Settings › Data Categories

Build Landing-Page-Only Ad Sets

  1. In Ads Manager create a new Campaign → make sure you use your new, clean pixel in ad set event optimization.

  2. Ad Set › Website: paste the Landing Page URL (not the store).

  3. Exclude existing remarketing audiences built from the old store pixel (they may carry flags).

  4. Publish.


6 Do & Don’t for Long-Term Stability

Do Don’t
✅ Keep Domain Masking toggled on after every Popsixle update. ❌ Turn it off “just to test”. Even one unmasked purchase can trigger review.
✅ Re-scan new creatives before launch. ❌ Drive any ad traffic directly to the main store.
✅ Check Events Manager › Diagnostics weekly. ❌ Ignore “Event missing deduplication” warnings.


This article is part of a series:

Need Help?