Skip to content

Send Square Appointments bookings to Google Ads as server-side conversions

When a booking happens inside an embedded Square Appointments widget, a page-view or browser tag can miss it. Server-side tracking instead sends the booking details directly to Google Ads, so ad blockers and browser privacy limits do not break the record.

Why browser tracking misses embedded bookings

Browser-based measurement can lose bookings for three common reasons. Ad blockers may prevent the Google Tag from loading at all. Privacy features in browsers such as Safari can sever the tag connection after roughly a day, so a click today and a booking four days later cannot be linked. A person may also click on a phone and finish on a laptop, and browser tracking cannot join those separate sessions.

Counting a confirmation page has a further gap for embedded booking widgets: the flow does not move to a dedicated URL, and a confirmation step does not carry the name, email, or phone number that Google Ads expects with a conversion. Server-side tracking addresses this by sending client details directly to Google, rather than waiting for a browser event to fire.

Two timing options

Choose the timing that matches the decision you want bidding to optimise for.

Send at booking: Use a visual workflow tool to watch for a new Square Appointments booking, retrieve the name, email, and phone number through the Square API, hash each value with SHA-256 as Google requires, and send the conversion to Google Ads with the GCLID, IP address, user agent, and other matching signals. This suits businesses that treat a booked appointment as the conversion.

Send when the lead becomes a customer: Capture the GCLID at booking, store it on the CRM record, and send the conversion later when the lead is qualified, a deal is created, or the first payment occurs. This suits businesses where a booking alone is not valuable enough to optimise for. Because most CRMs do not connect directly to Google Ads, an intermediary such as Zapier or Make is typically used to pass the record through at the chosen stage.

Field map for sending the conversion later

For the delayed option, the field map is the critical part:

  • Install the attribution snippet on the website so the GCLID from the ad URL is stored in the browser and survives browsing and return visits.
  • Add a custom question to the Square Appointments intake form, set it to be filled automatically, and name it gclid so the stored click ID can be written into it.
  • At booking, the GCLID is captured with the name, email, and phone number. Bookings are stored under Appointments in the Square Dashboard.
  • Push the booking details, including the GCLID, into the CRM with a tool such as Zapier or Make, so the click ID stays on the client record.
  • When the lead reaches the agreed stage, send the conversion from the CRM through the intermediary to Google Ads.

Checklist before you rely on the data: confirm the custom field is populated on test bookings, confirm the GCLID reaches the CRM record, confirm the later conversion fires only at the intended stage, and confirm hashed client details are included where required.

Three reports to run after setup

Once conversions flow back, three views answer different budget questions.

Conversions by keyword: Compare keywords against the appointments they produced, rather than impressions and clicks alone. For a business running separate campaigns for different services, this shows which terms fill the calendar and which consume spend without bookings.

Conversion value by campaign: Attach the deal value from the CRM record to each conversion. A booking from one campaign may be worth several times a booking from another, so equal weighting would misdirect spend. Value-based reporting makes that gap visible before budget is moved.

Conversions by geography: Split conversions by country, state, or postcode. For local appointment businesses, this reveals whether bookings come from the intended service area or whether spend is leaking to distant clicks. Location bid adjustments can then increase investment in postcodes that convert and reduce it where they do not.

What to expect

Reliable conversion data supports the decisions that matter most: which keywords deserve more budget, which campaigns produce valuable customers, and which locations to keep or drop. It also gives automated bidding a clearer picture of the ideal client, which can help ads reach more similar people. Reported Google averages for server-side tracking are a 23% increase in recorded conversions and a 10% reduction in cost per conversion, but your result depends on how much browser tracking was previously missing and on the quality of the data sent.

Booking-time versus customer-time conversion sending
TimingBest forData path
At bookingBusinesses optimising for appointmentsBooking trigger, hashed client details, GCLID and matching signals sent to Google Ads
When lead becomes a customerBusinesses optimising for qualified leads, deals, or first paymentGCLID stored on booking and CRM record, then sent at the chosen sales stage

Both routes use server-side sending; the difference is when Google Ads receives the conversion.