Server-side tracking for ClickFunnels 2.0
The right server-side source on ClickFunnels is the payment processor, not ClickFunnels itself. One event per charge, keyed on the transaction ID, sent from the processor's webhook. That's immune to declined upsells still loading a page and to customers who refresh anything.
Free30 minutesNo obligation
ClickFunnels 2.0 server-side · 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 server-side · the fix
What changes — ClickFunnels 2.0 server-side
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 server-side · architecture
What ClickFunnels 2.0 exposes to a server container
Source from the processor and the funnel's branching stops mattering.
- 1
Events from the payment processor's webhook
One per charge, regardless of which pages loaded.
- 2
Transaction ID as the deduplication key
Not the funnel step.
- 3
Every branch mapped before building
Accept, decline, downsell, bump.
- 4
Refunds from the processor
Which ClickFunnels itself won't tell you about.
- 5
Click IDs captured at the opt-in
And carried to the processor's metadata where supported.
ClickFunnels 2.0 server-side · 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 server-side · prove
The QA evidence — ClickFunnels 2.0 server-side
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 server-side · 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 server-side · 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 server-side · what we deliver
What the server-side build gives you on ClickFunnels 2.0
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from processor charges
The payment processor's charge webhook, which fires once per actual payment regardless of which funnel pages loaded.
Deduplicated at every destination
On a shared event ID, verified before any existing path is removed.
Consent enforced before dispatch
A denied destination receives nothing, verified by capture rather than configuration.
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 server-side questions, answered
The payment processor, not ClickFunnels. One event per charge, keyed on the transaction ID.
For money events, largely yes. Keep them for opt-ins and funnel steps.
The processor's transaction ID. The funnel step is not a stable key.
From the processor's refund webhook. ClickFunnels won't tell you about them.
Free · 30 min
Move ClickFunnels 2.0 events off the browser
WhatsAppFree30 minutesNo obligation
