Why can't I just do this myself?

You can — if you have 80–120 hours to learn server-side GTM, debug iOS dedup edge cases, and stress-test EMQ across every conversion event. We do it in 7–10 days because we've done it 300+ times.

What if it doesn't work?

Two protections: (1) 95% tracking accuracy guarantee — we keep working free until your Meta Match Quality hits 8+. (2) You own the entire stack — server, container, runbook — on your accounts from day one.

Will Apple / Google break this in the future?

1st-party server-side tracking is what survives Apple, Mozilla, and Chrome cookie deprecation. The CAPI / Events API endpoints we use are how Meta, Google, and TikTok publicly committed to keeping the channel open.

Does Calendesk have Google Analytics built in?

We could not confirm a native GA setting. GA4 can be loaded through the GTM container instead.

Can we send the Stripe payment as the conversion?

Yes. Prepaid bookings go through Stripe, so the charge amount is the value, sent server-side so it survives ad blockers.

How do we mark someone as attended?

From the booking's status in Calendesk, read through the REST API. That keeps the conversion tied to a real visit.

Is Zapier enough on its own?

It can move data, but it adds delay and another place for duplicates. For conversions we prefer the API feeding a first-party server container.

CalendeskMeeting & appointment schedulers

Conversion tracking for Calendesk booking sites

Calendesk is unusual among small schedulers: its website editor takes a Google Tag Manager container ID, and there is a separate Facebook Pixel ID field. That makes browser tracking possible, and makes it easy to run the same Meta event twice, once from the Pixel field and once from a tag in GTM. With Stripe prepayment and a REST API also available, the real job here is choosing one source per event, not finding one.

Get my free conversion tracking audit See what we check

Free30 minutesNo obligation

By Ariful IslamHow Calendesk works ↓

Calendesk · what breaks

What goes wrong on a Calendesk booking site

01
Pixel ID field and GTM both sending to Meta
Two installations, duplicated events.
02
Booking events in GTM are unconfirmed
A container can load without seeing the booking finish.
03
Paid and unpaid bookings blended
A Stripe-prepaid session and a free slot are not equal.
04
Booked is counted, attended is not
No-shows stay in the totals.

Calendesk · the fix

What changes — Calendesk

Paid or attended bookings as the conversion
Valued from Stripe or the service price.
A single, deduplicated Meta setup
Browser and server events sharing one event ID.
Booking status read from the API
Attended, cancelled and rescheduled, not guessed.

Calendesk · architecture

What Calendesk actually lets you do

Calendesk documents more here than most schedulers. Native Google Analytics is the one item we could not confirm.

1
A Google Tag Manager container ID in the website editor
Browser tags can load on the booking site.
2
A Facebook Pixel ID field
Useful alone, a duplication risk alongside GTM.
3
Stripe payments
Card, Apple Pay and Google Pay. The reliable money event.
4
A REST API and Zapier
Booking status for the server side, without screen scraping.
5
Check what booking events GTM can actually see
Not documented; we test which steps push anything usable.

Calendesk · diagnose

Where Calendesk tracking breaks, in diagnostic order

With two native tracking slots, duplication is checked before anything else.

01
Check whether the Pixel ID field and GTM both send to Meta
One test booking in Meta's Test Events shows it.
02
Check whether GTM sees the booking complete
A tag on page load is not a tag on booking.
03
Match Stripe charges against reported purchases
Per charge, over a closed window.
04
Compare attended bookings with conversions for unpaid services
No-shows sit in the gap.
05
Check any Zapier zaps that send events
A forgotten zap is a third installation.

Calendesk · prove

The QA evidence — Calendesk

Run on a real paid booking on your Calendesk site, not the editor preview.

Source of truth

Calendesk bookings with their status, and Stripe charges: paid and attended bookings by date and service

A paid booking from a tagged ad click with the identifier confirmed on the booking.
Meta's Test Events showing one event per booking, not two.
The Stripe amount sent as value, deduplicated on a shared event ID.
An attended booking pulled from the API and sent once.
A cancellation and a refund confirmed reversed.
Bookings reconciled per record over a fully closed window.
Re-checked 30 days later, and after any change to the GTM container.

Calendesk · free audit

What we check in the free audit

Check whether the Pixel ID field and GTM both send to Meta
Check whether GTM sees the booking complete
Match Stripe charges against reported purchases
Compare attended bookings with conversions for unpaid services
Check any Zapier zaps that send events

Checked against

Calendesk bookings with their status, and Stripe charges: paid and attended bookings by date and service

Get my free conversion tracking audit

Free30 minutesNo obligation

Calendesk · when not to buy

When you don't need this on Calendesk

Calendesk's native hooks are good enough for some businesses.

If you only advertise on Meta and the Pixel ID field alone fires once per completed booking, that may be enough at low volume.
If every service is prepaid through Stripe and you just need revenue in Google Ads, a clean Stripe-based conversion is the whole job.
If your bookings are mostly existing clients rebooking, retention reports in Calendesk matter more than ad tracking.
Removing a duplicate installation is sometimes the entire fix. We will say so if it is.

Calendesk · what we deliver

The event map for a Calendesk booking site

Service selected
Which bookable service the visitor chose.
Booking created
Leading signal, with service and employee.
Booking paid
Stripe prepayment, at the amount charged.
Booking attended
The conversion where no prepayment is taken.
Cancelled or refunded
Reversed in every destination.

Written guarantee

95%+ tracking accuracy

Measured against Calendesk bookings with their status, and Stripe charges: paid and attended bookings by date and service. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Calendesk questions, answered

One of them for Meta, never both. If you need more than Meta, GTM is the cleaner owner and the Pixel field stays empty.

RELATED GUIDES

Free · 30 min

Get Calendesk tracking firing once, with real value

Book the free call

Free30 minutesNo obligation

Conversion tracking for Calendesk booking sites

What goes wrong on a Calendesk booking site

Pixel ID field and GTM both sending to Meta

Booking events in GTM are unconfirmed

Paid and unpaid bookings blended

Booked is counted, attended is not

What changes — Calendesk

Paid or attended bookings as the conversion

A single, deduplicated Meta setup

Booking status read from the API

What Calendesk actually lets you do

A Google Tag Manager container ID in the website editor

A Facebook Pixel ID field

Stripe payments

A REST API and Zapier

Check what booking events GTM can actually see

Where Calendesk tracking breaks, in diagnostic order

Check whether the Pixel ID field and GTM both send to Meta

Check whether GTM sees the booking complete

Match Stripe charges against reported purchases

Compare attended bookings with conversions for unpaid services

Check any Zapier zaps that send events

The QA evidence — Calendesk

What we check in the free audit

When you don't need this on Calendesk

The event map for a Calendesk booking site

Service selected

Booking created

Booking paid

Booking attended

Cancelled or refunded

Calendesk questions, answered

Should we use the Pixel ID field or GTM?−

Does Calendesk have Google Analytics built in?+

Can we send the Stripe payment as the conversion?+

How do we mark someone as attended?+

Is Zapier enough on its own?+

More on Calendesk

Booking tools beside Calendesk, and what their bookings feed

Get Calendesk tracking firing once, with real value