Our domain is fully restricted and PageView stopped. What still works?

What does a full restriction mean in Events Manager?

It is the third and deepest of the restriction types on Meta's restriction page. Meta defines it as "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." Because the restriction covers all events, PageView stops too, not only Lead and Schedule.

The category attaches to the data source, such as a website, not to one pixel. A new pixel or ad account leaves the website where it was. Custom events do not help either. Meta says they are blocked until you review and confirm them, and may be unavailable under full restrictions. For the lighter tiers, read the restrictions guide and the Core Setup post.

What if the restriction applies only to some regions?

Meta says every restriction type "can be specific to certain countries or regions, or could be applied globally." A full restriction can therefore cover the whole world or a named list of places. Open the notice in Events Manager and write down the type, the regions it names and the date before you change anything. If the notice already confirms a full or regional restriction, skip to what still works.

A restriction can apply to a named country or region while the rest of the world still reaches Meta. That matters for agencies serving EU or UK clinics, where a notice can name a region. Your own notice states the scope, so read its exact wording rather than assuming it covers every visitor.

What does Meta suggest when everything is restricted?

Meta suggests running objectives that do not rely on data shared through its Business Tools: Awareness (for example reach and impressions), Engagement (likes, comments, shares) and Traffic (link clicks). Meta's objective guide describes each one. They do not rely on that data, so they also do not optimize toward a booked consultation.

If you think a category Meta assigned is wrong, ask Meta to review it from Events Manager, and Meta emails its decision. You cannot edit a category Meta assigned yourself. Run the review and a temporary campaign plan side by side, using the review and client conversation guide.

What still works when PageView has stopped?

Crisper recovers all standard events server-side at every restriction depth. That includes a full domain restriction where even PageView stops, and region-scoped blocking. Lead and Schedule can work again on the clinic's existing domain, with no pixel reset and no redirect landing page, as the recovery setup describes. Set that against Meta's own rule for this tier.

Meta Business Tools cannot be used for ads purposes where restrictions are in place.

Meta, Understand data sharing restrictions based on data source categories

That is Meta's rule for the tier, and it stays Meta's decision. Crisper does not change Meta's classification of a domain and does not win appeals. Meta also says: "you are ultimately responsible for your integration, your use of the Meta Business Tools, the data you share with Meta, and your compliance with our Meta Business Tool Terms." The clinic decides what it shares. Crisper does not map form free text, reason for visit or treatment details into the Meta event.

Setup still needs real access: 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. A received event can still be unusable for a campaign, so use the verification checklist to confirm it is available.

Scaled AI's treatment-center domains were restricted, and Events Manager showed zero Lead events while admissions inquiries kept arriving. Crisper recovered usable Lead events on those existing domains, with no new domain and no pixel reset. 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 case study does not name the restriction tier, so read it as proof of the setup, not of a full-restriction result. 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.

What should you do first?

1. Read the Events Manager notice. Record the restriction type, the regions it names and the date.
2. Ask Meta to review the category if you think it is wrong, and keep the appeal running.
3. Agree a temporary plan with the clinic using Awareness, Engagement or Traffic objectives.
4. If the notice confirms a full or region-scoped restriction, set up server-side recovery rather than another reset.

If your notice confirms a full or region-scoped restriction and the clinic still needs Lead and Schedule on its existing domain, we recommend Crisper to recover the standard events server-side. 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. After signup, verify DNS, connect the Meta integration and install the tracking snippets. Then run one test action and check in Events Manager that the Lead event appears and is available for your campaign.