How to connect Google Analytics, Google Ads and Google Tag Manager to Colib?

Created by Thibault Breboin, Modified on Wed, 26 Aug at 9:23 AM by Thibault Breboin

Add your own Google tags to Colib and measure the traffic on your booking page and your public page in your own Google account, including an event every time a client books an appointment.


Add your tag

  1. Open your Analytics settings. Go to https://www.colib.io/Settings?show=analytics, or click Settings in the main menu and open the Analytics tab, just under Public Page.

  2. Open the Google tags panel. You will find three fields, one per Google product. Fill in only the ones you use. You can leave the others empty.

  3. Paste your identifier and save. Colib checks the format as you type. If an identifier is rejected, compare it with the examples below: a missing prefix is the usual cause.





Which field to fill in

Google Tag Manager – GTM-XXXXXXX

Your container ID, shown at the top of your workspace in Google Tag Manager, next to the container name. Use this field if you prefer to manage all your tags yourself. Colib loads your container, and you decide inside Tag Manager what runs on the page.

Google Analytics – G-XXXXXXXXXX

Your GA4 measurement ID, found in Google Analytics under Admin › Data streams, by opening your web stream. The old Universal Analytics identifiers, starting with UA-, no longer collect anything and are not accepted.

Google Ads – AW-XXXXXXXXX

Your conversion ID, found in Google Ads under Goals › Conversions, in the tag setup instructions. Use this field to measure the results of your ad campaigns.

Already using Tag Manager? Then set up Analytics and Ads inside your container and leave the other two fields empty. Filling in all three would load the same tracking twice and count every visit twice.

What each tag does

The tags load on two pages only: your public page and your booking page. They never run inside your Colib account, and never inside your clients' portal.

Google Tag Manager

Tag Manager measures nothing on its own. It is a container that runs whatever you put in it. Colib loads it and makes the page load events available to it, plus the booking event described below. Everything else is up to your container setup.

Google Analytics

Analytics records a page view as soon as someone opens your public page or your booking page, and collects the visit details automatically:

  • page address, page title and referring site
  • campaign parameters, so you can tell which ad or newsletter brought the visitor
  • device, browser, language, and an approximate location based on the IP address
  • a visitor identifier stored in a cookie, so several pages count as one visit

In practice you see your funnel: how many people land on your public page, how many move on to booking, and how many finish.


Google Ads

The Ads tag stores the identifier of the ad click that brought the visitor, so a booking can be credited back to the right campaign. It also feeds your remarketing audiences if you have turned them on in your Google Ads account.


The booking event

When a client reaches the confirmation screen, Colib sends an event called appointment_booked to your tags, with three details:

  • transaction_id – a unique identifier for the booking, so the same appointment is never counted twice.
  • appointment_type – the name of the appointment type that was booked.
  • establishment_name – the name of your clinic.

Trigger on the event, not on a page address. The confirmation screen appears without reloading the page, so Analytics does not record a separate “thank you page”. Setting a conversion on a page address will never fire. Always trigger on the appointment_booked event instead.

Turning the event into a conversion

How you do this depends on the field you filled in.

  • With Tag Manager. Create a custom event trigger named appointment_booked, then attach whichever tag you want to it: a Google Ads conversion, a GA4 event, a Meta pixel.
  • With Analytics. Open Admin › Events, find appointment_booked after your first test booking, and mark it as a key event. You can then import it into Google Ads as a conversion.
  • With Google Ads alone. The conversion ID on its own is not enough to record a conversion. Either import the event from Analytics, or use Tag Manager. Filling in the Ads field still lets Google credit bookings to the right campaign.

Good to know

  • Appointment changes send the same event. When a client edits an existing appointment, they go through the same confirmation screen, so appointment_booked is sent again. Keep it in mind when you read your conversion numbers.
  • The booking widget counts separately. If you embedded the booking widget on your own website, it runs in a frame, and your tags see that visit as separate from the rest of your site.
  • Changes take effect immediately. Save the settings, then reload your public page and the tag is live.

What Colib never sends

No client information ever reaches your tags: no name, no email address, no phone number, no date of birth, and nothing from your forms.

That said, your tags remain yours. Analytics collects an approximate location and a visitor cookie on a page where people book healthcare appointments, and the appointment type can be revealing depending on the care you offer. You are the one responsible for those tags, so mention them in your privacy policy and ask for consent where your local rules require it.


Checking that it works

  • In Tag Manager, open Preview and load your booking page. Your container appears, and appointment_booked shows up in the event list once you complete a test booking.
  • In Analytics, open Admin › DebugView, or watch the Realtime report while you browse your own page.
  • Make a real test booking and cancel it afterwards. It is the only way to see the booking event fire end to end.

Still stuck? Write to us at support@colib.io with your clinic name and the identifier you pasted, and we will check the setup with you.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article