Agency enablement
Objection card
Live bridges for “new pixel,” appeals, CAPI already done, and who should pay.
Desk card during the pitch
How to use this card
On every row: Objection → Say → Bridge. Enemy = Meta data sharing restrictions. Pay link live. Trial live. Formal guarantee not live.
1. “We don’t need this right now.”
Say
Every day Events Manager stays at zero while spend is live is another blind day. Restriction does not pause because the calendar is full.
Bridge
If Lead / Schedule stayed usable for the next 30 days, would you still wait — or is the dashboard already empty?
2. “We already changed the pixel / account / domain.”
Say
Restriction often rides the domain. Another pixel on the same domain is why you’re still empty.
Bridge
What still shows — zero leads, suppressed restricted events, or “Your data is restricted”?
3. “We’ll just appeal / request a review.”
Say
Appeal in parallel if you want. Reviews reject; waits hit 30 days. Health appeals feel like a lottery most people never win. Plan A is getting events counting while you wait.
Bridge
Are you willing to keep spending blind for a month on a review outcome you don’t control?
4. “We already did CAPI / server-side tagging.”
Say
Basic CAPI/SST often does not fix restriction depth. Same toolbox words, different job: restricted lead-gen recovery.
Bridge
After that install, did Lead / Schedule become usable for optimization — or only “configured”?
5. “Too expensive / What’s the coupon?”
Say
Recovery is $297/mo list. Compare to a blind week of spend or another failed freelancer reset. We don’t brand forever 90% off.
Bridge
Who feels the wasted spend — the agency or the clinic? (Then: send pay link.)
6. “Why would the agency pay?”
Say
You shouldn’t eat it. Client pays Stripe; you keep the org. Pay link is live for that.
Bridge
If the clinic funds the sub, are you ready to operate site one this week?
7. “Just give me a trial.”
Say
7-day trial is live — Start 7-day trial → /signup (card required). Use trial when the path is clear. Book a Call when Core Setup vs standard events vs full domain is fuzzy. Formal guarantee is not live.
Bridge
Clear enough for trial on site one this week — or thirty minutes first to name restriction depth?
8. “What if we’re still at 0 leads?”
Say
We care about Events Manager usable again, not a green checkmark. Call path diagnoses before the wrong invoice. Formal guarantee not live; honesty over theater.
Bridge
What does “working” mean for you — Lead usable, Schedule usable, or something else?
Pocket extras
| Objection | Say | Bridge |
|---|---|---|
| Need a developer? | Often no for common stacks; call walks messy cases. Not 24/7. | DIY after stack-check, or guided first? |
| Break Google / GA4? | Scope is Meta recovery; GA4 / Google Ads are live connections. | What’s still working that we must not treat as disposable? |
| Legal / bypass hack? | No policy-evasion pitch. Clean recovery; consent still applies. | Usable optimization events — or a story you can’t defend? |
| Isn’t this Hyros / ecommerce? | No. Lead-gen + data sharing restrictions only. | Wound = 0 Lead / Schedule under restriction? |
Close (after a bridge lands)
Outcome: Meta counting leads and bookings again after a data sharing restriction. Recovery $297/mo list. Next: trial /signup or Book a Call → client pay link → verify Lead / Schedule are actually usable.
Do not say
- “Guaranteed ROAS” / formal money-back as live — not live
- “This bypasses Meta” — compliance
- Gateway education as the product — wrong offer
- Invented testimonials or Stape ecommerce stats — not Crisper proof
Next step
Start Recovery when the path is clear. Book a Call when restriction depth is messy. Agencies: send the client pay link so the clinic funds Stripe while you keep the org.