Implementations / Booking to Ads
Turn Acuity bookings into Google Ads conversions.
Acuity Scheduling was built to fill a calendar, not to talk to an ad account. We wire the booking event to Google Ads so a confirmed appointment shows up as a conversion, not just a line in your calendar. The same pattern works whether you run one practitioner's calendar or several staff calendars inside one Acuity account.
- $0 setup. Month to month.
- 30-day guarantee, pay only if satisfied.
- Free proposal within one business day.
The workflow
From a booking widget to a conversion action.
The field map
Acuity stores the appointment type, calendar, client contact details, and any custom intake questions you have added to the booking form. We decide which of those becomes the conversion name in Google Ads, and whether the appointment type carries a fixed price we can pass through as conversion value. A recurring appointment type, such as a standing weekly session, needs its own rule too, since only the first booking in a series may deserve a fresh conversion.
The identity match
We add a hidden custom question to your booking form that reads the gclid off the page URL when a visitor lands on your booking page from an ad. That value rides along with the appointment record so it can be matched back to the original click when the conversion is imported. We check the current lookback window Google Ads allows for offline imports at setup time, since that limit shifts as Google updates the feature.
Where the data enters
Acuity can fire a webhook when an appointment is scheduled, rescheduled, or cancelled. We read that webhook through Zapier or Make and write the result into Google Ads as an offline conversion import, with GA4 as an optional second destination if you also want it there. A short delay between the webhook firing and the import showing up in Google Ads is normal and does not mean the connection failed.
How failures surface
A booking made from a direct visit, a referral, or an ad blocker that strips URL parameters will not carry a gclid. We do not drop that booking. It still records in Acuity; it just gets logged as unattributed instead of silently counted or silently lost. We can show you the unattributed count each month, right alongside the attributed one, so the real split is visible rather than assumed.
What makes this hold up over time.
Access we need first
Admin access to your Acuity account to add the custom question and webhook, and access to your Google Ads account to create the conversion action. If you already run GA4, we need that too. We ask for the minimum level of access needed to do the work, not full account ownership.
What gets delivered
A written field map, a working webhook connection tested against a real appointment, and a plain note on what a healthy upload looks like inside Google Ads so your team can check it without calling us. We also hand over the exact settings screens involved, in case your own staff change providers later.
The acceptance test
We book a real test appointment through your own page, confirm the gclid survives the trip through Acuity, and confirm the offline conversion lands in Google Ads with the right time and value before we call it done. If that first test does not clear the import queue, we keep working until it does.
What is out of scope
Your no-show and deposit policy, and any bidding strategy inside Google Ads, stay yours to set. We build the pipe that carries the data. What you do with the data in your account is a separate conversation, and one we are happy to scope if you want our help with it too.
How the setup runs.
01
Audit
We open your Acuity account and your Google Ads account side by side, note every custom question already in the booking form, and confirm what, if anything, is currently being tracked.
02
Build
We add the hidden gclid question, connect the webhook to Zapier or Make, and map the appointment fields into the offline conversion format Google Ads expects, including a value if one applies.
03
Verify
We run a real booking through your live page end to end, confirm it clears Google Ads' import queue, and leave you a short checklist for a monthly spot check.
Acuity to Google Ads FAQ.
Not directly. Acuity does not have a native Google Ads integration, so this runs through Acuity's own webhooks and a connector like Zapier or Make. We confirm the exact setup available on your Acuity plan before we start.
They still show up in Acuity as normal appointments. They just will not be counted as a Google Ads conversion, because there is no click to match them to. We report the unattributed rate so it is visible, not guessed at.
Yes, if you want it. Acuity's cancellation and reschedule webhooks can trigger a conversion adjustment in Google Ads, so a booking that later cancels does not stay counted as a win forever.
Google's own import processing usually takes a day or two, though the exact window can shift and we check current behaviour at setup rather than assume it. Same day is not typical, so we build reporting expectations around that.
Usually, as long as the page passes the gclid parameter through to the Acuity widget embed. Some page builders strip URL parameters. We test this on your actual page before quoting the build, not after.
Get your Acuity to Google Ads setup scoped.
Tell us how your booking page is built and what you already track. We will send a free proposal within one business day with a fixed price and a clear list of what we need access to.