How can I track diary appointments
I want to know if/how I can track appointment booked from my adds (Currently ad responders book a session in my google diary using a timetrade app on my web page (s). ) Does Google have an equivalent that will let me track sessions booked.
The short answer is:
The most reliable way to track booked appointments is to use the Offline Conversion Import feature in Google Ads, fed by your TimeTrade data.
Since TimeTrade is the authoritative source for the booking, you need a mechanism to get the confirmed booking data from TimeTrade’s server to your Google Ads account, along with the Google Click ID (gclid) that was created when the user clicked your ad.
A highly effective, long-term, and cost-efficient solution to automate this is to use a server-to-server connection via the TimeTrade API, the Google Ads API (specifically for uploads), orchestrated by a Google Tag Manager (GTM) Server Container hosted on a platform like Stape or Google Cloud Platform.
This bypasses front-end tracking issues and gives you credit only for confirmed, high-value appointments.
The long answer is:
Your challenge is common for businesses using third-party schedulers, as the final, valuable action – the booked appointment – often happens off your main website’s domain or on a server that doesn’t easily fire a client-side tracking pixel back to Google Ads.
TimeTrade is where the true conversion, the appointment, is confirmed, and that is what Google Ads needs to see as a conversion event.
Simply tracking a click on the booking button is inaccurate, as it does not account for no-shows or incomplete forms.
The fundamental issue is moving the conversion signal from the TimeTrade server to the Google Ads server reliably.
To do this, you need two pieces of data: the gclid (the unique identifier Google Ads creates on the ad click) and the appointment confirmation event from TimeTrade, which you can call a custom Standard Event like BookedAppointment.
Here is how the solution works using the APIs and server-side tracking, which is both excellent and cheap in the long run:
When a user clicks your Google Ad, a unique gclid parameter is automatically appended to your landing page URL.
Your first step is to ensure this gclid is captured on the landing page and passed to the TimeTrade app when the user starts the booking process, and that TimeTrade stores it alongside the user’s booking details (name, email, etc.).
Once an appointment is successfully booked in TimeTrade, you have a confirmed conversion.
This is the perfect moment for a server-to-server connection.
You leverage the TimeTrade API to retrieve the details of this confirmed booking, specifically the stored gclid and the timestamp.
You then use a GTM Server Container (hosted affordably on a service like Stape or more complexly on Google Cloud Platform) as the smart intermediary.
The server container receives the confirmed booking data (including the gclid) from the TimeTrade API.
Inside the server container, you configure a tag that uses the Google Ads API to perform an Offline Conversion Import.
This tag sends the gclid and the BookedAppointment event timestamp directly to Google Ads’ servers.
This approach is excellent and cheap for several reasons: it is highly reliable because it is server-to-server, bypassing browser restrictions and ad blockers that often break front-end tracking pixels; it is highly accurate because the conversion is recorded only when TimeTrade confirms the booking, not just when a form is submitted; and it is cost-effective because GTM Server Containers can be hosted cheaply on Stape (often for a very low monthly cost for most small to medium businesses) or by managing a Google Cloud Platform instance, which is far cheaper than the lost revenue from inaccurate ad spend decisions based on bad data.
This server-side setup gives you the most precise signal for your Google Ads account to optimize bidding toward actual, high-value appointments, treating the confirmed booking as the true Standard Event of your campaign.
About The Author
