Server-side tracking for Mindbody
The Mindbody server-side build is mostly about getting the identifier across an origin boundary and then out of a webhook. Pass it into the hosted widget deliberately, store it on the client record so it survives an intro period, and fire on the membership sale rather than the class booking. Marketplace and app bookings are segmented out before any coverage number is quoted.
Free30 minutesNo obligation
Mindbody server-side · what breaks
What goes wrong on Mindbody
- 01
The booking widget on a Mindbody domain
First-party cookies do not cross the origin boundary.
- 02
App bookings with no click identifier
A large share of volume that no ad can be credited with.
- 03
Class bookings counted instead of memberships
A drop-in is a fraction of the value of a retained member.
- 04
Intro offers priced to be easy
Which makes them abundant and unrepresentative.
Mindbody server-side · the fix
What changes — Mindbody server-side
Memberships and packages as the conversion
At expected tenure value, from Mindbody's sales records.
The identifier carried through the hosted widget
Verified on a real booking rather than assumed.
App-sourced volume reported separately
So paid is judged on what it actually produced.
Mindbody server-side · architecture
What Mindbody exposes to a server container
The server-side build on Mindbody specifically.
- 1
Pass the identifier into the hosted widget
Through its supported parameters, verified on a real booking.
- 2
Store it on the Mindbody client record
So it survives the intro period into the membership sale.
- 3
Fire on membership or package sold
Not on class booked.
- 4
Segment marketplace and app bookings out
They have no identifier by construction.
- 5
Wire cancellation as a reversal
Retention is the business model, so churn has to reduce the number.
Mindbody server-side · diagnose
Where Mindbody 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
Check whether the identifier survives into a Mindbody booking
One real booking answers it and it is the usual cause.
- 02
Measure the share of bookings from the app and marketplace
Your attribution ceiling.
- 03
Compare Mindbody sales against reported conversions
Per sale, over a closed window.
- 04
Check whether class bookings are being sent as conversions
Common, and it includes your existing members.
- 05
Check whether cancellations reverse
Usually not, so reported member value only rises.
Mindbody server-side · prove
The QA evidence — Mindbody server-side
Run on Mindbody specifically, on a live conversion rather than in preview mode.
Source of truth
Mindbody's sales and visit records — memberships and packages sold by date, and visits attended
- A booking made through the hosted widget with the identifier confirmed on the Mindbody client record.
- Membership sales reconciled per sale against each platform over a closed window.
- A cancellation confirmed to reverse.
- App and marketplace booking share measured and stated.
- Tenure value shown as a calculation from your own retention.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Mindbody server-side · free audit
What we check in the free audit
- Check whether the identifier survives into a Mindbody booking
- Measure the share of bookings from the app and marketplace
- Compare Mindbody sales against reported conversions
- Check whether class bookings are being sent as conversions
- Check whether cancellations reverse
Checked against
Mindbody's sales and visit records — memberships and packages sold by date, and visits attended
Free30 minutesNo obligation
Mindbody server-side · when not to buy
When you don't need this on Mindbody
Worth reading before you buy anything, from us or anyone.
- If most of your bookings come through the Mindbody app and marketplace, measure that share first — it may show paid is a small slice and this build is not the priority.
- If Mindbody's own reports already reconcile with what the platforms say, this is working.
- If you are not running paid media at meaningful spend, fixing the intro-to-member reporting inside Mindbody is the higher-return work.
- Studios with a single location and word-of-mouth growth often do not need this at all.
Mindbody server-side · what we deliver
What the server-side build gives you on Mindbody
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Mindbody sales records
Mindbody's sales records are authoritative for revenue and its visit records for attendance. Attendance during an intro period is the strongest predictor of conversion available, and it is worth reporting even though it is not a conversion.
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 Mindbody's sales and visit records — memberships and packages sold by date, and visits attended. 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
Mindbody server-side questions, answered
Passed in deliberately through the widget's supported parameters, then written to the client record. It does not travel on its own because the widget is a different origin — and testing this on one real booking is the highest-value ten minutes in the whole project.
Membership sale. Class bookings include your existing members, which means sending them as conversions teaches the algorithm to find people who already pay you.
Monthly fee times your average membership length in months, from your own Mindbody data. Studio retention varies too much for an industry benchmark to be useful.
Store the identifier at intro purchase so it survives to the membership sale weeks later. That gap is longer than any browser cookie you can rely on, and it is exactly the period that matters.
Free · 30 min
Move Mindbody events off the browser
WhatsAppFree30 minutesNo obligation
