We already set up CAPI or server-side tracking. Why is Lead still blocked?

Why does Events Manager show server events while Lead is still blocked?

Delivery and eligibility are separate checks. Delivery asks whether Meta received the request. Eligibility asks whether the data source may share that event for ads, and a restriction answers the second question. If your notice already names Lead, skip to what to do.

Meta's restriction policy says that when a data source sits in a restricted category, Meta may limit or fully restrict sharing event data "via the Meta Business Tools". Meta's list of Business Tools names the Meta Pixel and the Conversions API together. The policy ties the restriction to the data source, not to the tool that sends the event.

Meta's page on event count differences adds a second reason to distrust the overview. It says Events Manager shows events "potentially before discarding events for reasons such as duplication, data policies or regulations". It does not list which restricted events are discarded. Read it as a warning that a count in Events Manager does not settle whether Meta can use the event.

The same symptom appears in a Stape community thread from July 2025. A poster using Stape's CAPI Gateway said Events Manager listed events from the Conversions API, while the source carried the notice "certain standard events are blocked and your data source(s) are in a core setup." A community reply said that once Meta has blocked the pixel, the events "will not be processed by Meta" even through the gateway. That is one member's opinion, not a Meta or Stape statement. The poster later said every event was custom-named, so the thread shows the symptom and no refused Lead.

What do CAPI, Stape and server-side tagging change?

They change transport. The request starts on a server, it can carry its own match keys, and an event_id lets Meta deduplicate it against a browser event. They do not change the category Meta assigned to the data source.

That is why a new pixel keeps the same domain category and why a successful Conversions API response counts as delivery evidence, not proof of a usable Lead. A new container, a gateway or a renamed event changes the route in the same way. Under a restriction, Meta's custom event guidance says custom events are blocked until you review and confirm them, or may be unavailable.

How do you tell refused events from reporting lag?

Read the notice first. Meta says it informs you by email and in Events Manager when it limits a source, and a restriction can apply to certain countries or regions. Note which events and regions the notice names before you change anything.

Lag is the easiest to rule out. Meta's Test events page says data may take 30 minutes or more to appear in analytics after you set up an event. Wait that long, then compare. If a notice names Lead, you are in the first row whatever the server log says. Also check whether the ad set can still select Lead on that source, as the verification guide does in its campaign step.

What do you do when the restriction is confirmed?

Request a category review and keep working while it runs. In Events Manager, open the dataset's Settings tab, go to Manage data source categories, click View details, then Request review, as Meta's category guide describes. You need full control of the business portfolio or an admin role on the ad account that owns the dataset. Meta does not let you change a category it assigned, and the review guide covers the client conversation while you wait.

The setup you built is the delivery half, and it stays useful once the event is eligible. While the review is pending, Crisper recovers the standard event server-side on the clinic's existing domain, with no redirect landing page and no pixel reset. Crisper does not decide the review. How it sits next to your current container is a question for the setup call that comes with the first client domain.

Resets of the pixel, the ad account and the domain had already failed for Scaled AI, an agency that runs Meta lead-gen for addiction treatment and behavioral health centers. Its CRM kept receiving admissions inquiries while Events Manager showed zero Lead events. Crisper recovered usable Lead events server-side on the existing restricted domains. 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 shows the setup and the timeline.

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.

If Events Manager shows your server events arriving and the same source carries a confirmed restriction on Lead or Schedule, we recommend Crisper to recover usable conversions on the domain you already have. 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. Then verify DNS, connect the Meta integration and install the tracking snippets. Once tracking is installed and events fire, they can appear in Events Manager within about 30 minutes. Run one approved test action, then check in Events Manager that Lead appears on the intended source and that the ad set can select it. A server response alone cannot show either.