All resources

Agency enablement

Pitch Meta restrictions. Close Recovery.

Reusable framework for discovery calls, clinic explainers, and closing restricted lead-gen Meta recovery. Live client pay link so the clinic funds Stripe while you keep the org.

The dual dialect

Agency dialect

Zero Lead / Schedule in Events Manager while CRM still moves. Core Setup or standard events blocked. Another pixel will not save the retainer.

Clinic dialect

Facebook is still charging your ads, but it stopped counting the leads and bookings. Front desk can be busy while Ads Manager looks dead.

How to use this template

  • Align partnersInternal alignment
  • Agency buyer callAgency opener + Discovery
  • Clinic on the callClinic dialect + analogy + pay-link
  • Business caseWaste, failed resets, retainer risk
  • PushbackObjection bridges

Primary CTA: Book a Call. Agency packaging (live): multi-site org + client pay link.

Crisper in 20 seconds

What it is
Server-side ad tracking for lead-gen advertisers hit by Meta data sharing restrictions (Core Setup / standard events / full domain).
What it does
Gets usable Lead / Schedule conversions counting in Meta again when Events Manager shows 0 leads while the phone, forms, or CRM still move.
What it is not
Ecommerce attribution. Generic analytics. A Meta policy bypass. A new-pixel reset.

Recovery $297/mo · Growth $597 · Scale $1,497

Internal alignment

Use when leadership says “too technical,” “niche,” or “we already do CAPI.”

Without a Plan A for Meta data sharing restrictions, we cannot defend performance on restricted lead-gen accounts. Another pixel on the same domain is not a strategy.

Position as diagnosis (Tracking Audit + call) → recovery (Crisper) → multi-site ops → client-paid packaging via pay link.

Clients already ask why Ads Manager is empty. This is a productized answer: recover usable conversions, bill the clinic via pay link, keep operating the roster.

Pitching agencies

Opener

You’re getting screenshots of zero Lead / Schedule while the client’s CRM still moves. If you’re on Core Setup or standard events blocked, another pixel won’t save the retainer. Let’s confirm restriction depth and get usable events back into Meta across the sites you run.
  1. Confirm symptom: 0 leads / suppressed events / restricted notice
  2. Name depth: Core Setup vs standard events vs full domain
  3. Inventory failed resets (pixel / account / domain / CAPI / appeal)
  4. Who pays today vs who should (pay link)
  5. Path: Book a Call → Recovery at list → setup → verify
  6. Expand roster only after site one is live

Pitching clinic clients

Opener

Facebook is still charging your ads, but it stopped counting the leads and bookings from those ads. Front desk can be busy while Ads Manager looks dead. Most people try a new pixel, new ad account, or new domain. That usually fails because the restriction is on how the website is allowed to share conversion data. We’re here to get those leads counting again.

Non-tech analogy

Imagine the ads keep running, but the cash register stopped printing receipts. The store is still selling. The report says zero. Meta restricted how your website shares conversion receipts. Changing the cash register brand (new pixel) on the same storefront often does nothing. We restore usable receipts so Meta can optimize again.

Discovery cheat sheet

Before pitching product, identify restriction depth, failed resets, and who pays.

Broken feedback loop

  • ~0 leads while phone or forms still move?
  • Notice: data sharing restrictions or suppressed event?
  • Which conversions matter: Lead, Schedule?

Failed resets

  • New pixel on the same domain?
  • New ad account that flagged again?
  • Basic CAPI / SST already installed?

Appeals

  • Review requested, waiting ~30 days?
  • Rejected before? Appeal in parallel. Plan A is counting again.

Who pays

  • Agency paying SaaS out of pocket?
  • How many restricted sites on the roster?
  • Who feels the wasted ad spend?

Create the business case

Angle A · Blind spend

You’re not buying a dashboard. You’re buying Meta counting leads again so you stop flying blind. $297 is cheaper than another blind week.

Angle B · Failed invoices

You’ve already paid for a new pixel, a new account, maybe a domain, and Events Manager is still empty. Another reset is the expensive wrong experiment when the restriction rides the domain.

Angle C · Retainer risk

One empty screenshot per client becomes a book-wide trust problem. Fix site one at Recovery list, prove usable events, then expand.

Pitch toolkit

Objection bridges

We already changed the pixel / account / domain.

Restriction often rides the domain. Another pixel on the same domain is why you’re still empty.

We’ll just appeal.

Appeal in parallel. Reviews reject; waits hit 30 days. Plan A is getting events counting while you wait.

We already did CAPI / SST.

Basic CAPI/SST often does not fix restriction depth. Same toolbox words, different job.

Why would the agency pay?

You shouldn’t. Client pays Stripe; you keep the org. Pay link is live for that.

Just give me a trial.

Trial isn’t live for this pitch path. A call diagnoses Core Setup vs standard events vs full domain first.

Is this a bypass hack?

No. Clean recovery and event setup for restricted lead-gen. Consent still applies.

Close

Outcome we’re buying: Meta counting leads and bookings again after a data sharing restriction. Recovery at $297/mo list. Next step: Book a Call → client pay link → verify events are actually usable.
More resources

Go live with fixed tracking in 5 minutes

And reveal your store's full potential with reliable adblock-proof ad tracking.

Live setup and launch within 5 minutes
No coding required
Exceptional 24/7 support