- 1PD Ops Club
- Posts
- A server-side tool didn't fix Meta's health restrictions for Good Body Clinic
A server-side tool didn't fix Meta's health restrictions for Good Body Clinic
Server-side tracking changes the route data takes. It doesn't change Meta's rules, or whether Meta can match the event to a person.

Hellooo,
"We added a server-side tracking tool, why is Meta still restricting our health account?"
This is the question behind a blog we just published, and the short answer is: a server-side tool alone doesn't establish compliance. It changes how an event reaches Meta, not whether Meta is willing to use it.
Server-side tracking changes the route, not the rule
Routing events through the Conversions API instead of the browser pixel gets data past ad blockers and iOS tracking limits. It does not establish that the data is now acceptable to Meta.
Meta has said directly that the Conversions API "isn't designed to be a means to bypass data-sharing policies", the restriction is attached to the business category and the content of the event, not the transport layer.
If the event still carries a condition name in a URL or a treatment type in a parameter, sending it server-side just moves the same problem to a different pipe.
The data still has to be clean before it leaves
A server-side tool typically passes along whatever it receives. It doesn't scrub a URL that reads /appointments/schedule?type=cardiology, and it doesn't rename an event called schedule_fertility_consultation.
If your tracking setup assumes the tool itself does this scrubbing, that assumption is worth checking against what the tool's documentation actually claims, most don't.
This is close to what happened with Good Body Clinic, where product URLs carried treatment names and dosage information. Their account came back online once URL scrubbing was switched on and PHI was removed before it reached Meta, the fix was in what left the server, not in adding a server between the browser and Meta.
Worth flagging what this does and doesn't establish: CustomerLabs reports the account was back online inside 24 hours and Event Match Quality improved. It does not disclose a revenue or profit figure, so treat the result as evidence of restriction recovery, not of ad spend efficiency.
Matching is the bottleneck nobody budgets for
Meta can only use matched events for attribution and optimization. If advanced matching is unavailable under a core (restricted) setup and browser-side tracking is disabled to stay compliant, you lose the browser identifiers that normally stitch a visit to a person.
A shopper who visits from an ad, comes back later through search, and converts a week after that looks like three unrelated people with few matching clues, not because the purchase event failed to send, but because nothing tied the three visits together. If your reporting shows events arriving but Event Match Quality still low, this is usually where to look first.
This is the gap that industry-specific first-party tracking for health and wellness brands is built to close: assigning an external ID on first visit, merging sessions into one identity-resolved profile, and sending that full history along with the conversion, none of which a generic server-side setup does on its own.


What this doesn't fix
None of this restores an event type Meta has already restricted for your account. If a bottom-funnel event is blocked at the category level, scrubbing and identity resolution improve the signal quality of what you can still send, they don't reopen a door Meta closed. If your immediate problem is a fully blocked account rather than weak matching, the restricted-account guide is the more relevant starting point than this one.
What to check in your own account
Do any event names or URL parameters still reference a condition, treatment, or product category by name?
Is advanced matching active, or did it drop out when server-side tracking was switched on?
Is your Event Match Quality score explainable by matched identifiers, or is it propped up by volume alone?
Are qualified CRM outcomes (booked consultation, closed lead) ever sent back to Meta, or does that data stop at your CRM?
Full breakdown, including the comparison between a standalone server-side tool and a first-party data layer:Will a Server-Side Tracking Tool Fix Meta's Health Restrictions?

Reply