Server-Side Tracking for Skincare Brands
Why skincare brands lose purchase data, when Meta treats a beauty store as health and wellness, and how to set up server-side tracking cleanly.
Article summary
TL;DR
Server-side tracking sends purchase events from your server to Meta, Google and TikTok, so ad blockers and browser limits don't erase them. Cosmetic skincare isn't one of the business types Meta's health and wellness data restrictions are known to target, but product names and URLs that name skin conditions can make your data look medical. Send complete, neutral data, and never disguise events.
- Meta recommends running the Conversions API alongside the pixel, deduplicated with the same event name and event ID.
- PixelFlow lists medical conditions, supplements, weight loss, prescription drugs and health services as health and wellness; skincare isn't on the list.
- Meta doesn't publish the list in this form, so check your own dataset's category in Events Manager.
- Product names like "acne treatment" or URLs like /eczema/ describe a condition; keep them out of the data you send.
- Upsells and subscription renewals need server events, or they never reach the ad platforms.
ChatGPT
Claude
Perplexity
GrokOn this page
This guide is part of our playbook on the best ecommerce platform for skincare brands. Ad rules: Meta and TikTok ads for skincare brands.
Why pixels miss skincare sales
Ad blockers and browser privacy
They stop part of the pixel events.
Upsells and routine add-ons
After payment, they often fire no browser purchase.
Subscription renewals
They happen without any browser.
Checkout on another domain
It can break the session.
Each lost purchase inflates your CAC and teaches the ad platform less about who buys.
Is a skincare brand "health and wellness" for Meta?
| Business type | Listed as health and wellness? | Source |
|---|---|---|
| Medical conditions, health statuses | Yes | PixelFlow2PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation) |
| Dietary supplements, weight loss | Yes | PixelFlow2PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation) |
| Prescription drugs, pharmaceuticals | Yes | PixelFlow2PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation) |
| Health-related services and remedies | Yes | PixelFlow2PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation) |
| Cosmetic skincare and makeup | Not listed | PixelFlow2PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation) |
Practitioner summaries; Meta does not publish this list in the same form.
What tips a skincare brand toward "health":
- Condition words in product names, URLs and categories: acne, eczema, rosacea, psoriasis.
- Drug-like products in the catalog, such as acne treatments with active drug ingredients4FDA, Is It a Cosmetic, a Drug, or Both? (Or Is It Soap?), September 11, 2024.
- Quiz answers about skin conditions sent as parameters.
Check your status in Events Manager: dataset settings, then "Manage data source categories"2PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation).
Watch out
Renaming purchase events with coded names so Meta doesn't recognize them is a way around Meta's rules. It puts the ad account at risk. Send what you are allowed to send, accurately.
What server-side tracking fixes, and what it doesn't
| Server-side tracking... | Fixes | Doesn't fix |
|---|---|---|
| Sends events from your server | Events lost to ad blockers | A health and wellness category already applied |
| Sends the purchase where it is paid | Upsells, renewals, cross-domain checkout | Ads rejected for claims3Meta Advertising Standards, Health and wellness, change log entry July 22, 2026 |
| Lets you choose the fields | Condition words leaking in URLs and names | Weak offers or creatives |
| Covers Meta, Google and TikTok | Under-reporting on all three | Consent you didn't collect |
What data to send
| Send | Don't send |
|---|---|
| Event name and event ID, shared with the pixel1Meta for Developers, Deduplicate Pixel and server events, read October 26, 2026 | Product names naming a condition ("acne kit") |
| Order value and currency | URLs or query strings with condition words |
| Hashed email and phone, where consented | Skin quiz answers about conditions |
| Neutral product IDs or categories ("serum", "cleanser") | Custom parameters implying a health status |
Neutral data is not a trick: it's what you should send anyway.
Setup
- Keep the pixel for browser events.
- Add the Conversions API and TikTok's and Google's server-side equivalents, from the system that takes payment.
- Use the same event name and event ID in pixel and server events, so Meta deduplicates them1Meta for Developers, Deduplicate Pixel and server events, read October 26, 2026.
- Send upsells and renewals from the server.
- Map products to neutral categories before sending.
- Respect consent for the hashed data you send.
Same event name and event ID in pixel and server events, so Meta deduplicates them.
Fig. 1One purchase, two events, one count
- PixelBrowser event, can be stopped by ad blockers
Conversions APIServer event from the system that takes payment
Same event name, same event ID: Meta keeps one purchase.
Check that it works
| Check | How | Healthy sign |
|---|---|---|
| Deduplication | Events Manager, event overview | Browser and server events merged, not doubled |
| Coverage | Ads Manager purchases vs. store orders | A small, stable gap |
| Restriction status | Data source categories2PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation) | NoLimitation |
| Upsells and renewals | Server events by type | Present, with correct value |
Then use the data for attribution: ad attribution for skincare brands.
How Tagada helps
Purchase events sent from the checkout that gets paid
- Server-side events to Meta, Google and TikTok, sent from the checkout that takes the payment
- One-click upsells and subscriptions in the same checkout
- One-page checkout with Apple Pay and Google Pay
It runs standalone, on Shopify, on WooCommerce or headless. Plans are on the pricing page.
Frequently asked questions
Is skincare restricted by Meta's health and wellness rules?
Why is Meta not tracking all my skincare purchases?
Do I need both the pixel and the Conversions API?
What data should a skincare brand send to Meta?
Sources
Checked October 26, 2026- Meta for Developers, Deduplicate Pixel and server events, read October 26, 2026
- PixelFlow, What are Meta's health and wellness restrictions and how do they affect tracking, read October 26, 2026 (vendor documentation)
- Meta Advertising Standards, Health and wellness, change log entry July 22, 2026
- FDA, Is It a Cosmetic, a Drug, or Both? (Or Is It Soap?), September 11, 2024
Tagada
Get every skincare purchase back to your ad platforms
Funnels, one-click upsells, subscription billing and payment routing, on one customer record.
- 01Create your free account
- 02Connect your store or build a checkout
- 03Launch funnels, upsells and subscriptions