Meta's health and wellness restriction: what Meta stops receiving

By the HonestTag team ยท Published November 20, 2026

HonestTag Learn: Meta's health and wellness restriction: what Meta stops receiving

Meta has placed your website in a category such as health and wellness, and purchases have dropped out of Ads Manager while your Shopify orders keep coming in.

A restricted category is Meta's own limit on what it takes in from your store, not a fault in your tracking: depending on the level, Meta stops taking in custom parameters and the part of each URL after the domain, specific mid and lower funnel events, or every event in some regions or all of them, so Ads Manager can show fewer purchases while your orders do not change. Meta may assign these categories from your site's topics and products, and says that when it limits or fully restricts a data source, it tells you by email and in Events Manager notifications. Sending events from a server does not change it, because Meta counts the Conversions API among the tools the restrictions cover. HonestTag counts the new customers whose first recorded ad click was a Meta ad from your store's own orders, so that count does not depend on what Meta takes in.

What Meta restricts, and who decides

Meta may assign a category to your website "based on the topics related to the data source and the products and/or services provided," and says certain categories "may have additional data sharing restrictions." Health and wellness is the one Shopify merchants ask about on Shopify's Community forum, and Meta defines it widely: a site "associated with medical conditions or specific health statuses," or with "health-related products and services." Meta lists others too, such as financial service, and says the list "is not exhaustive and may evolve over time."

Meta names three levels of restriction:

A restriction can also cover only part of your traffic: Meta says they "can be specific to certain countries or regions, or they could be applied globally." A store selling into several countries can see purchases fall in Ads Manager for some buyers and not others.

A category can come from two places. Meta may ask you to categorize your data sources, and gives you 60 days to do it; until you do, Meta applies the restrictions of "whichever category accounts for the most events in the same dataset." Meta can also assign a category itself. You can change a category you chose, but Meta says "you will not be able to modify a Meta-assigned categorization for your data source." If you think Meta's category is wrong, Meta says you can ask it to review it again, and that it tells you its decision by email.

Because the category follows what your site sells and talks about, a store that does not think of itself as a health business can still land in health and wellness. Merchants selling pregnancy and maternity products describe exactly that on the forum. Meta says that when it limits a data source, it tells you "via email and notifications in Meta Events Manager," so a restriction comes with a notice that names it.

The Conversions API and custom events under a restriction

Meta's restrictions apply to event data shared "via the Meta Business Tools," and Meta's Business Tools Terms name the Conversions API among those tools, beside the Meta Pixel. On our reading, purchases sent from a server reach a restricted dataset under the same limits as purchases from the browser pixel.

Custom events, the ones an app or tag sends under its own name, have a rule of their own. Meta says that when your business tool has data restrictions, "custom events are automatically blocked until you review and confirm them, or they may not be available to you," for example under full restrictions. Meta asks you to block a custom event you cannot confirm follows its Business Tools Terms, and says you are responsible for what you share, "including custom event names." A blocked custom event cannot be used with ads features. Custom conversions are checked too: Meta says they must not "suggest information not allowed under our terms," names references to specific health conditions as an example, and says a flagged one cannot be used in new campaigns.

So the forum advice to send a purchase under another name runs into Meta's own rules: on a restricted dataset that event starts out blocked, and the decision to confirm it, and the responsibility for what it carries, sit with you.

See what Meta ads bring when Meta cannot see the sale. HonestTag counts the new customers whose first ad click was Meta from your own Shopify orders, and the free Mirror plan sets Meta's claimed conversions beside them.

Install HonestTag free

How to tell a restriction from a tracking fault

A restriction and a broken tag can look the same in Ads Manager: purchases fall. What else changed tells them apart.

What you seeWhat it points to
An email or Events Manager notification from Meta about a data source categoryA restriction. Meta says this is how it tells you.
Some events keep arriving while purchases and checkouts stopThe restriction on certain standard events, which Meta says covers mid and lower funnel events
Events keep arriving, but their page addresses show only your domainCore setup. Meta says details after the domain may be unavailable in Events Manager, test events included.
Every event stops, in some countries or everywhereFull restrictions, or a tag that stopped sending. With no notice from Meta, look at your tracking first.
Purchases fall only for buyers in some countriesA restriction limited to certain regions

In every row, your Shopify orders are the fixed point. If your store's order count held while Meta's purchases fell, your sales did not drop; what Meta takes in or credits did. For drops with no category notice behind them, Meta purchases dropped suddenly walks through the other causes.

Ads Manager at zero while orders keep coming

