I start health and wellness measurement work by checking what may be sent. I do not start by making the purchase count higher.
There are three separate reviews. An ad can pass creative review while its associated data needs a different decision. A reduced payload can still come from a restricted source.
Advertising rules
Meta’s current Health and Wellness policy requires adult targeting for specified dietary, health, weight-management and cosmetic offers. It also lists exceptions, including general wellbeing and certain food or beauty products. It restricts particular claims and creative treatments.
I would not reduce that page to “all wellness ads need 18+” or “all before-and-after images are banned.” The current policy permits some before-and-after cosmetic transformations. The media team needs to check the exact product, wording and creative.
Passing ad review does not clear the measurement payload.
Data and source restrictions
Section 1.h of the Business Tools Terms prohibits data that includes or is based on health information. It also applies to the names and criteria of events, conversions and custom audiences. The terms cover both pixel and CAPI data.
Meta’s data-source category help describes additional sharing restrictions for some categories, including Health and Wellness. It directs businesses to review their classification in Events Manager and request review if it is wrong.
I check the category and the notices that actually apply. I do not promise that Purchase remains usable merely because the event has a value and currency.
Inspect what leaves the system
My technical review covers:
- URLs, query strings and referral fields.
- Product IDs, names, categories and custom parameters.
- Event names and conversion criteria.
- Audience definitions and their underlying source.
- Browser and server payloads, including consent handling.
Removing a diagnosis from an event name is not enough if another field or the source context still reveals it. Product-specific cart abandonment and purchase history can carry the same problem. I do not treat them as an approved fallback.
I decline condition-page audiences and attempts to disguise blocked events. If the applicable rules prohibit sharing, the implementation stops that transmission.
Use CAPI only after permission is established
A pixel and CAPI setup can provide two delivery routes for a permitted event. Both routes need the same sharing boundary.
Consent is one input. It does not override Meta’s terms. A server can deliver a prohibited event successfully; transport success is not compliance.
Report the gaps
The store’s internal orders remain the commercial record. Meta attribution is a separate view, subject to the data it receives and can use.
I reconcile recorded events with orders and label restricted or withheld events as such. The order-by-order reconciliation situation describes that work. I do not promise that every store order can be found individually in Meta’s reporting or attributed to an ad.
How I can help
I can audit payloads, implement permitted collection and document withheld events under Meta Conversions API work. Counsel supplies the legal position, including any HIPAA obligations. I implement the resulting boundary and verify the outgoing data. If the scope is clear, I can quote it; otherwise we agree a separate diagnostic engagement.
