Customer Tracking with the Univents DataLayer

After reading this, you'll be able to set up GTM and custom tracking code on your booking page, you'll know which events Univents pushes into the DataLayer and when — and that consent in the cookie banner comes first.

Univents provides a structured DataLayer on every booking page. This lets you pass submitted inquiries and completed steps to external tools like Google Tag Manager (GTM), GA4, or the Meta Conversion API — without personal data and fully GDPR-compliant.

Two things decide whether anything arrives at all: consent in the cookie banner and the visitor's first interaction. Both come first here.

Customer Tracking with the Univents DataLayer

On the first visit, the cookie banner Cookie Settings appears at the bottom of the booking page. Whatever the visitor chooses there applies to the whole visit:

  • Accept all — only after this does Univents load your GTM container and your own tracking code from the Code for <head> and Code for <body> fields. Only after this does Univents push events into the DataLayer as well. Before that, neither happens.
  • Necessary only — this switches tracking off for that visitor: no GTM, no custom code, and no events in the DataLayer. The page itself works normally.
  • The decision stays stored until the visitor changes it via the Cookie settings link in the page footer.

To test: open the booking page in an incognito window or clear the browser’s site data for univents.app, then click Accept all. Without that consent the DataLayer stays empty — that is intentional, not a fault.

Events do not start just because the page is viewed. The first ones come with the first interaction — a click or typing something. One exception: if required products are configured, the inquiry form adds them itself on load, and that can already report a step without the visitor doing anything. Sections a visitor filled in before consenting are not reported afterwards — only what happens after clicking Accept all counts.

Adding Tracking Code to Your Booking Page

You'll find the tracking settings in the editor of each booking page under the Analytics section (section 06 in the left navigation).

  1. Open Booking Pages from the menu and click on the desired page.
  2. In the editor, select Analytics from the left navigation.
  3. Enter your container ID in the GTM Container ID field (format: GTM-XXXXXXX).
  4. Optional: Add additional scripts in the Code for <head> field, e.g. the Meta-Pixel or GA4 directly (without GTM).
  5. Optional: Add code in the Code for <body> field that should be inserted at the end of the body.
  6. Click Save — changes are also saved automatically after a brief period of inactivity.

These scripts load only after the visitor has accepted in the cookie banner.

Conversion tracking via PostHog is automatically active.

Your own scripts load on the booking page too. If you add a Meta-Pixel (connect.facebook.net) via Google Tag Manager or the Code for <head> field, it now runs reliably — the booking page's security policy allows that source. Before, the script was blocked silently there: it looked as if tracking was running, but no hit ever arrived.

Which events Univents sends

Once the visitor has accepted, Univents pushes an event into the page’s DataLayer at every relevant step — even without a GTM container ID. Your GTM container is what reads those events and passes them on to GA4, Meta, and other systems. You don’t need to write any custom code for this.

booking_start

Sent on the first interaction on the booking page — once per session. Contains booking_page_id and booking_page_name.

booking_start is the older of the two names. Univents keeps sending it so existing triggers in Google Tag Manager don't stop firing.

booking_page_view

Sent at the same moment as booking_start — on the first interaction, not on page load. Contains bookingpage_id (the historic spelling; it is kept for compatibility), booking_page_id, and booking_page_name.

step_complete

Sent as soon as a visitor completes a step. Contains booking_page_id, step_index, and step_name.

  • Wizard: when advancing to the next step.
  • Single-page inquiry form: as soon as a section is complete — date and guests, location, catering, contact. The “Catering” section counts even when the form adds required products itself on load.
  • Webshop: when the checkout opens.

booking_submit and generate_lead

Both are sent after a successfully submitted inquiry or booking, with the same content: booking_page_id, booking_page_name, booking_request_id, guests, and — in the inquiry form, wizard, and webshop — coupon when a discount code was applied.

This holds in every form of the booking page: inquiry form, wizard, webshop, and the booking chat. The chat never passes a coupon. On a pure inquiry page, the submission is the conversion event too — no money changes hands there; an inquiry is created.

generate_lead is the GA4 name for this event; booking_submit is the older name. Both carry the same values, so you can build your triggers on either. For Meta the standard event is called Lead — send it as Lead in your Meta tag.

These events do not exist

Univents sends no add_to_cart and no purchase. Product selection, cart, and prices are not reported as their own event: there is no item list, no price fields such as total_gross or price_net_total, and no currency, language, or session_id either. Earlier versions of this article described such events — they were never sent, which is why triggers waiting for them never fire.

If you want to evaluate revenue or cart data, hook into generate_lead and add the missing values via your own tag in Google Tag Manager.

Key Parameter Reference

ParameterMeaning
booking_page_idTechnical identifier of the booking page
booking_page_nameName of the booking page as you entered it in the editor
bookingpage_idThe same identifier in its historic spelling, only on booking_page_view
step_indexNumber of the completed step, starting at 0
step_nameName of the step, e.g. checkout in the webshop
booking_request_idTechnical identifier of the created inquiry or order — no personal data
guestsNumber of guests as a figure. The inquiry form and the booking chat send 1 when no count was captured, the webshop 0; in the wizard the guest count is a required step and always set
couponThe discount code the server applied — present only if there was one; the booking chat never passes one

Setting Up in Google Tag Manager

  1. Open your GTM container and select Triggers.
  2. Create a new trigger of type Custom Event.
  3. Set the event name to booking_start (or booking_page_view), step_complete, or generate_lead.
  4. Create matching tags (GA4 Event, Meta Conversion API, etc.) and link them to the trigger.
  5. Optional: Access DataLayer variables like booking_page_name, step_name, or guests in your tag settings.

To verify: start GTM's preview mode and click once into a field on the booking page. booking_start and booking_page_view only show up in the preview after that.

What Data Is Not Transmitted?

Univents does not pass any personal data to the DataLayer:

  • No names
  • No email addresses
  • No phone numbers
  • No IP addresses
  • No customer IDs

booking_request_id is a technical identifier without any personal reference. All events are fully anonymized.

Frequently Asked Questions

I see no events in the DataLayer — why? Check in this order: did the visitor click Accept all in the cookie banner? Did they click or type on the page afterwards (no event before that)? Is a GTM container ID saved under Analytics? Is an ad blocker in the browser blocking the scripts? For a clean test, use an incognito window and accept there.

Can I extend the DataLayer events with custom data? Yes. In GTM you can add further DataLayer pushes via a “Custom HTML” tag — Univents events and your own events run in parallel.

Does this work with Meta? Yes. In your GTM tag, send generate_lead as the Meta event Lead — that is the standard name the Meta Conversion API and the Meta-Pixel understand. add_to_cart and purchase do not exist on booking pages.

Can I send personal data along with the events? No. This is not technically supported and would constitute a GDPR violation as well as a breach of Google's and Meta's platform policies.

Where do I find my GTM Container ID? In your GTM account, in the top right next to the container name — the format is always GTM- followed by 7 characters.

Univents newsletter

Three topics, pick any. Roughly once a month, no more.

Topics