Capture the GCLID on Every Acuity Scheduling Booking
Click data often disappears between a Google Ads landing page and a later booking. This guide shows how to preserve the click identifier from arrival, attach it to each Acuity Scheduling appointment, forward it to a CRM, and return it to Google Ads as an offline conversion.
Why booking-level click data matters
Analytics can count visits after an ad click, yet it may not connect that visit to a booked appointment or paying customer. Without the click identifier attached to the booking, campaign reporting stops at the website visit and budget decisions rely on incomplete evidence. Carrying the identifier through the booking closes that gap: the appointment record shows which click produced it, the CRM can retain it alongside contact details, and Google Ads can receive it later as an offline conversion.
Three-step capture workflow
- Install the attribution snippet on the website using the site builder or platform settings appropriate to the site. 2. Add a hidden field named GCLID to the Acuity Scheduling booking form so there is a destination for the stored value. 3. On arrival, the snippet reads the identifier from the landing URL and stores it in the browser. 4. When the visitor submits a booking, the snippet writes the stored value into the hidden field. 5. Acuity records it with the name, email, phone and other submitted details. Check the Appointments section and booking notification emails, then forward the record through Acuity integrations or an automation tool such as Zapier or Make.
Returning the identifier to Google Ads
Create the conversion action first: in Google Ads open Goals, then Conversions, start a new conversion, choose Imported, select CRMs, files, or other data sources, and on the data-source screen choose Add data source later. Next choose the pipeline moment that should trigger the upload. A closed deal is the most mature signal, but low closed volume can starve smart bidding strategies such as Maximise Conversions, Maximise Conversion Value, or Target CPA, which generally need at least 50 conversions per month. When closed deals are fewer, an earlier qualified event such as a new CRM deal may give bidding enough usable signal. Build the automation with that event as the trigger, select Google Ads and Send Offline Conversion as the action, and map the stored GCLID from the CRM or booking record to the matching field. Test the complete path before increasing ad spend.
What to verify before launch
URL-only capture fails when the visitor lands on one page and books on another, because the identifier is no longer in the address bar. Browser storage on arrival avoids that dependency and also survives a return visit on a later day. The same hidden-field setup can carry UTM and channel attribution alongside the click identifier, so paid and organic arrivals are both described. Use the field map below as a pre-launch checklist: confirm the hidden field exists, submit a test booking from a tagged landing page, verify the value in Acuity, confirm it reaches the CRM, and only then enable the offline conversion.
| Field | Paid-search example | Organic-search example |
|---|---|---|
| Channel | Paid Search | Organic Search |
| Channel Drilldown 1 | ||
| Channel Drilldown 2 | Executive Search Campaign | Search-engine domain visited |
| Channel Drilldown 3 | CFO Recruitment Sydney | Search query, if available |
| Channel Drilldown 4 | Free Consultation Ad | Not applicable in this example |
Illustrative examples from the guide; actual values depend on campaign tagging and search data available
Frequently asked questions
What is the minimum setup to capture the identifier on a booking?
Create a hidden field named GCLID on the booking form, install the attribution snippet on the site so it stores the click identifier from the landing URL, and let it populate that field at submission. The value then travels with the booking record.
Why store the identifier on arrival instead of reading it at booking time?
Because the identifier is stored in the browser on arrival, it can survive navigation to another page and a later return visit, unlike a method that only reads the URL on the booking page itself.
How do I return the booking identifier to Google Ads?
Create an imported conversion action in Google Ads, choose to add the data source later, then send the stored identifier from the CRM or booking record via an automation tool when the chosen pipeline event occurs. Test the flow before scaling spend.
Should the offline conversion fire on booking or on a later deal stage?
Waiting for closed deals may produce too few events for smart bidding, which the guide notes generally needs at least 50 conversions per month. An earlier qualified-lead or new-deal event can provide a stronger signal when closed volume is low.