Restricted Categories

Facebook restricted your ad account? You can still optimize for sales

If Meta has flagged your business as a restricted category, your pixel can only fire page views. Here is what that means, and how TrueMetriks gets your real conversions optimizing again

What Facebook changed

Meta now classifies websites in sensitive niches like health and wellness as special ad categories. Once your domain is flagged, Meta restricts the data it will accept from you. Your pixel, and even your server-side Conversions API, can effectively only send page views

The events that actually matter get blocked. Purchase, Lead, Add to Cart, Complete Registration and Book a Call no longer reach Meta, so they simply never show up in your Ads Manager

Who this affects

Meta assigns the category automatically from your site content and URLs, so plenty of businesses get caught even when they are fully compliant. The hardest hit include:

Health & wellness Supplements Beauty & aesthetics Medical & clinics Fitness & weight loss Mental health & therapy Dental Finance & insurance

Why it wrecks your campaigns

Only page views fire

Meta accepts page views but blocks your real conversion events at the domain level

No signal to optimize

With no purchase or lead data, Meta cannot find your buyers and your campaigns drift

ROAS collapses

Ads Manager shows almost no conversions, so your reporting and scaling both fall apart

How TrueMetriks fixes it

The fix is not another pixel or CAPI tool. It is sending Meta a conversion signal it will still accept. TrueMetriks lets you create a custom event with a safe, neutral name and map it onto the standard event you care about. Meta gets the optimization signal without the flagged event name, so your campaigns can learn and scale again

  1. 1Create a custom event in your TrueMetriks dashboard and set when it fires
  2. 2Map it onto the standard event you want to mirror, like Purchase, inside your Facebook integration
  3. 3Save, and TrueMetriks sends Meta a clean, safely-named signal it will accept

Custom event mappings

x7g2q9
The Custom event mappings panel inside your Facebook integration in TrueMetriks.

Purchase is the standard event you want to optimize for. x7g2q9 is an arbitrary name you make up - it can be anything, because Facebook only blocks the standard event names it recognizes, not random ones. When: Always sets the condition for sending it

So when a purchase happens on your site, TrueMetriks sends Facebook a conversion called x7g2q9 instead of Purchase. Facebook still receives the sale and can optimize your campaign towards it, but because the name is not on its restricted list the event is not blocked

Restricted by Facebook? Let's fix your tracking

No credit card required