Meta Conversions API setup for Thinkific
Fewer accidental paths than an open platform, and the same recurring-revenue gap. A student's Meta value stops updating after their first payment.
Free30 minutesNo obligation
Thinkific + Meta CAPI · 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 + Meta CAPI · the fix
What changes — Thinkific + Meta CAPI
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 + Meta CAPI · architecture
How Meta tracking behaves on Thinkific
One event per payment.
- 1
Order ID as event_id
Unique per payment.
- 2
First payment and renewals distinct
So value accumulates.
- 3
Click ID on the student record
The only durable storage.
- 4
Customer data from the Thinkific record
Normalized before hashing.
- 5
Refunds reversed
Material in this category.
Thinkific + Meta CAPI · 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 + Meta CAPI · prove
The QA evidence — Thinkific + Meta CAPI
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 + Meta CAPI · 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 + Meta CAPI · 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 + Meta CAPI · what we deliver
What gets built for Meta on Thinkific
A shared event ID on both paths
The Thinkific order ID, unique per payment and present on the webhook.
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 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 + Meta CAPI questions, answered
Because only the first payment is being sent. Renewals need the webhook.
The Thinkific order ID.
Low — injection is site-level and singular. Missing events are the bigger issue.
Capture fbclid on the course page and store it against the student.
Free · 30 min
Get Pixel and CAPI counting once on Thinkific
WhatsAppFree30 minutesNo obligation
