Skip to main content
Ad Account Rescue

The Meta Pixel says "You are attempting to send an unverified event"

The notice
You are attempting to send an unverified event. The event was suppressed. Go to Events Manager to learn more.
On this page

Your pixel fired a custom event that nobody at your business has confirmed in Events Manager, so it was not sent. Meta says "When you share a new custom event with Meta, you need to review it in Meta Events Manager." If your dataset has any data restriction, such as a Health and wellness category, custom events are "automatically blocked until you review and confirm them". Open the dataset's Settings, go to Manage event blocking under Data controls, and confirm the event only if its name and data carry no health information. If Meta blocked it for you, request one review. Don't rename it and send it again.

Curve Compliance helps health businesses send conversion events Meta can use. Curve's team replaces browser pixels with HIPAA-compliant, server-side conversion tracking, sends events under neutral event names, detects PHI-like patterns before data reaches Meta, and hashes identifiers with SHA-256 to Meta's requirements. It is typically live in about a week, with a BAA signed on every plan. Book a call with Curve.

Why the pixel suppressed the event

Custom events are the ones you name yourself, sent from the pixel with fbq('trackCustom'). Meta treats each new one as unconfirmed until someone reviews it: "Custom website, app and offline events need to be reviewed in Meta Events Manager." Standard events such as Lead or Purchase are not part of this review.

Meta may also block custom events on its own. "Meta may also block new and existing custom events, if we detect they may contain potentially prohibited information (e.g., health, financial) not allowed under Meta's terms." In both cases the result is the same: "You can't use blocked custom events with ads features."

Confirm or block: how to decide

Meta asks you to confirm a custom event only if all three of these are true:

  • "Your custom event 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 the custom event to Meta, and want to continue to share the event."
  • "You have correctly formatted your custom event data."

How to review the event

You need full control of the business asset to do this. On a health website, the event name itself can carry health information, so check it before you confirm. Meta says you are "in the best position to ensure your integration does not share prohibited information to Meta, including custom event names."

  1. Go to Meta Events Manager and click Datasets in the left menu.
  2. Select your dataset and click the Settings tab.
  3. Scroll to Data controls and click Review in the Manage event blocking section.
  4. In the Action required tab, select the custom events to confirm or block, then click Next.
  5. Choose Confirm the custom event or Block the custom event, click Review, then Done.
  6. Fire the event again from your site and check that it now appears in Events Manager.

If Meta blocked the event

An event Meta detected and blocked sits in the Blocked tab, and you may not be able to confirm it. If you think the block is a mistake, select the event, click View details and select Request review. Use that request carefully: if the review is not approved, "the custom event will remain blocked and cannot be used with ads features. You won't be able to request another review." Fix the event's name and parameters first.

Don't rename it and send it again

Sending the same event under a new name to get past the review sends the same information again, and Meta names custom event names among the things you are responsible for. Fix what the event carries, or leave it blocked. Why Meta blocked your custom events covers the queue that appears when a whole dataset is restricted, and a custom conversion flagged for health information covers the conversions built on top of these events.

Talk to Curve

A suppressed event means the tracking on your site is sending Meta something it can't use. Curve's team sets up HIPAA-compliant, server-side conversion tracking in place of browser pixels, with neutral event names, PHI-like pattern detection before data reaches Meta, SHA-256 hashing to each platform's requirements, and attribution kept through booking tools such as IntakeQ, Calendly and Jane. It is typically live in about a week, with a BAA signed on every plan, so book a call with Curve.

How Curve helps

  • Replaces browser pixels with HIPAA-compliant, server-side conversion tracking to Meta Conversions API, Google Ads and TikTok.
  • Sends events under neutral event names and detects PHI-like patterns before data reaches Meta.
  • Hashes identifiers with SHA-256 to each platform's requirements, and includes consent management.
  • Keeps attribution through booking tools such as IntakeQ, Calendly and Jane.
  • Signs a BAA on every plan, with setup done for you by Curve's team, typically live in about a week.

Frequently asked questions

What does "You are attempting to send an unverified event" mean?

The pixel tried to send a custom event that hasn't been confirmed in Events Manager, so the event was not sent. Review it under Manage event blocking in your dataset's settings.

Do standard events like Lead or Purchase need this review?

No. Meta says you don't need to review standard events in this process. Standard events can be limited in other ways when your data source is in a restricted category.

Can we rename the event and send it again?

Not to get past the review. The new name goes into the same review, and Meta holds you responsible for what custom event names and parameters carry. Fix the event's data or keep it blocked.

Does sending the event server-side avoid the review?

No. Meta's review covers custom website, app and offline events in your dataset, and events sent through the Conversions API land in the same dataset as pixel events.

How does Curve help with custom events on Meta?

Curve's team sets up HIPAA-compliant, server-side conversion tracking with neutral event names and PHI-like pattern detection, and signs a BAA on every plan. 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