Track bookings and quotes with Google Tag Manager

Paste your GTM Container ID to send booking and quote-request events from your public booking page into GA4, Meta Pixel or Google Ads.

Settings › Business Profile › Analytics & Tracking

Servetic does not have separate fields for a GA4 Measurement ID or a Meta Pixel ID. Instead you connect one Google Tag Manager container, and wire up GA4, Meta Pixel, Google Ads or anything else from inside that container - without ever coming back to Servetic to change something again.

Add your container

  1. Open Settings from the sidebar and choose Business Profile.
  2. Scroll to Analytics & Tracking.
  3. Find your Container ID in Google Tag Manager, under Admin, Container Settings. It looks like GTM-XXXXXXX.
  4. Paste it into GTM Container ID and save.
  5. Leave the field blank if you do not use GTM - nothing is loaded on your booking page until an ID is saved.

Where the tag loads

The container only loads on your public-facing booking and quote pages - never inside the Servetic app itself, since those pages are shared by every business on the platform and cannot carry any one business's tracking snippet.

Events Servetic sends

EventFires when
booking_submittedA booking is finalised. For a booking that requires payment, this fires only after the payment is verified, not at form submission.
quote_request_submittedA quote request is created, including the quote-only part of a mixed order that also contains a direct booking.

Both events are pushed onto the page's dataLayer, the same mechanism GTM's own snippet uses, so any tag, trigger or variable you build in GTM can react to them.

Wiring up GA4 conversion tracking

  1. In GTM, create a Custom Event trigger whose event name is exactly booking_submitted.
  2. Connect that trigger to a GA4 Event tag.
  3. Publish the container.
  4. In GA4, mark that event as a key event.

Booking forms embedded on your own website

When your booking form is embedded on your own site using the script embed from Booking Forms, Widget & Sharing, these events are also forwarded to your website's own GTM container running on your page, rather than only firing inside the embedded frame. This avoids the same event being counted twice if both containers could technically see it.

Start a 15-day free trial · See pricing · Book a demo