Question from Reddit:
Hey there,
Im going to run ads for new client and they use acuity scheduling. They gave me editor access to their calendars. How can I track the bookings if I dont have full access to their acuity account? I cant see an option to add my pixel to the calendar page.
Thanks!
Answer from Nabil:
The short answer is:
The primary issue is that Acuity Scheduling, being a third-party platform, does not typically allow for easy client-side Meta Pixel installation, especially without full account access.
Since you can’t edit the page code directly, the client-side approach is blocked.
The most effective and future-proof solution is to completely bypass the need for code access by implementing a server-side tracking pipeline using the Facebook Conversions API (CAPI) combined with the Acuity API.
This setup allows you to trigger the Purchase
or Schedule
conversion event directly from the Acuity server to Meta’s server, eliminating the need for any on-page code changes or GTM.
The long answer is:
Your situation is common when dealing with third-party scheduling or checkout tools, where you have limited access and the platform doesn’t offer a simple pixel integration method.
Since you have editor access to the calendars but not the full account settings, you are restricted from adding the traditional client-side Meta Pixel code via a custom code injection area that Acuity usually provides in its main settings.
Even if you could add the pixel, client-side tracking is prone to being blocked by ad-blockers and privacy browsers, leading to underreporting.
The best solution is to move to a server-side tracking architecture that collects conversion data directly from the source of truth – the Acuity booking confirmation – and sends it to Meta’s server.
This involves using the Acuity API to trigger the conversion event.
The Acuity API allows you to set up a webhook that will fire a signal to an external endpoint every time a new appointment is booked.
You can set this external endpoint to be your server-side container hosted on a platform like Stape or Google Cloud Platform.
When your server container receives the booking data from the Acuity API webhook, it is instantly enriched with any customer matching parameters you can gather (like email or phone number).
This enriched data is then sent using the Facebook Conversions API directly to Meta’s server.
This server-to-server connection achieves two critical things: first, it guarantees that every single booking is tracked, regardless of ad-blockers or browser settings, leading to highly accurate reporting.
Second, it eliminates the need to touch the Acuity calendar page code or even use GTM on the calendar page, as the event is triggered from the backend.
GTM can still be used on your main website pages to collect initial click and user data, which can then be matched with the server-side conversion event, creating a complete and highly reliable attribution picture for your campaigns.
This CAPI and Acuity API connection is the gold standard for tracking conversions on third-party domains.