Meta Tracking for Medical and Healthcare Sites on WordPress

You have three ways to reduce the risk with PixelYourSite, separately or in combination: strip the risky parameters from Meta events, replace standard conversion events with custom ones, or stop tracking the sensitive parts of the site entirely. Pick the combination that fits how much of your business is medical.

No setup guarantees this works. Meta detects medical and health content in ways you don’t fully control — by scanning page text, image content, URL patterns, your domain category, your ad creatives, and signals from other sources beyond your events. Stripping parameters and renaming events reduces the obvious tells, but it does not make the site invisible to Meta’s classifiers. Restrictions can still hit accounts that did everything on this page. Treat these strategies as risk reduction, not a fix.

What Meta actually restricts

Meta’s policies block sharing of Protected Health Information through advertising tools. In e-commerce, the most common ways PHI leaks into events are:

• Product names like HIV_test_kit or Insulin_pump_X.
• Page titles like Buy Blood Pressure Monitor Online.
• URLs with category slugs like /category/diabetes-care/.
• Tags and categories assigned to medical products or articles.

Meta’s enforcement applies most strictly to lower-funnel events (Purchase, AddToCart, Lead) because those events strongly imply user intent and condition. PageView and ViewContent get more leeway.

The three strategies on this page address each layer: drop the risky data, drop the risky event names, or drop the page entirely.

Strategy 1: Strip risky parameters from Meta events

The video shows the setting. PYS Pro adds a Medical Content card to the Meta settings page. Turn it on, choose which parameters to drop, and PYS removes them from every Meta browser pixel and CAPI event for the whole site.

Where: PixelYourSite Pro → Meta (Facebook) → Medical Content card.

• Don’t track parameters — the master toggle for the Medical Content filter.
• Don’t track these parameters for the Meta pixel and CAPI events — multi-select. Default list:
  • event_url
  • post_title
  • page_title
  • landing_page
  • content_name
  • categories
  • category_name
  • tags

Add any other parameter that could leak PHI on your site (for example, a Custom Event parameter you populate with a medical-related value).

This setting applies to Meta only. To remove the same parameters from Google Analytics, Google Ads, TikTok, Pinterest, or Bing events, use the global parameter controls on the Dashboard, the WooCommerce page, or the EDD page.

Strategy 2: Replace standard events with custom events

Standard events like AddToCart, Purchase, and Lead carry strong intent signals. Meta is more likely to restrict them on a medical-flagged account. The workaround is to fire a Custom Event with a neutral name instead — event_purchase_alpha, cart_step_b, anything that doesn’t telegraph the medical action.

PixelYourSite includes two triggers built for this:

• WooCommerce Add to Cart — fires when a Woo AddToCart action happens.
• WooCommerce Purchase — fires when a Woo Purchase action happens.

Where: PixelYourSite Pro → Events → Custom Events → Add new event → Triggers.

Pick either trigger, give the event a neutral name in the Meta tag card, and enable auto-value tracking to attach value and currency automatically without naming the product.

Then disable the corresponding standard event in your WooCommerce settings so it doesn’t fire alongside the custom one.

Using the custom event in Meta Ads

After the event starts firing:

1. In Meta Events Manager, find your custom event in the events list. Verify it’s reporting.
2. In Ads Manager, create or edit a campaign. At the ad-set level, pick your custom event as the conversion event.
3. Build Custom Audiences and Lookalike Audiences off it the same way you would for any standard event.

The custom event behaves like a standard event in Meta’s UI, only without the name that triggered restrictions.

Strategy 3: Stop tracking sensitive pages entirely

If medical content is a small slice of your site and not key to your ad spend, just block the pixel from those pages. The rest of the site tracks normally; the medical pages are invisible to Meta.

How, with the Super Pack add-on: PixelYourSite Pro → Meta (Facebook) → Hide rules.

• Hide if page URL includes — block specific URLs (e.g. /blood-pressure/).
• Hide if landing URL includes — block the entire session when the visitor enters via a medical URL.
• Hide on specific WordPress pages, posts, categories, or tags — use the per-page exclusions.
• Hide on specific WooCommerce products, categories, or tags — same idea, for products.

Combine with Strategy 1 or 2 if the rest of the site still needs the parameter stripping or the custom event swap.

Picking the right combination

Things this won’t do

• No legal compliance guarantee. This is risk reduction, not HIPAA compliance. PixelYourSite is not a Business Associate Agreement partner. If you handle actual patient data (appointment bookings, patient portals, medical records), Meta tracking on those flows almost certainly violates Meta’s own terms regardless of which parameters you strip. Talk to a healthcare-compliance attorney before running ads against patient-side flows.
• Doesn’t change what Meta sees server-side from other sources. If your checkout sends order data to Meta through another integration (Conversions API directly, another plugin, a server-side tool), the parameter filtering only applies to PYS’s own events.
• Custom Events can still be restricted. A neutral name helps, but Meta also scans page content and patterns. If everything on the site is medical, neutral names alone won’t fully shield you from restriction.
• Doesn’t substitute for consent. Visitors in the EU, UK, and several US states still need a consent banner. See Meta Limited Data Use (LDU) for US state opt-outs and ConsentMagic for the consent layer.