Conversion tracking for 17hats bookings
On 17hats the booking rarely happens on the visit the ad paid for. A prospect fills in your inquiry form, you reply, and the scheduling link arrives in an email days later, or they find the embedded schedule on a return visit. Add optional approval, where a booking sits as pending until you accept it, and default pixel tracking either misses the booking entirely or counts requests you later turn down.
Free30 minutesNo obligation
17hats · what breaks
Where 17hats bookings fall out of your ad data
- 01
The scheduling link travels by email
The client opens it from their inbox, often on a different device, so the session that clicked your ad never sees the booking.
- 02
Pending requests counted as clients
With approval switched on, a booking is a request until you accept it. Counting at the request stage rewards campaigns that send people you decline.
- 03
One account, several businesses' worth of services
Solo operators often list a free intro call next to a paid shoot or a retainer session. One flat conversion value hides which ads produce the paid work.
- 04
Workflow emails mistaken for confirmations
The confirmation and workflow emails 17hats sends say nothing to Meta or Google, however complete they look in your inbox.
17hats · the fix
What changes on a 17hats account
Approved bookings, not requests, sent as the conversion
Requests still recorded, but the ad platforms learn from the ones you accepted.
The click tied to the person, not the browser
Captured at the inquiry and matched when the same client books from the emailed link.
Value taken from the payment where one is collected
Free consultations sent separately, so they stop diluting paid sessions.
17hats · architecture
What 17hats actually lets you do
Confirmed from 17hats' own help documentation, plus the gaps you need to check on your account.
- 1
Two ways in: an emailed link or an embedded schedule
The availability page can be copied as a URL for emails or embedded on your website with the code 17hats provides.
- 2
Optional approval before a booking is final
Bookings can wait in a pending state until you accept them, which is the natural place to draw the conversion line.
- 3
Workflows triggered at booking
A booking can start a 17hats workflow. Check whether any workflow step can call an outside URL; if it can, that becomes a server-side trigger.
- 4
Payments taken as part of booking
Where you charge at booking, that amount is the cleanest value you will get.
- 5
Analytics tags inside the schedule: unverified
Check whether the hosted or embedded schedule accepts Google Analytics, GTM or a Meta Pixel at all. Assume nothing fires there until a test booking proves it does.
17hats · diagnose
Where 17hats tracking breaks, in diagnostic order
Start with the routes clients actually use to book, because on 17hats the route predicts the failure.
- 01
Count how many bookings came from the emailed link
If most did, a browser pixel was never going to see them. That alone explains a large gap.
- 02
Check whether the click survives from inquiry to booking
Look up one recent paid client and see whether anything links their booking to the ad they clicked.
- 03
See whether pending requests are being reported
If a conversion fires before approval, declined requests are in your numbers.
- 04
Compare paid booking totals with reported value
If the platforms show a flat value per booking, free intro calls are pulling your return figures down.
- 05
Test the embed on your live site
Check whether the embed renders in a way that lets your page see the booking at all, or whether it is effectively a sealed frame.
17hats · prove
How the 17hats setup is proven
Every check runs on a real booking in your 17hats account, through the same links your clients use.
Source of truth
17hats' booking and payment records, approved bookings by date with the service booked
- An ad click followed by a booking from an emailed link, matched to the right campaign.
- A booking left pending confirmed not to convert, then confirmed to convert on approval.
- A paid booking sent at the amount 17hats collected, not a default value.
- A free consultation sent as its own event, separate from paid services.
- An embed booking and an emailed-link booking both traced end to end.
- Bookings reconciled client by client over a fully closed month.
- The same reconciliation repeated 30 days later.
17hats · free audit
What we check in the free audit
- Count how many bookings came from the emailed link
- Check whether the click survives from inquiry to booking
- See whether pending requests are being reported
- Compare paid booking totals with reported value
- Test the embed on your live site
Checked against
17hats' booking and payment records, approved bookings by date with the service booked
Free30 minutesNo obligation
17hats · when not to buy
When you don't need this on 17hats
Plenty of 17hats users should not spend money on this. Check which group you are in.
- If your clients come from referrals and repeat work and you spend little on ads, a spreadsheet of where each booking came from will tell you more.
- If you only ever send the scheduling link after a phone call, the call is the real conversion and the booking adds little.
- If your paid work is invoiced later rather than at booking, reconcile the invoices first; the booking says nothing about revenue.
- If you already ask every client how they found you and the answers are reliable, start there before building anything.
17hats · what we deliver
The 17hats event map
Inquiry submitted
Your website form, where the click identifier is first captured.
Schedule opened
From the embed or the emailed link, labelled by which one.
Booking requested
The pending state when approval is on. A leading indicator only.
Booking approved
The conversion for free sessions, sent once you accept.
Booking paid
The conversion for paid services, at the amount collected.
Service booked
Carried on every event so a discovery call never looks like a paid job.
Written guarantee
95%+ tracking accuracy
Measured against 17hats' booking and payment records, approved bookings by date with the service booked. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
17hats questions, answered
Treat that as unknown until tested. 17hats does not document pixel support on the schedule, so make one test booking and watch the Events Manager test tool before trusting any number.
Yes, but not by a pixel on the booking page. The click is captured when they first inquire on your site and matched to the booking afterwards, server-side.
When you approve it, if you use approval. Requests you decline are not clients, and teaching the ad platforms to find more of them is money wasted.
Workflows can start at booking, but whether a step can call an outside URL needs checking on your plan. If it cannot, the booking is picked up another way.
Yes. Send the free call as a lead signal and the paid session at its collected value, so bidding favours the ads that produce paying clients.
More on 17hats
- 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 17hats, and what their bookings feed
- MoxieConversion tracking for Moxie's meeting scheduler
- Bloom.ioConversion tracking for photographers booking on Bloom.io
- BonsaiConversion tracking for Bonsai scheduling
- Google Ads · Wedding servicesGoogle Ads conversion tracking for wedding vendors
- Meta · PhotographyMeta Ads conversion tracking for photography businesses
- Google Ads × Invoicing SystemHow to reconcile Google Ads against your invoicing system
- Meta · Lead → booked callHow to track lead to booked call for Meta Ads
- PhotographyConversion tracking for photographers, measured in booked shoots
Free · 30 min
Find out what your 17hats bookings are really telling the ad platforms
WhatsAppFree30 minutesNo obligation
