Meta blocked my custom events until I review them

Why every custom event was blocked at once

Meta's help center says it directly: "If your Meta 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, if your Meta Business Tools have full restrictions)." The trigger is the restriction on the dataset, not a problem Meta found in a particular event, which is why a harmless newsletter signup gets blocked too.

The restriction tier decides what review can achieve. Under core setup or a restriction on certain standard events, a custom event can be used again once you confirm it. Under a full restriction it may not be available at all, and confirming it will not change that. Check the tier on the dataset's data source category settings first. What each tier restricts is covered separately.

What is blocked and what still works

• Blocked: every custom event on the restricted dataset until it is confirmed. Meta says "You can't use blocked custom events with ads features", and lists those features as custom conversions, custom audiences, ad campaigns and lift studies.
• Not in the review: standard events. Meta says "You don't need to review standard events in this process." They still follow the dataset's tier, so a restricted Purchase or Schedule event stays restricted.
• Available again after confirmation: a confirmed custom event can be used with ads features, within whatever tier the dataset is in.

How to review them

1. Open Events Manager and find the custom events waiting for review. Meta's prohibited information article gives the path: the Data sources tab, then the dataset, then the events table, then the event.
2. For each event, read the name, every parameter it sends and the URLs of the pages it fires on. Curve Compliance's free website scan lists every pixel and tracker on a page. Ask one question: does any of it name, imply or depend on a condition, treatment, medication or test?
3. Confirm an event only when all of Meta's criteria hold. Its data, "including the event name and parameters, follows the Meta Business Tools Terms and doesn't include prohibited information". You "recognize and intended to share" it. It is correctly formatted.
4. Keep everything else blocked. An event you cannot vouch for is a liability, not lost signal. If an event is only useful because of the condition it points to, it should stay blocked.
5. If you believe Meta blocked an event in error, Meta says "you may be able to request a review from Events Manager or Ads Manager." Check the name, parameters and URLs before you ask, because the review looks at the same data.

Can I rename the event and send it again?

Not to get restricted data through. Meta's rule covers names and what sits behind them: "the names you choose and criteria you establish for your events, conversions, and Custom Audiences must not reflect, imply, or be based on any prohibited information." If an event called "Event 1" fires on the same weight loss intake page with the same parameters, it is still based on the same thing. The new name changes nothing that matters to that rule.

It also breaks a second rule. Where Meta has already detected and removed data from a stream, its troubleshooting article says: "You must not attempt to send data that has previously been detected and removed." Relabelling an event to resend the same data is exactly that.

Advice to use numbered or obfuscated custom events is common in e-commerce forums. It is written for online stores and treats Meta's filter as the only obstacle. Meta's own position is the opposite: "Meta's systems are not a substitute for your own compliance mechanisms."

Stop the next batch from needing review

Every new custom event on a restricted dataset joins the same queue, so the lasting fix is upstream. Decide which pages send events at all. Keep condition-bearing URLs, query strings and form contents out of what is sent. Server-side tracking through a HIPAA-compliant tool such as Curve Compliance sends each platform only a fixed list of fields and flags PHI-like patterns, such as condition names in URLs, before data reaches Meta, so they can be stopped at the source. Make sure a new custom event is not based on a condition in the first place, in its name or in the data behind it. Meta also says you "shouldn't send information about people from web pages where visitors may log in and provide potentially sensitive information, such as patient portals."

Related reading: what the prohibited information notice means, what still works under core setup and server-side tracking and Meta restrictions.

Talk to Curve

Every new custom event on a restricted dataset joins the same queue, so the lasting fix is in what your site sends. Curve's team will work out with you which events and fields your site sends today and set up HIPAA-compliant server-side tracking that keeps your campaigns optimizing, with a BAA signed on every plan. To get started, book a call with Curve.

Frequently asked questions

Sources

• Meta Business Help Center: About reviewing custom events in Meta Events Manager
• Meta Business Help Center: Understand data sharing restrictions based on data source categories
• Meta Business Help Center: About prohibited information
• Meta Business Help Center: Troubleshoot Meta Business Tools prohibited information notifications

Last verified September 28, 2026

Related pages

• Meta Removed Potentially Prohibited Information: Next StepsWhat Meta's prohibited information notice means for a health business, where to find what was removed, how to fix it, and why you must never re-send it.
• Meta Core Setup for Health Businesses: What Still WorksMeta core setup strips custom parameters and everything after the domain. What still works for a health business, why it happened, and what to fix first.
• Meta Restricted Purchase Events for Health and WellnessWhy Meta restricts Purchase and other lower-funnel events for health and wellness sites, what still works in each tier, and the compliant way back.
• Does Server-Side Tracking Get Around Health Restrictions?No. Meta restricts health data by data source, not by route, and forbids re-sending removed data. Here is what server-side tracking is really for.
• Meta Conversions Stopped: Restriction or Broken Tracking?Meta conversions dropped. How to tell a data restriction from broken tracking or a page change, event by event, and which layer to fix first.
• Meta Pixel Unverified Event Was Suppressed: What to DoMeta Pixel says your event is unverified and was suppressed? It is a custom event waiting for review in Events Manager. How to confirm it safely.
• Meta Restricted Standard Events: What You Can Still UseWhat Meta's standard-event and full restrictions stop, which events and objectives still work, and how to pick a new optimization event for a clinic.
• Data Sharing Restrictions Applied in Meta: What It MeansSaw "Data sharing restrictions applied" in Events Manager, or an email saying your site is in a category with restrictions? What it means and what to do.