Can a custom event replace Lead under Meta's health and wellness restriction?

Can a custom event replace Lead under a data sharing restriction?

Not reliably. Renaming Lead changes the label on an event, not the data source it leaves from, and Meta applies the restriction to the data source, meaning the website or app that shares data.

The tip is easy to find in forums: send the same action under a new name and optimize for that. Meta's own pages describe a different outcome. On a restricted source, custom events are held until someone confirms them, and some are blocked or unavailable. If you have not confirmed the restriction yet, start with the data sharing restrictions guide. If it is confirmed and Lead is the event you need, skip to what recovers Lead.

What does Meta's "Important update to custom events" email mean?

It is a notice, not a block, and the email itself says "There is no immediate action necessary on your part." The rule it announces is the one in this post: new custom events will be blocked "until you confirm that they are from your business and follow our Meta Business Tools terms."

The sentence is conditional. It applies "if data restrictions are turned on in your data source", so the email alone does not confirm a restriction. Check the dataset's Settings for its data source categories, and read the data sharing restrictions guide for what each one means.

It also covers new custom events only. The email says nothing about events you already confirmed. However, Meta's review instructions say Meta may block new and existing custom events when it detects potentially prohibited information, so a confirmed event is not safe for good. Meta has sent this wording since at least 2024, so it is not a new policy. What Meta does with these events comes next; to check yours now, skip to the review screen.

What does Meta do with custom events on a restricted source?

It treats them as events to review before use. Meta's page on reviewing custom events says that when a source has data restrictions, custom events are automatically blocked until you review and confirm them, or they may not be available, for example under full restrictions. You can use confirmed custom events with ads features. You can't use blocked ones.

You confirm an event only if its name and parameters follow the Business Tools Terms and leave out prohibited information. Meta's prohibited information page says the names you choose for events and conversions must not reflect, imply or be based on prohibited information, and health information is on that list. Meta can also block new and existing custom events itself when it detects potentially prohibited information, according to its review instructions.

Meta does point advertisers with standard event restrictions toward other events. Read plainly, that is advice to optimize for a different action. The page says nothing about sending the same enquiry under a new name.

Is a custom event as useful as Lead for optimization?

Meta does not describe it that way. Standard events are "actions with predefined names that Meta recognizes and supports across ad products." Custom events are actions the standard list does not cover, and Meta asks you to review a new one before it is used. Lead and Schedule are standard events.

Meta publishes no comparison of how well each type optimizes, and this post has no test of its own. Anything more specific is inference. The inference here is narrow. A campaign that optimizes for a custom event needs that event to be confirmed and usable, and Meta says you don't need to review standard events in that process.

One poster in a Stape community thread (November 2025) described the weaker-signal problem. After Purchase stopped firing, they sent a custom event through server-side GTM and the Conversions API. It showed in Events Manager for the browser but not as a server signal. When they switched the campaign goal to the custom event, they called the traffic and CPM "bots and quite garbage." A reply pointed out that the server trigger was set to Purchase while the event had another name, and told the poster to allow the custom event in Events Manager. It is one report, and a setup cause is plausible, so it shows what people try rather than what Meta does.

Other people report that a custom event worked. A January 2026 reply in the same thread says nondescript names usually go through for health and wellness. That is one practitioner's experience, with no rate behind it. Meta's rule is the one that applies: names must not reflect or imply prohibited information, and Meta can review events that are already sending. An event that arrives today still sits on a source Meta can look at again.

How do you check whether a custom event is blocked?

Open the review screen instead of reading the event count. You need full control of the business asset, and the path comes from Meta's review instructions.

1. Open Events Manager and click Datasets in the left menu, then select the dataset.
2. Open the Settings tab and scroll to Data controls.
3. In Manage event blocking, click Review.
4. Read the tabs: Action required for events waiting on you, Blocked, and Confirmed.

This post has no Events Manager capture of a blocked custom event, because a drawn mock would not be your account. Save your own dated screenshots of each tab. The audit checklist covers the rest of the evidence to collect.

What if Meta flagged one of your custom conversions?

Build a new custom conversion and move the campaign onto it, because a flagged one can't be repaired in place or swapped out of a published campaign. Meta flags a custom conversion when its name or criteria suggest information its terms don't allow, and its example is a specific health condition such as arthritis. You can't use a flagged custom conversion when creating new campaigns.

1. Open Events Manager, go to Custom conversions and read the flagged conversion's name, rules and source event.
2. If a rule depends on a condition, such as a page path named after a treatment, create a new custom conversion that counts the step itself. Meta lets you edit a custom conversion's name, description and value, but not its rules, so renaming changes the name and leaves the rule.
3. For each running campaign, duplicate it and select the unflagged conversion before publishing the copy. Once a campaign is published, Meta says you can't remove or swap its custom conversion.
4. Request a review only if the flag is wrong, from the campaigns table in Ads Manager or the custom conversions page in Events Manager.

A flag is a different problem from a URL rule that stopped matching under Core Setup, which the Core Setup guide covers. A new custom conversion also does nothing for a restricted standard event. If the Lead or Purchase event itself is the one you need, skip to what recovers Lead.

What recovers Lead itself?

If the action is a lead, the useful fix is getting the standard Lead event usable again, not finding it a new name. A fix has to keep the event name Meta recognizes, keep the clinic's existing domain, and not depend on Meta approving a custom label. Crisper recovers the standard event server-side on the clinic's existing domain, with no new domain, no redirect landing page and no pixel reset, as the recovery setup describes. A new source does not remove the category, as the pixel reset guide explains.

Scaled AI, which runs Meta lead-gen for addiction treatment and behavioral health centers, hit the gap this post is about. When Meta restricted its clients' domains, Events Manager showed zero Lead events while admissions inquiries kept arriving in the CRM, and resets of the pixel, account and domain had already failed. Crisper recovered the standard Lead event on the existing domains, with no new domain and no pixel reset, and the agency now runs its roster under one org. As of 7 October 2026, 12 of its restricted treatment-center domains are active on Crisper, and 10 of them recorded 207 Lead events through Crisper in the previous seven days. That is Crisper's own count of Lead events sent from the clinics' existing domains, so confirm your own in Events Manager. The Scaled AI case study has the timeline and a video from its founder.

Scaled AI is not the only case. As of 7 October 2026, 18 restricted health and wellness sites on Crisper, among them dental implant clinics in the US and Spain, an ear-care clinic in Ireland and a medical clinic in Hungary, recorded 380 Lead events and 125 Purchase events through Crisper in their previous seven days. Those are Crisper's own counts on the customers' existing domains, not Meta acceptance figures, with purchases and leads counted separately.

Crisper does not win Meta appeals or change how Meta classifies the site, so keep the appeal going in parallel with the review and client conversation guide. Keep each event faithful to the action, so a consult request is a Lead and a booked appointment is a Schedule. The clinic stays responsible for what it shares with Meta.

If your clinic's Lead or Schedule event is unusable under a confirmed restriction, we recommend Crisper to recover the standard event on your existing domain instead of renaming it and waiting on a review. Setup takes about 5 minutes when you have DNS access, access to the Meta integration and the ability to add the tracking snippets, and the founder sets up the first client domain with you. Start 7-day trial. A payment method is required, with one trial per domain and 7 days to cancel. 30-day money-back guarantee. We keep working with you until it is fixed. Verify DNS, connect the Meta integration and install the tracking snippets on the clinic's site. Once tracking is installed and events fire, they can appear in Events Manager within about 30 minutes. Then run one test action and confirm in Events Manager that the standard event arrives and is available to the campaign. Signup alone does not fix tracking, so treat that Events Manager check as the proof.