Meta Conversions API setup for Framer
Framer sites usually have one pixel in the custom code slot, so duplication is rare. The common fault is a Lead event that never fires and a page view that only fires once.
Free30 minutesNo obligation
Framer + Meta CAPI · what breaks
What goes wrong on Framer
- 01
Forms submit without navigation
So URL-based conversion triggers never fire.
- 02
SPA route changes
Page views fire once per session and then stop.
- 03
No server code of your own
Framer hosts everything.
- 04
Custom code placement is constrained
Where and when your code runs is Framer's decision.
Framer + Meta CAPI · the fix
What changes — Framer + Meta CAPI
Conversions on real submission success
Bound to Framer's own state.
Route changes emitting page views
Explicitly.
Click IDs carried into submissions
Captured on first load.
Framer + Meta CAPI · architecture
How Meta tracking behaves on Framer
One pixel, one missing Lead event.
- 1
Pixel in the custom code slot
One place, so duplication is rare.
- 2
Lead bound to form success
The usual missing piece.
- 3
Page views on route change
Not just first load.
- 4
fbclid captured on first load
Into a hidden field.
- 5
Customer data from the submission
Normalized before hashing.
Framer + Meta CAPI · diagnose
Where Framer tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Submit a form and watch the URL
It won't change.
- 02
Navigate between pages and watch for events
One page view then silence is the SPA signature.
- 03
Check hidden fields have values
Not just that they exist.
- 04
Test the error state
A failure must not count.
- 05
Reconcile submissions against your CRM
For a closed month.
Framer + Meta CAPI · prove
The QA evidence — Framer + Meta CAPI
Run on Framer specifically, on a live conversion rather than in preview mode.
Source of truth
your form or CRM records
- Route changes confirmed emitting page views.
- Conversion confirmed firing on a real submission with no navigation.
- Hidden fields confirmed populated.
- Error state confirmed producing no conversion.
- Submissions reconciled against CRM records for a closed month.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Framer + Meta CAPI · free audit
What we check in the free audit
- Submit a form and watch the URL
- Navigate between pages and watch for events
- Check hidden fields have values
- Test the error state
- Reconcile submissions against your CRM
Checked against
your form or CRM records
Free30 minutesNo obligation
Framer + Meta CAPI · when not to buy
When you don't need this on Framer
Worth reading before you buy anything, from us or anyone.
- If your Framer conversions already fire on submission and route changes emit page views, the builder-specific problems don't apply.
- Both fixes are small pieces of custom code. If you have a developer, this is an hour.
- Server-side on Framer buys cookie durability and consent control, not a fix for the binding. Do the binding first.
- Reconcile against your CRM before assuming anything is wrong.
Framer + Meta CAPI · what we deliver
What gets built for Meta on Framer
A shared event ID on both paths
A lead ID generated at submission and written into both the event and your CRM record.
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
Written guarantee
95%+ tracking accuracy
Measured against your form or CRM records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Framer + Meta CAPI questions, answered
The Lead event was bound to a navigation that doesn't happen.
Capture fbclid on first load into a hidden field.
Only if you're losing events. Fix the Lead event and reconcile first.
A lead ID generated at submission, if you send a server event too.
Free · 30 min
Get Pixel and CAPI counting once on Framer
WhatsAppFree30 minutesNo obligation
