Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Learn how Upstack’s Health & Wellness container restores accurate Meta tracking using server-side-only delivery, data sanitization, domain aliasing, and custom event mappings.

​
Overview

When Meta flags your store under Health & Wellness, standard tracking breaks down. Upstack Data implements a specialized Health & Wellness container that works around these restrictions while staying fully compliant. The result: Meta receives high-quality conversion data for optimization, and your store avoids being re-flagged. The solution has four components that work together.

​
1. Server-Side-Only Tracking

For Health & Wellness stores, Upstack removes the Facebook browser pixel entirely and operates server-side only via Meta’s Conversions API (CAPI). Why this matters: The browser pixel (JavaScript) has a mind of its own — it sits on your website and grabs data automatically, including product names, URLs, and page content that may contain flaggable keywords. Upstack cannot control what the browser pixel pulls, and it runs in the background independently. By going server-side only through CAPI, Upstack has complete control over every piece of data sent to Meta with 100% guaranteed delivery. The entire Upstack platform is built around ensuring redundancy without the browser pixel.

​
2. Data Sanitization

Before sending any data to Meta, Upstack pre-processes it to remove anything that could trigger a flag:
  • Product names containing health/wellness keywords are stripped — for example, a product like “Magnesium Supplement for Cramping” would be flagged because “cramping” is a medical condition in that context.
  • Product URLs with flaggable terms are cleaned.
  • Product descriptions that could indicate medical conditions are filtered.
  • SKUs, product IDs, and titles are removed or anonymized.
  • Only essential data is sent: event type, purchase value, currency, and user identifiers (email, phone, click ID).
Meta still receives everything it needs for accurate attribution and optimization — without the content that causes flags.

​
3. Domain Aliasing

All events are sent from a clean alias domain instead of your flagged primary domain. This prevents new pixels from inheriting the flag. How it works:
  • The alias domain is a separate root domain (not a subdomain) that you register.
  • It has a simple, compliant landing page — just a headline and an image.
  • No real traffic is ever sent to this domain. It exists so Meta’s compliance bot sees a clean page.
  • All CAPI events are reported as originating from this alias domain.
Since the Health & Wellness flag is attached to your domain (not your pixel), aliasing is what makes the entire solution work. The alias domain prevents Meta from connecting the event data you’re sending to anything that has previously been flagged on their backend. Domain aliasing has no negative performance impact — it is purely a safety measure.

​
4. Custom Event Mappings

Standard Meta events (AddToCart, Purchase, etc.) are mapped to Upstack Health & Wellness custom events to avoid triggering Meta’s automated flagging systems. For example, the Purchase event becomes UPSTACK_HW_6117d13b and AddToCart becomes UPSTACK_HW_de792bda. These custom events must be approved in Meta Events Manager before they can be used for campaign optimization. For the full mapping table: Health & Wellness Custom Event Mappings → For instructions on approving custom events: How to Approve Facebook (Meta) Custom Events →

​
Dual-Pixel Transition Strategy

When switching to a new pixel, Upstack supports a dual-pixel approach:
  • Data feeds to both your existing pixel and the new clean pixel simultaneously.
  • Your current campaigns continue running on the existing pixel while the new pixel builds up data.
  • Once the new pixel has enough data (typically about a week), you can begin migrating campaigns.
  • How fast you switch depends on your current ad performance — if things are painful, switch quickly; if performance is acceptable, train the new pixel with data first and transition gradually.
If your existing pixel has not been flagged and retains its audience data, you may be able to continue using it instead of creating a new one. Discuss this with the Upstack team during onboarding.

​
Ongoing Protection

Once set up with the Health & Wellness container:
  • No re-flagging as long as all Meta events are sent through Upstack (no direct browser pixel, no data from the flagged domain). This approach has a 100% success rate in preventing re-flagging.
  • The alias domain stays in place permanently — the registration fee and hosting cost are the only ongoing expenses.
  • Theme changes don’t break tracking since everything is server-side (no Theme App Extension dependency for Meta events).
  • No extra cost — the Health & Wellness container, implementation, and ongoing support are all included in your Upstack subscription.

​
Get Started

Ready to set up the Health & Wellness solution? Follow the step-by-step guide: How to Set Up a Health & Wellness Pixel for Meta →

​
Related Articles