Question Posted by the DataCops team

Skincare on Meta: when does it count as health? (acne and rosacea vs a glow routine)

Skincare sits in a grey zone, and grey zones are where accounts get restricted. So let me lay out the shape of the grey, because "it depends" isn't helpful unless you know what it depends on.

It depends on what the product claims.

Cosmetic skincare, like a moisturiser or a glow routine, is usually not a health category. It's about how skin looks and feels, and nothing in it describes a condition.

Skincare that treats a condition often is. Acne, rosacea, eczema, redness, rough skin. Once the product or the page is about treating one of those, it reads as health. And Meta decides partly from your product pages and partly from the events you send.

That last part is the one people miss. So let me draw it as a ladder, from clearly cosmetic to clearly health.

Rung one: a glow serum, a hydrating cream, a cleansing routine. Cosmetic language. Usually fine.

Rung two: products aimed at concerns, like "for oily skin" or "for dullness". Mostly cosmetic, sometimes borderline.

Rung three: products aimed at named conditions: "acne treatment", "rosacea relief", "eczema cream". This is where a page starts to read as health.

The rung isn't only decided by the ad copy. It's decided by everything the platform can see: the product page, the page title, the URL, the product name, and the event names. A cosmetic brand can drift down the ladder by accident. A collection called /collections/acne-prone, a bundle called "Rosacea Calming Set", a conversion event called Purchase_Acne_Kit: each one moves the account a rung.

So what helps? Keep the condition out of the parts that travel with every purchase: the page link, the product name in the address, and the event name. Sell the set, keep the condition out of your ad data. The purchase still counts. It just doesn't carry the diagnosis with it.

A small made-up example. Before: yourshop.com/products/rosacea-calming-set, event called Purchase_RosaceaSet. After: yourshop.com, event neutral, value and a hashed identity attached. Same sale, same match, nothing in it that says what a person's skin condition is.

To be clear about what this is and isn't. It's about not leaking condition data through tracking. It isn't a way to make claims your product can't back up, and the ad itself still has to follow Meta's rules on health claims.

If you have a catalogue of fifty products, here's how to audit it quickly. Export your product URLs and titles into a sheet. Sort them by the words they contain: any that mention a condition (acne, rosacea, eczema, redness, dermatitis, and so on) get flagged. For each flagged product, decide: is the page really about treating a condition, or is the wording just careless? For the careless ones, you can often reword the URL or title without changing the product. For the genuine ones, keep the condition out of the events and the page links that travel with the purchase.

Don't forget collection and category pages. A collection called /collections/acne-prone is where the visitor was before they bought, and that referrer can travel with the event. And check your discount codes, because a code called ROSACEA20 ends up in URLs and order data.

Then re-run the audit after each new product launch. New products are the usual way a clean catalogue drifts.

Where does your skincare or derm brand sit? Cosmetic, treatment, or somewhere in between?

More on this: Meta health and wellness restrictions, and the complete guide to offline conversion tracking.

1 comment

Comments (1)

DataCops team author · 30 Sep 2026

Practical check: read your best-selling product page's URL and title out loud. If it names a condition, that's the part that travels with every purchase event.

1
Replies from DataCops account holders are coming soon. Until then, questions about your own setup can go to the team.

More threads

See what your own setup is missing

Send CRM sales back to the ad click that started them, logged per send.

Setup in 5 minutes. No credit card.

Live traffic quality

Updated just now

Visits · last 24h

487
Real users
35873.5%
Bots · auto-filtered
12926.5%

Without filtering, 26.5% of your reported traffic is bot noise inflating dashboards and draining ad spend.

Don't trust your analytics!

Make confident, data-driven decisions withactionable ad spend insights.

Setup in 2 minutes
No credit card