Restricted categories

Video guide

Why standard events get throttled

If your business sits in a category Meta restricts (health, wellness, weight loss, finance, supplements, gambling, dating, alcohol, and a few others), Meta will block or throttle ad delivery when you optimise on certain standard event names: Purchase, Lead, InitiateCheckout, AddToCart, Schedule, and ViewContent. In practice you get pushed back to PageView, which is too high in the funnel to optimise on, so your ROAS suffers even when the offer converts fine.

The workaround is to stop sending the restricted standard event and instead fire your conversion through a custom event with a neutral, meaningless name. TrueMetriks sends everything server-side through the Conversions API, so you fully control the name Meta sees. Meta's pattern detector cannot map a random name back to a restricted intent, so your delivery is judged on performance, not on the label.

Rule 1: give the event an arbitrary name

This is the part most people get wrong. The whole point is that the event name reveals nothing. So do not name it anything that hints at what it is:

• Bad: custom_purchase, purchase_v2, real_purchase, buy, checkout, lead_real, sale. Each of these still contains the intent Meta is looking for.
• Good: ghu, kt8x2, evt_a7, kenny_florian, bluefin - a random string or unrelated word that carries no meaning. Meta sees a name it cannot classify, so it has nothing to restrict.

Pick something you will recognise in your own reporting but that means nothing to an outside pattern detector. Avoid any of the words purchase, buy, cart, checkout, lead, signup, subscribe, order, sale. A short nonsense token like ghu is the safest choice.

You still get a clean, dedicated conversion column in Ads Manager and you optimise campaigns against it exactly like a normal Purchase. The only thing that changed is the label.

Rule 2: keep your product names and URLs neutral too

The event name is not the only thing Meta reads. Its systems also scan your landing page URLs, product names, and on-page content. If your custom event is called ghu but it fires on yoursite.com/diabetes-destroyer, you have given the game away - the URL hints at exactly what the offer is.

So apply the same discretion everywhere the platform can see:

• Product names / slugs: use a neutral code, not the marketing name. Diabetes Destroyer becomes Program A or offer-7; Keto Shred Pro becomes bundle-b.
• URLs: prefer yoursite.com/p/offer-a or yoursite.com/order/7 over yoursite.com/diabetes-destroyer. The path should not describe the niche.
• Anything the pixel or crawler can read (page titles, content names sent with the event) should stay just as neutral as the event name.

The goal is consistency: a meaningless event name plus a neutral URL and product name give Meta nothing to classify. A neutral event name next to a giveaway URL does not.

Set up the custom event

You create the custom event inside the TrueMetriks integration card for your pixel, the same place the Allowed events checkboxes live. First, uncheck the restricted standard (for example Purchase) in Allowed events so only your neutral custom name fires. Then create the custom event.

Step 1: click Create

Inside the expanded pixel row, scroll to the Custom events panel and click the highlighted Create button.

Step 2: fill in the popup with a neutral name

The Create custom event popup opens. Set:

• Standard event (dropdown) - the standard event you want to mirror. Pick Purchase to fire every time a Purchase would have. Same for Lead, Schedule, and so on.
• Custom event name (input) - your arbitrary name from Rule 1, such as ghu. This is the name Meta sees.
• Fire when (dropdown) - Always is the default. For Purchase, Lead, and Schedule you can also pick New customers only or Returning only to split your audience (see New vs returning customers).

Click Create, then click the highlighted Save changes button at the bottom of the card to create the Custom Conversion in Facebook.

Step 3: confirm the Custom Conversion in Facebook

The moment you save, TrueMetriks calls the Meta API and creates a Custom Conversion in Facebook for you - you do not set it up by hand. To confirm, open Meta Ads Manager → Events Manager → pick the pixel you mapped → Custom conversions tab. Your neutral name shows up there.

It stays Inactive until the first event lands. Fire a test event or wait for live traffic; the status flips to Active once Meta sees the first conversion.

Step 4: add the conversion as a column

In Meta Ads Manager → Campaigns (or Ad sets / Ads) → the Columns: Performance dropdown → Customize columns. Search for your neutral name, tick Total, Value, and Cost on the matching row, then click Apply.

Step 5: read the column and optimise on it

The Campaigns / Ad sets / Ads table now has a dedicated column for your custom conversion. Use it exactly like a Purchase column - sort by it, build saved reports, and set automated rules and ad-set optimisation against it.

Gotchas

• Wait 30 to 60 seconds after Save before firing test events. Meta needs to finish creating the Custom Conversion first; events fired too early land without the conversion attached.
• Removing a custom event in TrueMetriks does not delete the Custom Conversion in Facebook. It stops the custom name from firing, but the entry stays in Events Manager. Delete it manually from Facebook's Custom conversions tab if you no longer need it.
• Custom Conversions have a 100-per-pixel limit (Meta's restriction). Each custom event counts as one; the list shows how many you have remaining.

Related

• Facebook integration - the full custom events reference and how the Conversions API connection works.
• New vs returning customers - use the When condition to split a restricted-category conversion by audience.