Enter the dashboard password. Opened from Shopify admin (Apps › BP Meta Pixel) you are signed in automatically and this screen is skipped.
●
Meta Pixel Sanitizer
BariatricPal Store · dataset 1518864288430229
Signed-in view could not load data. If you opened this outside Shopify admin, use the app under Apps › BP Meta Pixel.
Loading status…
Overview
Health
Tools
Activity
Data safety (blocked-parameter guard)
Protected
Meta blocks health-adjacent params (content_name, content_category, product titles, search terms). Our pixel and server both strip these before anything reaches Meta, and this guard alerts the moment any code path tries to send one, days before Meta would email you. Meta exposes no API for its block list, so watching our own outgoing events is the earliest possible warning.
-
Purchases sent
via CAPI
-
Funnel events sent
via CAPI
-
Delivery queue
failures waiting
-
Skipped safely
invalid or ineligible
Reconciliation
idle
Catches Purchases that Meta never received (webhook miss or downtime) and resends them. Dedup-safe, so a resend is harmless if it already arrived. Runs hourly.
Last run-
Recovered (total)-
Delivery health
Test mode
Live pulse of the server-side (CAPI) pipeline. Green dot = flowing normally; the time is how long since that system last spoke to us.
Shopify orders coming in-
ReCharge subscriptions-
Meta accepting our events-
Events delivered to Meta (running totals)
Purchases-
Product views-
Adds to cart-
Checkouts started-
Payment info entered-
Problems-
Connect the Meta access token to see events Meta received.
Delivery queue
clear
Events appear here only after delivery fails. Retry sends the same event ID for deduplication; dismiss archives events that are invalid or older than Meta's seven-day window.
Event
Event time
Meta response
Loading…
Test mode
Route events to Events Manager › Test events instead of production while you verify. With a code set, real orders that fire the webhook land in the test bucket, not production.
Meta CAPI access token
Not set
Paste the token from Events Manager › Conversions API. Stored encrypted in the worker. Nothing is sent to Meta until you activate the pixel or the webhook fires.
Meta reporting token
Not set
Read-only credential for Meta-received event totals. This is separate from the working CAPI delivery token and requires ads_read plus business_management.
Alert email
Worker alerts (delivery down, Meta errors, config drift, low coverage) email the PPC inbox via SparkPost. Repeat alerts are suppressed for 6h; warnings ride the daily digest. Use the test to verify the pipe end to end. Note these emails come from the relay itself, so they cannot report the relay being down; that is what the external uptime monitor is for.
Browser pixel
installed
The active Shopify Custom Pixel loads this code remotely. Pixel ID and sanitizer terms update from the relay at runtime, so Worker deployments and term changes require no Shopify code edit.
The pixel fires on the live storefront and real checkout only. It quietly ignores these non-production surfaces so preview/staging visits never pollute the dataset or audiences. This is a blocklist (not an allowlist) on purpose: an allowlist of only store.bariatricpal.com would break ReCharge/Shopify checkout on other hosts. Read-only; the rules live in the pixel (isNonProdContext).
Skipped surface
Why
*.myshopify.com
Dev / preview store domain (bariatricpal.myshopify.com)
*.shopifypreview.com
Theme “Preview” share links
bariatricpal.com · www.bariatricpal.com
Forum / main site apex, not the store
/password
Password / coming-soon page
?preview_theme_id · _fd · _ab · pb
Theme editor / unpublished-theme preview
Everything else fires: store.bariatricpal.com and all checkout hosts (incl. checkout.rechargeapps.com). To manage the domains Meta itself accepts, use Events Manager › Settings › Traffic Permissions (Meta exposes no API for that, so it can’t live here).
Event previewer
See the exact server-side (CAPI) JSON the worker would send for each event, with product values scrubbed and customer data hashed. This is what leaves the worker for Meta.
Scrub tester
Paste any product name, category, or search query to see exactly what the pixel would send to Meta after scrubbing. Uses the same term list as the live pixel below.
Sent to Meta as-
Sanitizer terms
The health, diet, and condition words stripped from content_name, content_category, and search_string before anything reaches Meta. Edit and Save here - it applies to both the server (CAPI) and the browser custom pixel automatically. No code editing, no redeploy.
Meta dataset / pixel ID: -
Catalog leak scan
Runs every product title and category through the live Sanitizer terms and reports anything a health/condition/diet word net still finds. Run it after editing terms or adding products (takes ~30s). Note: it can only flag words in its candidate net, so it lowers risk but does not prove the term list is complete - Meta's Diagnostics after go-live is the real test.
Blocked parameter monitor
checking
Loading the latest retained Meta diagnostic snapshot.