Health & Wellness
Run health and wellness ads without getting flagged.
If you sell anything Meta treats as health and wellness, you have watched performance fall without warning. Upstack strips the fields that trigger category detection before they reach Meta, and forwards everything the algorithm actually matches on.
Used by supplement, skincare and wellness brands in restricted categories
The problem
Category detection reads your payload, not your catalogue.
Restricted targeting, flagged ads and account reviews arrive without notice. The cause is rarely the product — it is that standard tracking forwards product names, categories and descriptions, and those fields are what category detection reads.
| Field in the payload | Result | Effect on delivery |
|---|---|---|
Product nameCollagen Supplement 60ct | Flagged | Health category restriction applied |
CategoryHealth & Wellness | Flagged | Targeting options limited |
Content typesupplement / vitamin | Flagged | Audience reach reduced |
Outcomeaccount review triggered | Restricted | Event data deprioritised or blocked |
“We’re part of the health and wellness category. I feel like we’re definitely seeing performance hits big time.”
“We got flagged about a month ago. I appealed it and it didn’t work.”
How it works
Strip what triggers detection. Keep what drives optimisation.
Three steps, configured once.
Route events through a filtered container
Events leave your store and pass through Upstack before they reach Meta’s Conversions API. Field rules are applied there, once, rather than being maintained separately in every tool that touches the payload.
Keep the signal the algorithm needs
Hashed email and phone, the click ID, purchase value and a persistent external ID all continue through untouched. These are the fields Meta matches on — none of them describe what the product is.
Send a different payload to each destination
Filtering is per destination, not global. Meta receives a payload without health-category fields; your warehouse and your analytics still receive everything, because they have no such restriction.
What changes
Before and after the filter.
| Dimension | Standard tracking | Filtered payload |
|---|---|---|
| Category flags | Recurring flags and account reviews | Removed at the payload level |
| Match quality | Degraded once events are restricted | EMQ 7.5+ maintained |
| Acquisition cost | 2–3× pre-restriction levels | Returns toward pre-restriction levels |
| Payload control | All fields forwarded by default | Per-destination field rules |
| Where it is fixed | Appeals, after the fact | Before the event is sent |
Field by field
Exactly what leaves, and what does not.
Withheld from Meta
Fields that describe the product
- Product names containing health keywords
- Health & Wellness category values
- content_type values such as supplement or vitamin
- Product descriptions naming an ingredient or condition
Forwarded as normal
Fields Meta matches on
- Hashed email — the primary matching signal
- Hashed phone in E.164 format
- Click ID (fbclid), when present
- Purchase value and currency
- Client IP and user agent
- External ID, persistent across sessions
Customer results
What identity resolution is worth alongside it.
Filtering removes the flag. Resolution is what recovers the performance.
33% CAC reduction
90× return on the platform fee, and $92K a month in recovered abandonment revenue.
+128% customers identified
More identified customers means better optimisation even under category restrictions.
−20% CAC
+24% MER across the media mix, from sending complete conversions rather than partial ones.
Why this is the right fix
Appeals treat the symptom.
Data minimisation, not evasion
Meta’s category detection reads the payload, not your catalogue. Sending a product name that is irrelevant to conversion matching is a choice, not a requirement — and not sending it is ordinary data minimisation.
Standard CAPI moves the problem
Sending the same payload from a server rather than a browser changes where the data comes from, not what is in it. If the fields that trigger a flag are still present, the flag still happens.
The cause, not the symptom
An appeal asks for a decision to be reversed while the payload that produced it keeps sending. Filtering the fields addresses the input instead of contesting the output.
Rules you can read
Every rule is visible and every payload is inspectable, so you can see exactly which fields left and which were withheld, per destination, per event.
Common questions
Health and wellness compliance, answered.
Is this a workaround for Meta’s policies?
No. It is a decision about which fields to send. Meta’s conversion matching runs on identifiers — hashed email, phone, click ID — and none of those describe a product. Withholding a product name that plays no part in matching is data minimisation, and it is the same principle behind sending hashed identifiers rather than raw ones.
What counts as health and wellness to Meta?
Broader than most brands expect. Supplements, skincare with active claims, fitness, sexual wellness and anything implying a condition or outcome can all fall inside it. Meta publishes the current definition, and it changes — we will point you at the version that applies when we scope your account.
Can I still optimise for purchases?
Yes. The purchase event, its value and its currency are all forwarded. What changes is that the payload no longer carries fields describing what the product was.
Do I need a separate set-up per destination?
No. Rules are configured once and applied per destination, so Meta can receive a filtered payload while your warehouse receives the complete one.
How quickly does performance recover?
It depends on how long the account has been restricted and how much of your spend sits in affected campaigns, so we would rather scope it against your account than quote an average that will not hold for you.
What if Meta changes the policy?
The rules are configuration rather than code, so the field list can change without a re-implementation on your side.
Does this affect Google or TikTok?
Only if you want it to. Filtering is per destination, so a rule applied to Meta leaves every other destination untouched.
Will you tell me what was removed?
Yes. Every event is inspectable, showing which fields were forwarded and which were withheld for each destination.
Stop losing performance to category restrictions.
Talk to us about which fields your products are sending, and what happens when they stop.