Meta data sharing restrictions applied: what it means and what to do
Read the exact Meta restriction notice, distinguish Core Setup from event limits, and choose category review, tracking repair or existing-domain recovery.
7 min read6 views
Eight things agencies see in a clinic's Meta tracking, and the guide that answers each one. Pick what you see, or type it.
yourclinic.com
Website pixel
DiagnosticsNo issues reported.
Touring 8 symptoms. Pick one to pin it.
Read the notice before touching the pixel.
Crisper gets your clients' Lead and Purchase events counting again after a data sharing restriction. No new domain, no pixel reset. A free 7-day trial on every eligible domain; we set up the first client domain with you on a call.
16 guides, most read first. Each one appears under at least one symptom above.
Read the exact Meta restriction notice, distinguish Core Setup from event limits, and choose category review, tracking repair or existing-domain recovery.
7 min read6 views
Facebook Ads Manager shows zero conversions? Check the report, event trigger, dataset, domain allow list and attribution before assuming a Meta restriction.
12 min read2 views
Find the source-category review procedure, check access, prepare accurate evidence and plan measurement while Meta reviews the category.
6 min read2 views
Check whether a new pixel repairs an installation fault or leaves the same domain restriction. Use the evidence to choose the next tracking step.
7 min read2 views
Send a Crisper pay link for the client website. The clinic pays the subscription, and your agency keeps managing the tracking.
6 min read1 view
Paste a prompt into your website coding agent to add an event your tracking does not detect automatically. Define the action, include available customer details and test the result.
9 min read0 views
Add Crisper to your AI agent with one command and click Allow. The agent adds your website and opens billing and ad-platform setup; you approve each step.
5 min read0 views
Server-side tracking changes how an event travels, not the category Meta assigned to the data source. Tell refused events from reporting lag, then choose a category review or recovery.
6 min read0 views
Meta documents event_source_url as required for website events sent through the Conversions API. Find the dataset that shows the warning and check the event URL your CRM sends.
6 min read0 views
A custom event is not a reliable stand-in for Lead when Meta restricts a clinic's data source. Check the event's review status, and recover the standard Lead event on the existing domain.
11 min read0 views
A full restriction covers all events, in named regions or everywhere. Read Meta's tiers and regional scope, run the objectives Meta suggests, and see what Crisper recovers.
6 min read0 views
Weigh Instant Forms, Traffic, Landing Page View and a CRM webhook while Lead is blocked. None repairs the website event, so recover Lead and Schedule on the existing domain.
8 min read0 views
Compare the same action, dates, source filters and attribution settings before treating a CRM and Meta reporting gap as broken tracking.
7 min read0 views
Check completed enquiries and bookings across Cal.com, GoHighLevel, Gravity Forms, Calendly and other tools. Verify success triggers, Meta receipt and duplicates.
9 min read0 views
Core Setup limits URL details and custom parameters. Check conversion rules, custom events and separate event restrictions before changing tracking.
9 min read0 views
Follow a completed action through collection, Meta receipt, duplicate handling and campaign availability. Record what each check proves before claiming recovery.
8 min read0 views
The next tracking checklist, restriction explainer, or Crisper walkthrough, by email. Free to subscribe.
Use your business email and first and last name. We email you when a new guide is published.
Free to subscribe
Payment method required at checkout. One trial per domain. The 30 minutes start once tracking is installed and events fire; it is visibility in Events Manager, not same-day ROAS.