The numbers below are made up to show the arithmetic. A store spends $3,000 a month on Meta ads. In the month before a restriction, Ads Manager reports 90 purchases, and the store's own orders show 60 new customers whose first recorded ad click was a Meta ad. Meta's 90 is the purchases Meta credits to its ads, while the 60 counts only new customers whose first recorded click was a Meta ad, so the two were never the same count.

Then Meta restricts the store's purchase events in every region, and in this example Ads Manager reports 0 purchases the next month. The store still spends $3,000, and its orders show 50 new customers whose first recorded click was a Meta ad.

Made-up example: Meta-reported purchases against new customers from Meta ad clicks, before and after a restrictionMade-up numbers, $3,000 of Meta spend each month. Before the restriction, Ads Manager reports 90 purchases and the store's orders show 60 new customers whose first click was a Meta ad. After it, Ads Manager reports 0 purchases and the store's orders show 50 such new customers.Made-up numbers$3,000 a monthMonth beforeMeta reports 9060 new customersMonth afterMeta reports 050 new customersfirst click a Meta ad, from your orders
Ads Manager's purchases go from 90 to 0, but the store's own orders show Meta ads still bringing 50 new customers a month.

Read from Ads Manager, the campaign stopped selling. Read from the store, it still brought 50 new customers, at $3,000 / 50 = $60 each, against $3,000 / 60 = $50 the month before. Whether $60 is worth paying is a margin question (see new-customer acquisition cost (NCAC) and break-even return on ad spend (ROAS)), and it can only be answered from the store's side while Meta cannot see the sale.

What this means

If Meta's purchases fell to near zero, your Shopify orders held, and Meta sent you a category notice, the drop is Meta's restriction, not your sales and not a broken tag. If only purchases and checkouts vanished while other events kept arriving, it is the restriction on certain standard events; if only some countries dropped, it is regional; if every event stopped with no notice, look at your tracking before you blame a category.

The cost is in the reading. With purchases restricted, Ads Manager can no longer tell you which campaigns sell, so a campaign judged on Meta's purchase column looks dead even while it brings customers, and money moves away from it on a number that stopped counting.

HonestTag counts the new customers Meta ads brought from your own Shopify orders, so you can still see what Meta ads start when Meta cannot see the sale.

How HonestTag helps

The Gap counts the new customers whose first recorded ad click was a Meta ad from your store's own orders, from Meta's click id in the landing address, so its count does not depend on what Meta takes in.

Install HonestTag free from the Shopify App Store, and the Mirror plan sets Meta's claimed conversions beside the new customers Meta ads brought, counted from your own orders.

Frequently asked questions

Does sending purchases from a server get around Meta's health and wellness restriction?

No. Meta's restrictions apply to event data shared through its Business Tools, and Meta's Business Tools Terms name the Conversions API among those tools, beside the Meta Pixel. On our reading, purchases sent from a server reach a restricted dataset under the same limits as purchases from the browser pixel.

Can I change a category Meta assigned to my website?

Not yourself. Meta says you can change a category you chose, but you will not be able to modify a Meta-assigned categorization for your data source. Meta says you can ask it to review a category you think is wrong, and that it tells you its decision by email.

Will a custom event with another name get my purchases through?

Not as a way around the restriction. Meta says that when your business tool has data restrictions, custom events are automatically blocked until you review and confirm them, or may not be available at all, for example under full restrictions. Meta asks you to block a custom event you cannot confirm follows its Business Tools Terms, and says you are responsible for what you share, custom event names included.

Does a restriction cover all my customers?

Not always. Meta says its data sharing restrictions can be specific to certain countries or regions, or applied globally. A store selling into several countries can see Meta's purchases fall for buyers in some countries and not in others.

Do HonestTag's events get through a restriction?

HonestTag's own events, sent on paid plans, are custom events, so Meta's custom-event rules apply to them like any other: on a restricted dataset they start out blocked until you confirm them, and under full restrictions they may not be available. What HonestTag adds is a count the restriction does not change, because it is read from your own Shopify orders: the new customers whose first recorded ad click was a Meta ad, on every plan, the free Mirror plan included.

Sources

See what Meta ads bring when Meta cannot see the sale

HonestTag counts the new customers whose first ad click was Meta from your own Shopify orders, and the free Mirror plan sets Meta's claimed conversions beside them.

  • Feed your ads a clean signal. On paid plans, the platforms you send to get each verified purchase, new customers marked as new once confirmed.
  • Catch the sales your pixels miss. On paid plans, purchases are sent from your Shopify orders, server to server.
  • Know what to scale. From the Truth plan, a weekly scale, hold or cut call when the data supports one, and on every paid plan, proof behind every attributed order.
  • Start free. The free Mirror plan puts Google Ads and Meta claims beside your orders. Keep your current tracking while you look.

Install HonestTag free