What your store sends to Meta
The Meta Pixel sits on every page of the store. When a shopper views a product, adds it to cart, checks out and buys, the Pixel sends each step to Meta as an event, recorded in the store's dataset in Meta Events Manager.
Each event carries parameters: the product name (content_name), its ID (content_ids), the page URL and the value. Two first-party cookies, _fbp and _fbc, identify the browser and the Meta ad that was clicked, and a Purchase can carry customer details such as email, phone, city, state, zip, country and IP address, sent hashed, which Meta uses to match the event to a person's account.
- event_name
- Purchase
- content_name
- Weight Loss Gummies
- content_ids
- [LF-GUM-60]
- event_source_url
- leanfield.shop/products/weight-loss-gummies
- value
- 49.00 USD
- _fbp · _fbc
- fb.1.1790343215482.1873920465 · fb.1.…
- em · ph
- [email protected] · +1 303 555 0142 (hashed)
- ct · st · zp · country
- Denver · CO · 80205 · US (hashed)
- client_ip_address
- 73.14.201.88
Why that is health information
On a Health & Wellness store, the product is the signal. An order for weight-loss gummies, attached to one person, implies something about that person's body and health.
In healthcare, disclosing a patient's health information to an ad platform can be a HIPAA violation. Meta's data-sharing rules treat health and wellness signals with the same caution, whether or not HIPAA applies to your store.
How Meta classifies the store and restricts its data
Meta assigns each data source a category from what it can see, including product names and URLs. A store that sells health and wellness products can be classified Health & Wellness.
For a restricted category, Meta can turn on Core Setup, which, in Meta's words, “restricts the sharing of custom parameters and parts of URLs following the domain.” In Zappush's experience auditing restricted domains, lower-funnel events such as Add to cart, Initiate checkout and Purchase can be blocked or stripped as well.
What it costs your campaigns
A campaign optimizing for Purchase learns from the purchases Meta receives. When Purchase is blocked, the ad set keeps spending with no conversions to learn from, and delivery can sit in Learning limited.
Why your ads can be approved while your data is restricted
Ad review and domain classification are separate systems. Meta reviews the ad creative through one process and classifies the domain's data source through another; passing one does not change the other. A brand can have approved ads delivering impressions and clicks while its conversion events are suppressed.
Why the usual fixes don't lift it
01
Rename the event
Meta evaluates the whole payload, not the event name. conv_01 carrying “Weight Loss Gummies” says the same thing.
02
Switch to the Conversions API
Server-side events follow the same data-sharing rules as the Pixel. The delivery changes; the data doesn't.
03
Appeal
It can work for a misclassified domain. For stores that genuinely sell health products, we've found no documented reversal.
How Zappush lifts it
Zappush is Health & Wellness compliant infrastructure, built specifically for health and wellness brands. It removes the health signal from every event (the product name, ID and page URL) before it reaches Meta, then sends the event server-side.
Meta still receives the Purchase and its value. With no health data reaching Meta, there is nothing to restrict: the same sale, without the health inference.