Meta data sharing restrictions applied: what it means and what to do

Why can clinic leads disappear from Meta while ads still run?

A website data restriction can affect conversion measurement while ads continue delivering. Meta's restriction guidance distinguishes limits on shared data from full restrictions, and explains that campaign changes depend on the scope applied to the source.

Ad approval, event receipt and attributed results answer different questions. An approved ad does not show that its website conversion event is available. A CRM lead does not establish that Meta received it or that the lead came from a Meta ad.

Where do you check Meta data sharing restrictions?

In Events Manager, select the clinic's dataset and open Settings. Meta's category-management instructions direct you to Manage data source categories, then Manage, where you can inspect sources, categories and statuses. The section may be absent when your sources are not in the relevant categories.

1. Confirm the source name and ID against the pixel or server integration on the live website.
2. Open Settings and look for data source categories or data restrictions. Record the domain and the exact notice.
3. Check the affected events, any geographic scope shown, and the date activity changed.
4. Compare the event list with the campaign optimization event. Keep Lead and Schedule separate if both are used.

The capture below is an existing Help Center artifact from 1 October 2026. It illustrates the category definition at that date. It does not show the restriction on your client's account or a recovered event.

What changes under Core Setup, event restrictions and full restrictions?

Meta identifies three restriction types, and more than one can apply to a source. Read the domain, affected events and regional scope on your notice. A health and wellness category does not establish which of these restrictions your account has. If your notice already names the Lead or Schedule event you use, skip to what recovers it.

Meta's Core Setup definition covers custom parameters and URL details after the domain. Check restrictions on standard events separately. Meta also requires review of custom events shared by a tool with restrictions; full restrictions may make them unavailable. The custom event guide covers whether renaming Lead helps.

You may see labels such as Other, Condition or Provider. Record the exact label and its accompanying notice. Do not infer a fixed list of blocked events from the label or treat a vendor's numbered tiers as the wording Meta displays.

Does zero in Events Manager prove a restriction?

No. Zero events can also reflect the wrong source, a tag that does not fire, consent behavior, a broken form trigger or a reporting-period mismatch. Those are checks to run, not diagnoses to assign from a screenshot.

Use the same date range and note the time zone on each screen. A booked appointment and a form submission may be different actions on different days. CRM totals include leads from other channels unless you have evidence identifying their source.

What can an agency do while website conversions are restricted?

Review the campaign objective and available events before choosing a temporary plan. For certain standard-event restrictions, Meta recommends evaluating available alternative events. For full restrictions, it suggests objectives that do not depend on Business Tools data, including Awareness, Engagement and Traffic. Those changes do not establish that website conversion tracking has recovered.

For a clinic, assess form content and data handling with its privacy contact before changing lead collection. Track lead quality and bookings in the clinic's records. Avoid promising a performance improvement or changing the objective solely to remove a warning.

If the category seems wrong, use the data-source review checklist. If someone proposes reinstalling everything, check whether a new pixel addresses the failure first.

What evidence should you gather before changing tracking?

Gather the source notice, campaign settings and a redacted business record for the same period. The conversion tracking audit checklist explains what each artifact can establish.

What recovers Lead and Schedule once the restriction is confirmed?

When the notice covers the event your campaign optimizes for, a fix has to make that standard Lead or Schedule event usable again on the clinic's own domain. Renaming the event or switching the campaign objective leaves the standard event as it was. 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.

Scaled AI runs Meta lead-gen for addiction treatment and behavioral health centers. It has 10+ treatment-center domains recovered on Crisper, with usable Lead events on the same restricted domains. The Scaled AI case study shows the setup and the result in its own words.

A wrong source, broken trigger or traffic allow-list error still needs its own repair first. Crisper does not win Meta appeals or change how Meta classifies the site, and the clinic stays responsible for what it shares with Meta.

If a confirmed restriction is what stops the clinic's Lead or Schedule events, we recommend Crisper to recover usable events on the domain the clinic already has. 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. Once tracking is installed and events fire, they can appear in Events Manager within about 30 minutes. Then trigger one test enquiry and look for the intended event on the correct source. Receipt and attributed ad results still need separate checks.