What the Flag Is
Meta categorizes certain stores — those selling supplements, wellness products, or health-related goods — under a restricted “Health & Wellness” category. Once your store is flagged, Meta applies stricter privacy and content policies that limit what data your pixel can collect and use for optimization. There is no notification from Meta when the flag is applied. Most brands discover it when they see unexplained performance declines or when events stop being accepted for optimization. The flag is attached to your domain, not your pixel. Creating a new pixel and sending data from the same flagged domain results in the new pixel also getting flagged. This is why simply swapping pixels doesn’t solve the problem — and why domain aliasing is a core part of Upstack’s approach.What the Flag Restricts
There is no uniform severity — Meta doesn’t expose “levels” of the flag, and the impact ranges from no noticeable change, to a sharp drop right after the flag, to a slow decline over weeks or months. The specifics vary, but common restrictions include:- Loss of Purchase event optimization. In some cases, brands lose the ability to optimize toward Purchase events entirely. Meta has an internal setting called “core setup” that is either on or off. When core setup is on, you typically cannot optimize toward Purchase events at all — this is the most severe level.
- Browser pixel data rejection. Meta may restrict or ignore data sent from the browser pixel on the flagged domain.
- Reduced audience building. With less event data flowing, custom audiences and lookalike audiences degrade over time.
Appealing the Flag
You can contest the flag through Meta’s support channels, and some brands do win their appeal, but a successful appeal does not guarantee a full resolution.How Upstack Handles It
For flagged stores, Upstack sends events to a new Meta dataset with Restricted Category Mode turned on for the Meta destination. It has four components that work together.1. Server-Side-Only Tracking
With Restricted Category Mode on, Upstack never loads the Meta browser pixel on your store and sends events server-side only, through Meta’s Conversions API (CAPI). The browser pixel sits on your website and grabs data automatically, including product names, URLs, and page content that may contain flaggable keywords, and Upstack cannot control what it pulls. By going server-side only, Upstack controls every piece of data sent to Meta. Why the Meta browser pixel is removed →2. Data Sanitization
Before sending any event to Meta, Upstack removes what could trigger a flag: product names are replaced with placeholders, product categories and brands are removed, and page paths are replaced with a hash. Product and variant IDs, prices, and quantities are still sent. Meta flags keywords in context — for example, a product like “Magnesium Supplement for Cramping” would be flagged because “cramping” is a medical condition in that context. Meta still receives what it needs for attribution and optimization — event type, purchase value, currency, and user identifiers — without the content that causes flags. What gets stripped and what Meta still receives →3. Domain Aliasing
All events are sent from a clean alias domain instead of your flagged primary domain: a separate root domain (not a subdomain) that you register, with a simple, compliant landing page and no real traffic. All CAPI events are reported as originating from this alias domain. You set it in Domain Alias on the Meta destination’s Category Mode tab. Without it, events still carry your store’s domain. Since the flag is attached to your domain (not your pixel), the alias domain prevents Meta from connecting the event data you’re sending to anything that has previously been flagged on their backend. How Domain Aliasing Works for Health & Wellness Tracking →4. Standard Purchase Optimization
Campaigns optimize on the standard Purchase event. Upstack still sends the legacyUPSTACK_HW_* custom events alongside the standard events (for example, UPSTACK_HW_6117d13b next to Purchase). Ignore them. They’re listed in Health & Wellness Category Events (Deprecated).
Moving to a New Dataset
A flagged pixel stays flagged, so Health & Wellness tracking always goes to a new dataset. A pixel that has never received any events also works.- Wait 24 hours after events start arriving on the new dataset before you launch campaigns on it. If Meta flags it again, it usually happens within that time.
- Then clone your campaigns onto the new dataset and move your spend over within about 10 days.
- Meta doesn’t deduplicate between datasets, so while campaigns run on both, one order can be counted by campaigns on each.
Ongoing Protection
Once Restricted Category Mode is on:- Keep every Meta event going through Upstack. A browser pixel, app, or script that sends events from your store’s domain can get the new dataset flagged.
- Keep the alias domain and its page live. If the alias domain changes, update Domain Alias in Upstack.
- Keep the Upstack pixel on your store. Storefront events are still captured by the Upstack pixel in the browser; only delivery to Meta is server-side.