Why Meta stops seeing your conversions.

Your ads are running. Your forms are filling. But Meta is missing the leads. Watch how a data sharing restriction breaks that connection.

A telehealth example, from the first ad click to Events Manager.
Start 7-day trialGet a free consultation

Payment method required · one trial per domain · 7 days to cancel · 30-day money-back guarantee

See what changes before an event reaches Meta.

Follow a sample Lead or Purchase through Crisper’s recovery layer. See which details are removed, how contact details are hashed, and what is sent to Meta.

Capture

A Lead fires on the clinic's own domain.

Captured on a subdomain of the domain Meta restricted. No new domain, no pixel reset.

Captured on your domain

What Meta receives

Not sent yet
  • eventLead
  • emailpriya@example.com
  • phone+1 415 555 0132
  • namePriya Shah
  • items[{ name: "Detox program" }]
  • messageI need help with…

Why Meta restricts your website

Meta reads every event it receives. When the details describe someone’s health, it classifies your whole domain and limits what it accepts from it. Your ads keep running, so it’s easy to miss.

1 · Your events

Each event describes a patient.

A Lead names the program they asked about. A Purchase says what they bought and what they paid. With the ad click and their matched account, that is health information about one person.

  • content_nameGLP-1 Weight-Loss Program
  • content_categoryweight_loss
  • value199.00 USD
  • fbcfb.1.1728…IwAR2x

2 · Meta’s classifier

Your domain gets a health category.

Meta’s AI reads event details and page addresses, then files the domain under a category such as Health & Wellness. For a clinic, sharing a patient’s health information with an ad platform can be a HIPAA violation, so Meta restricts the data instead of taking the risk.

  • CategoryHealth & Wellness
  • Data sharingRestricted

3 · Ads Manager

Ads approved. Conversions blocked.

Ad review and domain classification are separate systems. Your ads can pass review and keep delivering while Lead and Purchase are cut off, so Meta optimizes for leads and sales it never sees.

  • Ad reviewApproved
  • DeliveryActive
  • LeadBlocked
  • PurchaseBlocked
Meta’s explanation of source categories

Why the usual fixes don't work.

Meta puts the restriction on your website, not on the pixel or the ad account. Anything that keeps the same website runs into the same block.

Standard Meta pixel

The browser sends the event from the restricted website, so Meta blocks it.

Conversions API setup

A server sends the same event for the same website. Meta gets it and still can't use it.

New pixel

The restriction is on the website, so a new pixel gets it too.

New ad account

Same website, same restriction.

New domain

You rebuild the site, and Meta usually restricts it again.

Meta appeal

It can take weeks, and it rarely works.

Custom event

A new name doesn't change the website it comes from.

Instant Forms or Traffic

You get form fills or clicks, but the website's Lead stays blocked.

What works instead: Crisper's recovery layer.

It prepares each event before it reaches Meta. The standard name stays, the restricted details are removed, and match keys are added. Same website, same pixel, same ad account.

See how it works

How deep is your restriction?

Tap the one that matches Events Manager. Then switch Crisper on.

What Meta receives

One clinic visit · Level 2, Standard event

One or more websites are in categories with data sharing restrictions. Certain standard events are blocked. (recreated)

  • PageVieweventArrives
  • URL path and queryafter the domainStripped
  • Custom parameterscustom_dataStripped
  • LeadeventBlocked
  • ScheduleeventBlocked

Lead and Purchase usable for optimisation

0/2

Crisper recovers Lead and Purchase at every depth. Including full domain, where even PageView stops.

Same domain, same pixel, same ad account. Region-scoped blocks, where events “may be blocked when visitors are in the European Region”, are covered too.

1. Core Setup

Meta ignores everything after your domain in a page address, and the extra details you send with each event.

“Restricts the sharing of custom parameters and parts of URLs following the domain.”
Meta Business Help Center
Purchase event, before and after
BeforeSent to Meta

  • event_name

    PurchasePurchase

  • content_ids

    ["glp1-kit", "pen-needles"]removed

  • contents

    [{ id: "glp1-kit", quantity: 1 }]removed

  • value

    249.00249.00

  • currency

    USDUSD

  • fbc

    fb.1.1728…IwAR2xfb.1.1728…IwAR2x

Illustration. Sample values.

What breaks

  • Custom conversions and audiences built on page URLs stop matching.
  • Product details like content_ids and contents get blocked.
  • Events Manager diagnostics can flag “Event parameters blocked”.

What we do

  • contents, content_ids and content_name are removed before the event leaves.
  • value and currency stay, so a Purchase keeps its revenue.
  • Form free text, like a reason for visit, is never mapped into the event.
  • The ad click ID stays with the event, so Meta can still credit the ad.

