Server-side tracking for Thinkific
Thinkific's webhooks cover orders and enrolments, which is the route to recurring revenue. As with every hosted course platform, the click ID must live on the student record rather than in a cookie that won't survive to the next payment.
Free30 minutesNo obligation
Thinkific server-side · what breaks
What goes wrong on Thinkific
- 01
Subscriptions and payment plans
Revenue arriving after the checkout page is gone.
- 02
Site-level injection only
Enough for a pixel, not enough to see the payment flow.
- 03
Plan totals sent at checkout
Reporting uncollected money.
- 04
Refunds unreversed
Reported revenue only climbing.
Thinkific server-side · the fix
What changes — Thinkific server-side
Payments counted as they clear
Each one its own event.
Click ID on the student record
Surviving to later payments.
Refunds reversed
Net revenue reported.
Thinkific server-side · architecture
What Thinkific exposes to a server container
Webhooks for money, browser for funnel.
- 1
Order webhooks as the money event
One per payment, as it clears.
- 2
Click ID on the student record
Captured at the course page.
- 3
Amount charged per event
Never a plan total.
- 4
Refunds wired as reversals
The step nobody builds.
- 5
Container on your own subdomain
Receiving both paths.
Thinkific server-side · diagnose
Where Thinkific 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 Thinkific revenue to platform revenue
For a closed month.
- 02
Check what value checkout sends
Plan total or amount charged.
- 03
Confirm subscribed webhooks
Usually none.
- 04
Check click ID storage on students
Determines later attribution.
- 05
Test a refund
It rarely reverses.
Thinkific server-side · prove
The QA evidence — Thinkific server-side
Run on Thinkific specifically, on a live conversion rather than in preview mode.
Source of truth
your Thinkific order records
- Each payment confirmed arriving as its own event.
- Click ID present on a live student record.
- Values confirmed as amounts charged.
- Revenue reconciled against Thinkific for a closed month.
- 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.
Thinkific server-side · free audit
What we check in the free audit
- Compare Thinkific revenue to platform revenue
- Check what value checkout sends
- Confirm subscribed webhooks
- Check click ID storage on students
- Test a refund
Checked against
your Thinkific order records
Free30 minutesNo obligation
Thinkific server-side · when not to buy
When you don't need this on Thinkific
Worth reading before you buy anything, from us or anyone.
- One-time course sales with no plans or subscriptions: the checkout event is enough.
- If your numbers already reconcile against Thinkific, don't buy anything.
- Fixing the checkout value is a small change with most of the benefit. Start there.
- Webhooks need a receiver. If you have none and no appetite for one, that constrains what's realistic.
Thinkific server-side · what we deliver
What the server-side build gives you on Thinkific
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Thinkific orders
Thinkific's order and enrolment webhooks, firing per payment with no browser involved.
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 Thinkific order 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
Thinkific server-side questions, answered
Recurring payments become visible at all, and refunds can reverse.
The Thinkific order ID, one per payment.
Adequate — orders and enrolments cover the money events.
Somewhere to receive the webhook, yes.
Free · 30 min
Move Thinkific events off the browser
WhatsAppFree30 minutesNo obligation
