Skip to main content
Ad Account Rescue

Meta restricted my purchase events because my business is health and wellness

On this page

Meta has placed your website or app in its Health and wellness data source category, and that category carries data sharing restrictions. The category is assigned to the data source as a whole, based on its topics and the products or services it offers, so it is not a pixel fault or one bad event. If Purchase is restricted, you are in one of two tiers: "Restriction on certain standard events", which Meta says "Restricts the sharing of specific mid and lower funnel events", or full restriction. You can't send Purchase under another name. You can move campaigns to events and objectives Meta still accepts, and request a review only if the category is genuinely wrong.

Curve Compliance helps you keep campaigns optimizing inside your tier. Curve's team reviews what your website sends to Meta, Google and TikTok with you, then rebuilds your conversion tracking so it is HIPAA-compliant and optimizes on the events Meta still accepts, while attribution holds through booking tools such as IntakeQ, Calendly and Jane, so your own reporting still shows booked appointments. A BAA is signed on every plan. Book a call with Curve.

Why Meta restricted your purchase events

Meta defines Health and wellness as a data source that "Is associated with medical conditions or specific health statuses, provider/patient relationships, services for accessing personal health information, or health-related products and services". Its own examples include "a patient portal, wellness tracker, telemedicine platform, pharmacy, health insurance marketplace, or condition-specific support group".

A clinic, telehealth provider or pharmacy fits that definition. So the useful question is usually not how to get Purchase back. It is which tier you are in, where it applies, and what you can still optimize for. Meta says it tells you about a restriction "via email and notifications in Meta Events Manager".

Find which tier you are in

Meta describes three tiers:

  • "Core Setup: Restricts the sharing of custom parameters and parts of URLs following the domain."
  • "Restriction on certain standard events: Restricts the sharing of specific mid and lower funnel events."
  • "Full restrictions: Fully restrict the sharing of all events in specific regions or all regions. In these circumstances, Meta Business Tools cannot be used for ads purposes where restrictions are in place."
  1. Open Meta Events Manager and click Datasets in the left menu.
  2. Select your dataset and open the Settings tab.
  3. Scroll to Manage data source categories and click Manage.
  4. For each data source, note the category, whether you or Meta assigned it, and its status.
  5. Screenshot what you see and keep Meta's email. You will want both if you request a review later.

What still works in each tier

Every tier also affects custom events. Meta says that with data restrictions, "custom events are automatically blocked until you review and confirm them". See why Meta blocked your custom events.

  • Core setup: Meta says "most campaigns should continue to run as expected". Standard events still flow, while custom parameters and URL paths do not. The details are on what core setup still allows.
  • Restriction on certain standard events: Meta suggests you "consider leveraging more upper-funnel events to maintain effective audience targeting and campaign optimization". Check which events are restricted, and pick an optimization event from the ones that remain.
  • Full restriction: Meta points to objectives that don't rely on data from its Business Tools, such as Awareness, Engagement and Traffic.

The compliant way back

For one vertical worked through end to end, see why peptide therapy conversions stop arriving.

  1. If Meta assigned the category and your business genuinely falls outside its definition, request a review from View details. Read how the category review works, and when not to use it first.
  2. If the category fits, change the optimization event or the campaign objective to one Meta still accepts in your tier.
  3. Fix what the site sends. Condition names in URLs, UTM values, parameters and custom event names can trigger prohibited information notices, and repeat notices are one route into core setup.
  4. Measure booked appointments and purchases in your own reporting, so budget decisions don't depend on the events Meta no longer receives.

What not to do

  • Don't re-send the restricted event as a custom event with a new name. Meta says event, conversion and audience names "must not reflect, imply, or be based on any prohibited information", and "You must not attempt to send data that has previously been detected and removed."
  • Don't try to self-categorize your way out. Meta says "you will not be able to modify a Meta-assigned categorization for your data source."
  • Don't open a new dataset, pixel, domain, ad account, Page or Business Manager to escape the category. See whether to open a new ad account after a restriction.
  • Don't expect server-side delivery to lift it. The category follows the data source and the business, not the way events travel. See why server-side tracking doesn't lift a restriction.

Talk to Curve

A restricted Purchase event doesn't have to leave you guessing. Curve's team will review what your site sends to Meta and the other platforms with you and set up HIPAA-compliant conversion tracking that keeps your campaigns optimizing on the events Meta still accepts, with booked appointments still visible in your own reporting. To get started, book a call with Curve.

How Curve helps

  • Curve's team reviews what your website sends to Meta, Google and TikTok with you.
  • Curve rebuilds your conversion tracking so it is HIPAA-compliant and keeps your campaigns optimizing on the events Meta still accepts, sending conversions server-side to Meta Conversions API, Google Ads, TikTok, Microsoft and LinkedIn.
  • Curve keeps attribution through booking tools such as IntakeQ, Calendly and Jane, so booked patients are credited to the channel that sent them.
  • Personal identifiers are SHA-256 hashed as the ad platforms' APIs require.
  • Curve signs a BAA on every plan.

Frequently asked questions

Can I get Purchase back by sending it through the Conversions API?

No. The restriction applies to the data source and its category, not to how events travel, so server-side events land under the same limits.

Can I rename Purchase to a custom event?

No. Custom events are blocked until you review and confirm them, and Meta says names must not "reflect, imply, or be based on any prohibited information". Renaming an event to get restricted data through is a workaround, not a fix.

Does the restriction apply everywhere?

Not always. Meta says restrictions "can be specific to certain countries or regions, or they could be applied globally", so check the status of each data source in Events Manager.

Will my ads stop running?

Under core setup, Meta says most campaigns should continue to run as expected. Under the standard-event tier, campaigns that optimize for a restricted event need an event Meta still accepts. Under full restriction, Meta Business Tools can't be used for ads purposes where the restriction applies.

How can Curve help if Purchase is restricted?

Curve rebuilds your conversion tracking so it is HIPAA-compliant and keeps your campaigns optimizing on the events Meta still accepts. Attribution holds through booking tools such as IntakeQ, Calendly and Jane, so your own reporting still shows booked appointments. Book a call with Curve.

Sources

Last verified

Talk to Curve about the data side of your restriction

Book a call and Curve's team will look at what your site sends to Meta, Google and TikTok, and show you the compliant setup that keeps your campaigns optimizing.

Book a call