How to request a review of a Meta data sharing restriction

Where do you request a data-source category review?

Meta's category-management instructions give the review path below. You need full control of the business portfolio or an admin role on the ad account that owns the dataset. This reviews a source category; a rejected ad or restricted ad account has a separate review process.

1. Open Events Manager and select Datasets in the left menu.
2. Select the dataset name and ID connected to the clinic website.
3. Open Settings, then Manage data source categories and Manage.
4. Inspect the domain, category and status. If Meta assigned an inaccurate category, open View Details and choose Request review.
5. Save the request confirmation. Reopen View details to inspect a pending review; Meta sends its decision by email.

If someone on your account assigned the category, Meta describes an Edit Category option under View details. Check which case applies before requesting review. The category-management section can be absent when sources are not in the relevant categories, so an absent button alone does not establish a tracking fault.

What should an agency collect before a review?

Collect the notice and the facts needed to explain the classification issue. This is a suggested preparation checklist, not a list of mandatory Meta submission fields.

1. Save the source ID, affected domain, exact category and review status.
2. Record the notice and its event or regional scope.
3. Identify the public pages that explain the business accurately.
4. Keep any support reference and the date of submission.
5. Record current event availability so you can compare it with the result.

Explain any classification error with accurate facts from the public website. Wanting conversion tracking restored is not evidence that a clinic is outside health and wellness. Use the conversion tracking audit checklist for campaign and redacted CRM evidence, and keep patient records out of the review pack.

Should campaigns keep running while the review is pending?

Decide with the clinic using the available events, qualified lead volume and spend. A pending review does not settle that budget decision.

Meta's published procedure says it emails the decision; it does not give an approval deadline. Set a client update date around evidence you can check, including review status, usable events and lead quality. Crisper can support Lead and Purchase recovery on the existing domain when that fits the diagnosed restriction. It does not decide or guarantee the category review. If the intended event is restricted while the review is pending, skip to recovering events during the wait.

How do you explain the restriction to the clinic?

Use the observed facts and an agreed next check. The following is suggested wording you can adapt, not a client testimonial.

"We found a data sharing restriction on the source connected to your website. Your CRM still records leads, but we need to check which of those events Meta can use. We will request review if the category is wrong and agree how to measure campaigns while it is pending. Our next update will cover the review status, event availability and lead quality."

If the restriction is not confirmed, say so. Zero results can have other causes, as the restriction diagnosis guide explains.

What should you verify after Meta responds?

Read the decision and check the affected event again. A category change and an event usable by the campaign are separate observations.

If someone proposes a reset while you wait, use the new-pixel decision table. Keep the campaign decision tied to the observed restriction and business outcome.

Can you recover events while the review is pending?

The review decides the category, and the campaign needs usable events before that decision arrives. A fix for the wait has to keep the standard Lead or Schedule event, keep the clinic's existing domain, and not depend on Meta's decision date. 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. Run the review and recover events while it is pending; one does not replace the other.

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.

Crisper does not win the review or change how Meta classifies the site, so keep the category facts accurate and the request going. The clinic stays responsible for what it shares with Meta.

If a confirmed restriction keeps the clinic's Lead or Schedule events unusable while the review is pending, we recommend Crisper to recover them on the existing domain rather than waiting on an email with no date. Keep the category facts accurate, and check permitted event use separately from the review decision. 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, 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 run one test action and check the intended event on the correct source; receipt and attributed ad results are separate checks. 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.