Conversion tracking for Gazelle
Your Book Now button sends the client off your site to a scheduling page on gazelleapp.io, so your ads see the click and then nothing. What comes back is a reservation you still have to approve, and the money lands later on a Stripe invoice. Gazelle documents one browser hook, a completion redirect to your own site, plus an API that holds reservations, appointments and invoices. We wire the two together so Google and Meta learn which clicks became tunings.
Free30 minutesNo obligation
Gazelle · what breaks
What goes wrong with Gazelle
- 01
The booking happens on gazelleapp.io, not on your site
Gazelle tells you to link a Book Now button to your public self-scheduling URL. The client lands on a page Gazelle hosts, your tags never load there, and Google Ads keeps paying for clicks it can't score.
- 02
A reservation isn't a job yet
Every online booking waits in Dashboard > Online Reservations until you approve or decline it. Count the request as the conversion and bidding learns from the ones you turned down.
- 03
Reminder rebookings look like new customers
The scheduling_link merge code turns every reminder into a private booking link with the client's details preloaded. Those bookings come from your own list, yet they get credited to whatever ad the client last saw.
- 04
The value shows up on the invoice, not the booking
A tuning, a pitch raise and a regulation are each just a bookable service on the scheduler when the request comes in. The dollars only exist once the appointment is completed and invoiced, so the platforms optimize for volume, not revenue.
Gazelle · the fix
What changes — Gazelle
The redirect becomes a real conversion
Gazelle's completion redirect lands the client on a thank-you page on your domain, where the click ID saved at the first visit is still readable.
Approved jobs replace raw requests
Approved reservations and completed appointments come out of Gazelle's API and reach Google and Meta from your own server container. Declined requests never teach the bidder anything.
Existing clients stay out of acquisition
Private-link bookings and clients already Active in Gazelle are tagged as retention and excluded from the conversion your ads optimize on.
Gazelle · architecture
What Gazelle actually lets you do
Search Gazelle's help center for Google Analytics, Facebook or Zapier and nothing relevant comes back, and its website advice is a Book Now button, not an embed. These are the hooks it does document.
- 1
A hosted public scheduling link
Your Self-Scheduling URL is www.gazelleapp.io followed by your company code. Book Now buttons link out to it; nothing of yours runs on that page.
- 2
Completion redirect
Under Settings > Self-scheduler > Behavior, Gazelle sends the client to a URL you choose after the reservation, and its own article names this as the place for conversion tracking and pixels.
- 3
Private scheduling links
The public link with a client ID appended. Reminders use it so existing clients book prefilled, which is how we tell a rebooking from a new lead.
- 4
OAuth2 GraphQL API
The same API Gazelle's own apps use. It exposes clients, pianos, event reservations, appointments, estimates, invoices, invoice payments and cancel notices. No webhooks are documented, so we poll.
- 5
Stripe payments and QuickBooks sync
Card and bank payments run through the Stripe account you connect to Gazelle, and Stripe payouts can sync to QuickBooks Online. We read paid invoices from Gazelle, so the value matches your books.
Gazelle · diagnose
Where Gazelle tracking breaks, in diagnostic order
We start at the hand-off, because on Gazelle the usual fault is a reservation never recorded, not one counted twice.
- 01
Is the completion redirect set at all?
If clients still land on Gazelle's default completion page, no browser event exists for the booking.
- 02
Does the click ID survive the trip to gazelleapp.io and back?
Book from an ad-tagged URL and check the cookie set on your site is readable on the redirect page.
- 03
Are private-link bookings being separated?
The redirect fires on them too, so reminder rebookings must be tagged, not counted as new leads.
- 04
What happened to declined reservations?
Compare redirect events to approved reservations in the API. The gap is requests you turned down.
- 05
Do completed appointments and paid invoices reach the platforms?
If the only conversion is the reservation, a piano move is worth the same as a tuning.
Gazelle · prove
The QA evidence — Gazelle
Run on a real reservation through your public scheduling link, approved and invoiced.
Source of truth
Gazelle's own records — online reservations with approve or decline status, completed appointments, and invoice payments by date
- A reservation made from an ad-tagged URL, where the click ID set on your site is read back on the redirect page and written to the client record.
- Google Ads and Meta Events Manager each showing a single conversion for that reservation, the browser and server copies sharing one event ID.
- A declined reservation confirmed absent from every platform.
- A reminder rebooking from an Active client confirmed tagged as retention.
- Completed appointments and paid invoices reconciled per client against both platforms over a closed month.
- A cancel notice reversed where the platform allows it.
- The whole set run again 30 days on, and after anyone touches the Self-scheduler settings or your thank-you page.
Gazelle · free audit
What we check in the free audit
- Is the completion redirect set at all?
- Does the click ID survive the trip to gazelleapp.io and back?
- Are private-link bookings being separated?
- What happened to declined reservations?
- Do completed appointments and paid invoices reach the platforms?
Checked against
Gazelle's own records — online reservations with approve or decline status, completed appointments, and invoice payments by date
Free30 minutesNo obligation
Gazelle · when not to buy
When you don't need this on Gazelle
Plenty of piano technicians on Gazelle are better off with one settings change and no agency.
- If you're a solo tuner filling the calendar from referrals and reminder rebookings, with no paid ads, the redirect is a nice-to-have and nothing more.
- If you advertise on one platform and only want to know that bookings happen, point the redirect at a page with that platform's tag yourself.
- If most of your revenue is rebuilds quoted through Gazelle estimates and closed by phone, track the estimate approval first.
- If reservations sit unapproved for a week, fix the workflow before measuring it; that's a business problem, not a tracking one.
Gazelle · what we deliver
The event map on Gazelle
Book Now clicked
The hand-off to the gazelleapp.io scheduler. The click ID is parked in a first-party cookie before the client leaves.
Reservation completed
Fired on the completion redirect page. The leading indicator, not the money event.
Reservation approved
Read from allEventReservations in Gazelle's API once you've accepted it; we confirm the status field on your account. Declined requests are dropped.
Appointment completed
The job that moves a client from New to Active in Gazelle. The conversion we recommend Google Ads bids toward.
Invoice paid
Taken from the invoice payment record, valued at what Stripe collected.
Cancellation, rebooking, referral
Cancel notices reverse the event. Reminder rebookings and clients with a Referred By entry are logged for retention and kept out of the ad conversion.
Written guarantee
95%+ tracking accuracy
Measured against Gazelle's own records — online reservations with approve or decline status, completed appointments, and invoice payments by date. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Gazelle questions, answered
Not on the scheduler page; Gazelle hosts it and documents no tag or pixel settings for it. It does document a completion redirect to a page on your own site, and that page is where the tracking goes.
Its help center returns nothing for Zapier, and the developer docs describe an OAuth2 GraphQL API with no webhooks documented. Reservations and invoices have to be read on a schedule, which is what we set up.
Because the button sends the client to gazelleapp.io and your conversion tag never loads there. Until the completion redirect brings them back to your domain, Google sees a click and nothing after it.
The completed appointment, with the paid invoice as the value. A reservation is a request you may still decline, and bidding on requests teaches Google to find more of those.
It will if nothing separates it. Private links carry the client ID and the client is already Active in Gazelle, so we tag those bookings as retention and keep them out of the acquisition conversion.
The redirect and the API are documented settings, not scraped markup, so design changes don't touch them. We still repeat the match 30 days on.
More on Gazelle
- 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 Gazelle, and what their bookings feed
- BuildOpsYour BuildOps pipeline knows which ads won contracts. Google and Meta don't.
- KickservKickserv conversion tracking for ads that fill the inbox but not the schedule
- OptimoRouteWhich ads put new accounts on your OptimoRoute routes? Right now, nobody can say.
- MarkateMarkate is full of booked jobs. Your ads can't see which clicks booked them.
- ServicePowerYour ads are taking credit for warranty jobs ServicePower sent you
- ServiceTradeYour ads are taking credit for deficiency work your ServiceTrade inspections already won
- CleanGuruGoogle Ads never hears about the contracts you win in CleanGuru
- Route4MeRoute4Me knows which quotes became serviced stops. Your ads still count every form fill.