2. Standard event

Meta blocks the events that matter most, like Lead, Schedule and CompleteRegistration. Your ads can't learn from them anymore.

“Restricts the sharing of specific mid and lower funnel events.”
Meta Business Help Center
What Meta does with each event
EventBeforeWith Crisper
  • LeadSuppressedReceived
  • ScheduleSuppressedReceived
  • PurchaseSuppressedReceived

Illustration. Sample values.

What breaks

  • Meta drops the event: “You are attempting to send a restricted event. The event was suppressed.”
  • Ad sets can't optimize for leads, so they sit in learning limited. Meta wants about 50 conversions a week per ad set.
  • Renaming Lead to a custom event gives Meta a brand-new event with no history to learn from.

What we do

  • The event keeps its standard name. Lead stays Lead and Purchase stays Purchase.
  • It reaches Meta as one event with one event_id, so the browser and server copies count once.
  • Same pixel and same ad account. Nothing to rebuild in Ads Manager.
  • It shows in Events Manager within about 30 minutes of a correct install.

3. Full domain

Meta takes nothing from your website. Not even a page view.

“Fully restrict the sharing of all events in specific regions or all regions.”
Meta Business Help Center
Events reaching Meta
EventBeforeWith Crisper
  • PageViewBlockedReceived
  • ViewContentBlockedReceived
  • LeadBlockedReceived
  • PurchaseBlockedReceived

Illustration. Sample values.

What breaks

  • PageView, ViewContent, Lead and Purchase all stop.
  • Website audiences stop filling, and retargeting goes with them.
  • It can apply worldwide, or only to visitors in some regions, such as the European Region.

What we do

  • PageView, Lead and Purchase show in Events Manager again, with the ad click ID.
  • Every other standard event is covered the same way.
  • Region-only restrictions are covered too, from the same website.

380 Lead and 125 Purchase events

recorded through Crisper in one week across 18 restricted health and wellness sites, from dental implant clinics to treatment centers. Crisper's count, 7 October 2026.

Their conversions are counting again.

Meta restricted their domains. Hear how they got tracking back and what changed for their businesses.

Scaled AI

“An extension of me, my company, and my team.”

Mitchell PriceFounder, Scaled AI

10+ treatment-center domains recovered

See how tracking was recovered

Yatra Kundalini

“The [ROAS] came back up, my revenue also … we can manage ads just like before.”

Céline BergaminiFounder, Yatra Kundalini Activation

Days to get purchase tracking back

See how tracking was recovered

Try it on your domain for 7 days.

We set up the first one with you on a call, and we keep working with you until it is fixed.

Start 7-day trialGet a free consultation

Payment method required · one trial per domain · 7 days to cancel · 30-day money-back guarantee

We also help Meta match every event.

A recovered event only helps if Meta can tie it to a person and to the ad they clicked. Every recovered event carries more for Meta to match on, built into every domain.

Match keys on one Lead

Pixel on its own

2

  • em
  • fn

With Crisper

8

  • em
  • fn
  • ph
  • ct
  • zp
  • country
  • fbc
  • fbp
  • From the form
  • From an earlier visit
  • Added on our server
  • Kept from the ad click

Every key is SHA-256 hashed on our server before it leaves. Sample values.

Find the person

More ways for Meta to recognize who converted.

  • Location

    Your form doesn't ask for an address.

    We add city, zip and country to every event.

    ct · zp · country

  • Returning visitors

    Later events don't include the visitor's details.

    Details they gave on an earlier visit are added to later events.

    em · ph

  • Contact details

    Contact details can't go to Meta as plain text.

    We hash email, phone and name on our server, the way Meta requires.

    SHA-256

Credit the ad

Keep the link between the click and the conversion.

  • Ad click ID

    Meta loses track of which ad brought the lead.

    The click ID stays with the event, so Meta can credit the right ad.

    fbc · fbp

  • Safari

    Safari deletes ad click cookies.

    When the visitor comes back, we restore them.

  • Ad blockers

    Ad blockers stop tracking scripts.

    Tracking loads from your own subdomain, so ad blockers stop it less often.

Check every event yourself.

Meta's Events Manager shows the events it received. Your Crisper dashboard shows the rest for 10 days: what each event carried, and whether each platform took it.

Pulse

Healthy

Warns you on the dashboard when Leads or Purchases stop landing.

4 min
Last Lead
12
Today
63
This week

Resync

A delivery failed? Send it again with the same event ID, so Meta still counts it once.

  1. Lead · 10:09Failed
  2. Resynced, same event_id200 OK

DNS checks

