Meta Conversions API setup for ClickFunnels 2.0
Meta on ClickFunnels needs one event per charge with the transaction ID as event_id. Funnels that fire Purchase on every step of the sequence produce three or four conversions for a single customer.
Free30 minutesNo obligation
ClickFunnels 2.0 + Meta CAPI · what breaks
What goes wrong on ClickFunnels 2.0
- 01
Upsell revenue missing or front end double-counted
Depending on where the purchase tag was placed.
- 02
Declines still load a page
A customer who declines the upsell still sees the downsell page, and a page-based tag counts the refusal.
- 03
Downsell branches never walked
Built and never tested, so nobody notices they fire nothing.
- 04
Average order value meaningless
Because charges and events don't correspond.
ClickFunnels 2.0 + Meta CAPI · the fix
What changes — ClickFunnels 2.0 + Meta CAPI
One event per charge
Front end, bump, upsell, downsell.
Declines counting nothing
Because the event is bound to a charge, not a page.
Real average order value
Charges and events finally corresponding.
ClickFunnels 2.0 + Meta CAPI · architecture
How Meta tracking behaves on ClickFunnels 2.0
One event per charge, keyed on the transaction.
- 1
Transaction ID as event_id
Unique per charge, stable across paths.
- 2
Purchase sent per charge
Front end, bump, upsell, downsell each their own.
- 3
Nothing bound to page views
The single change that fixes most ClickFunnels Meta data.
- 4
fbclid captured at the opt-in
The first step of the funnel, before anything else.
- 5
Refunds reversed from the processor
Not available from ClickFunnels.
ClickFunnels 2.0 + Meta CAPI · diagnose
Where ClickFunnels 2.0 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
Compare processor charges to platform purchases
Charges, not orders.
- 02
Map every branch on paper
Accept, decline, downsell, bump.
- 03
Walk each branch with a real transaction
Including the decline.
- 04
Check which steps have purchase code pasted
Usually more than one.
- 05
Look for repeated transaction IDs
Proof of double counting.
ClickFunnels 2.0 + Meta CAPI · prove
The QA evidence — ClickFunnels 2.0 + Meta CAPI
Run on ClickFunnels 2.0 specifically, on a live conversion rather than in preview mode.
Source of truth
your payment processor's charge records
- One event per charge confirmed, across every branch.
- No transaction ID appearing twice.
- Decline and downsell paths walked with real transactions.
- Charge count and value reconciled against the processor for a closed week.
- A real refund tested and confirmed reversing.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
ClickFunnels 2.0 + Meta CAPI · free audit
What we check in the free audit
- Compare processor charges to platform purchases
- Map every branch on paper
- Walk each branch with a real transaction
- Check which steps have purchase code pasted
- Look for repeated transaction IDs
Checked against
your payment processor's charge records
Free30 minutesNo obligation
ClickFunnels 2.0 + Meta CAPI · when not to buy
When you don't need this on ClickFunnels 2.0
Worth reading before you buy anything, from us or anyone.
- If your funnel is a single product with no bumps or upsells, one charge equals one order and none of this complexity applies.
- If your processor charges and platform purchases already reconcile, the multi-charge problem isn't affecting you.
- Removing the purchase tag from upsell pages is a five-minute change that fixes most of this. Do that before buying anything.
- The decline-path test costs nothing and finds the most embarrassing bugs. Run it yourself.
ClickFunnels 2.0 + Meta CAPI · what we deliver
What gets built for Meta on ClickFunnels 2.0
A shared event ID on both paths
The payment processor's transaction ID, unique per charge.
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 payment processor's charge 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
ClickFunnels 2.0 + Meta CAPI questions, answered
Purchase is firing on funnel page views rather than on charges. Four pages, four events, one customer.
The processor's transaction ID, one per charge.
Only if they're a separate charge. If they're part of the front-end transaction, include them in that value.
Bind the event to a charge. A declined upsell produces no charge, so it produces no event.
Free · 30 min
Get Pixel and CAPI counting once on ClickFunnels 2.0
WhatsAppFree30 minutesNo obligation
