Conversion tracking for SuperSaaS schedules and credits
SuperSaaS is a do-it-yourself scheduler that ends up running very different businesses (lessons, equipment rental, room hire, testing slots), often embedded straight into the owner's website. Its Zapier connection documents triggers for new appointments, credit purchases and form submissions, which gives a server-side source even where browser tags fail. The twist is credits: a customer can pay once and book many times, so the money and the bookings arrive as separate events.
Free30 minutesNo obligation
SuperSaaS · what breaks
What goes wrong on SuperSaaS
- 01
Bookings paid with credits counted as revenue
Money taken once gets counted again on every booking that spends it.
- 02
Credit purchases with no booking attached
The real sale fires nowhere your ads can see.
- 03
Embedded schedule, unknown tracking
Whether your tags see inside it has to be tested, not assumed.
- 04
Form submissions mistaken for bookings
SuperSaaS treats them as separate triggers, and they should be separate conversions.
SuperSaaS · the fix
What changes on SuperSaaS
Money counted where money changed hands
Credit purchases and paid appointments, at their amounts.
Bookings kept as an engagement signal
Volume for optimization without double-counting revenue.
A server-side feed independent of the browser
Built on the Zapier triggers SuperSaaS documents.
SuperSaaS · architecture
What SuperSaaS actually lets you do
What SuperSaaS documents through Zapier, and what still has to be tested on your schedule.
- 1
Embeddable schedules
A schedule can sit inside your own website or stay on SuperSaaS.
- 2
Zapier trigger: new appointment
A server-side signal for each booking.
- 3
Zapier trigger: credit purchase
The cleanest revenue signal on a credit-based schedule.
- 4
Zapier trigger: form submission
Separate from appointments, and best treated as a lead.
- 5
Check whether Google Analytics or a pixel can be added
Not confirmed in the documentation we checked. Test it before building around it.
SuperSaaS · diagnose
Where SuperSaaS tracking breaks, in diagnostic order
On SuperSaaS the first question is what kind of money a schedule takes, because that decides what the conversion is.
- 01
Work out whether each schedule uses credits, direct payment or neither
Three different conversion designs, and one account can have all three.
- 02
Compare purchase events with actual payments
More purchase events than payments means credit bookings are being counted as sales.
- 03
Book through the embedded schedule from a tagged click
Confirm whether the click identifier survives into the appointment.
- 04
Check which Zapier triggers are already in use
A Zap feeding appointments to a spreadsheet can usually be pointed at the server container.
- 05
Check whether form submissions fire the booking conversion
If they do, leads and bookings are inflating each other.
SuperSaaS · prove
The QA evidence on SuperSaaS
Run on your live SuperSaaS schedules, with a real booking and a real credit purchase.
Source of truth
SuperSaaS's appointment and credit purchase records by date
- A credit purchase from a tagged click confirmed as one revenue event at the correct amount.
- A booking that spends those credits confirmed not to send revenue again.
- New-appointment and credit-purchase triggers confirmed arriving in the server container.
- Form submissions confirmed reporting as leads, not bookings.
- Appointments and purchases reconciled customer by customer against each platform.
- Matched per customer over a closed window, never on totals.
- Re-checked 30 days later and after any change to your Zaps.
SuperSaaS · free audit
What we check in the free audit
- Work out whether each schedule uses credits, direct payment or neither
- Compare purchase events with actual payments
- Book through the embedded schedule from a tagged click
- Check which Zapier triggers are already in use
- Check whether form submissions fire the booking conversion
Checked against
SuperSaaS's appointment and credit purchase records by date
Free30 minutesNo obligation
SuperSaaS · when not to buy
When you don't need this on SuperSaaS
Plenty of SuperSaaS accounts are too small to justify it.
- If your schedule is free to book and you only care how many bookings an ad drives, one Zap and consistent UTMs may be enough.
- If you run no paid ads, SuperSaaS's own reports will tell you everything this build would.
- If Zapier task limits are already a cost worry at your volume, weigh that before adding more Zaps.
- One schedule, one campaign and no credits is usually small enough for your own developer.
SuperSaaS · what we deliver
The SuperSaaS event map
Schedule viewed
On your site or on SuperSaaS, recorded separately.
Appointment created
From the new-appointment trigger.
Credits purchased
The revenue event, at the amount paid.
Form submitted
From the form-submission trigger; a lead, not a booking.
Appointment paid directly
Where a schedule takes payment per booking rather than in credits.
Returning customer
Flagged so repeat bookings are not counted as new.
Written guarantee
95%+ tracking accuracy
Measured against SuperSaaS's appointment and credit purchase records by date. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
SuperSaaS questions, answered
Not that we could confirm. What it documents is Zapier triggers, which we route through a first-party server container to each platform.
As the revenue event, at the amount paid. The bookings that spend those credits are engagement, not new sales.
We could not confirm that from the documentation, so we test it on your page. If it cannot see the booking, the Zapier trigger becomes the source.
It is captured on your page and passed into the booking, usually through a booking field if your schedule allows one, so the server can match it. We confirm it lands on a real appointment.
At the booking volumes most SuperSaaS users have, yes, with monitoring. The risk is a Zap that quietly stops, so we alert on it.
More on SuperSaaS
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside SuperSaaS, and what their bookings feed
- TimeTapConversion tracking for TimeTap's embedded scheduler
- ApptotoConversion tracking for Apptoto booking pages
- Fillout SchedulingConversion tracking for Fillout Scheduling
- Meta · Local servicesMeta Ads conversion tracking for local service businesses
- Meta · Coaches & consultantsMeta Ads conversion tracking for coaches and consultants
- Meta × Appointment SystemHow to reconcile Meta Ads against your practice or scheduling system
- Meta · Lead → booked callHow to track lead to booked call for Meta Ads
- Coaches & consultantsConversion tracking for coaches and consultants, where every booked call counts
Free · 30 min
Get SuperSaaS tracking done properly
WhatsAppFree30 minutesNo obligation