We check your tracking subdomain for you and send reminder emails if it isn't set up yet.

  • DNS recordVerified
  • SSL certificateIssued
  • Checked from several regionsOK

Your part is three steps. We handle the rest.

Have three logins ready: your DNS, full control of the Facebook Business Manager, and your website. No Google Tag Manager needed.

Crisper/Setup/yourdomain.com

Setup 0:00

The sample runs on it. Nothing is sent.

    • Record added at your DNS provider
    • Crisper checks it from several regions
    • yourdomain.com verified
Sample run

How you'll know it worked

  1. 1Lead and Purchase show as received in Events Manager.
  2. 2The same events show in your Crisper log, with each platform's response.
  3. 3Your ad sets can optimize for Lead again. Expect a ramp: Meta wants about 50 conversions a week per ad set.

What runs behind those three steps

We set up your first domain with you on a call. This is what gets built when you add a domain.

Setup like this normally runs $1,500. On your first domain, it's included.

  • Your tracking subdomain, with its own SSL certificate
  • DNS checks from several regions, rechecked automatically
  • The recovery layer, configured for your domain
  • Your forms and checkout mapped to standard Lead and Purchase events
  • Email, phone and name hashed to Meta's format
  • One event ID on every event, so nothing counts twice
  • Location and returning-visitor details added to each event
  • Safari click-ID recovery and ad-blocker-resistant loading
  • A bot score on every request
  • The same event sent to every platform you connect: Meta, Google Ads, GA4, TikTok and more
  • Your CRM connected by webhook, if you use one
  • On your first domain, the first events checked in Events Manager with you on the call
  • A pulse on the site that flags when events stop

7-day free trial. 30-day money-back guarantee. We keep working with you until it is fixed.

Every domain after the first uses the same setup, under one account.

Questions owners ask about how it works.

What reaches Meta is a standard event for your existing pixel. Contact details are hashed on our server, the way Meta requires, and the details Meta restricts, like the product list and form free text, are removed before the event leaves. Crisper doesn't lift the restriction or change the category Meta assigned, so keep any category review running. No one can promise how Meta will treat an ad account, and we don't.

Here's what crosses. Meta receives a standard event (Lead or Purchase), an event id, the ad click id, and match keys (email, phone, name) SHA-256 hashed on the server, which is the format Meta requires. Hashing is a transport format, not anonymisation: regulators treat hashed identifiers from a patient form as identifiable, so whether you may send them is a question for your counsel. Form free text, reason for visit, and treatment details aren't mapped into the event, and Crisper doesn't re-inject the URL paths or custom parameters Meta strips on restricted domains. Crisper is not a substitute for your HIPAA program — covered-entity status, patient authorization, and BAA needs sit with you and your counsel. Bring your compliance contact to the setup call and we walk through the field map.

You can appeal while we work on recovery. Appeals rarely restore usable optimization events. Recover Lead and Purchase now so ad sets aren't stuck in learning limited while the appeal runs.

Once Lead and Purchase are usable again, Meta still needs optimization volume (~50 events / 7 days per ad set to stay healthy). Delivery improves as learning limited clears — expect a ramp, not an instant ROAS reset on day one.

Your subscription includes a 30-day money-back guarantee. We keep working with you until it is fixed. You can also cancel any time in the 7-day trial.

Usually not. Every trial includes a setup call on your first domain, and we set it up with you. If a developer or agency holds your DNS or website login, ask them for access before the call, or bring them to it.

The core recovery path is Meta Lead and Purchase after a data sharing restriction. Google Ads and GA4 stay connected as integrations; they aren't the restriction problem this offer solves.

We recover the events your ads need.

Usable Lead and Purchase events, on your existing domain. Same pixel, same ad account. We keep working with you until they're usable.

Meta

The restriction and ad learning

Meta controls the domain category and restriction. Recovering events doesn't lift the restriction or guarantee immediate ad performance.

You or your agency

Campaigns and creative

You keep managing the ad account, budget and creative. Crisper handles conversion recovery.

You and your counsel

Compliance decisions

You handle patient authorization, HIPAA obligations and any BAA requirements. Crisper doesn't replace your compliance program.

Your event data. Standard events stay standard. Form free text, reasons for a visit and treatment details are never mapped into the Meta event.

Set up in about 5 minutes. Events in Events Manager within about 30.

~5 min setupwithin ~30 min
Setting up
  • 7-day free trialon every eligible domain, one per domain
  • $297/moper subdomain
  • We set up the first domain with youfounder included
  • 30-day money-back guaranteeand cancel any time in the trial
  • We keep working with youuntil it is fixed
Start 7-day trialGet a free consultation

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.