This page gets you here: in Google Tag Manager, use the event names the platform already sends, and connect them to GA4 or a Google Ads conversion.
This page is not a switch, and it is not a performance report. The container ID is still entered only in Set up tracking and verification. Google Search clicks and impressions are in Connect Search performance.
Sidebar: Tracking event specs (/admin/settings/tracking-events). The Analytics block on Site SEO also has View platform tracking event specs.
Who can view it? Same as Site SEO. By default, the owner and site editors.
What is on the page
The admin page explains why GTM should be the only container, how to avoid double-counting with direct GA4, and the event names, triggers, and suggested GTM setup that are supported now. Parameter detail lives on that page. This handbook does not copy it again.
Event names are a contract shared across sites. Do not rename them (for example, do not change one to booking_success). The Custom Event name in GTM must match the name listed in admin, character for character.
A sensible order
- Enter the GTM container ID first. On Set up tracking and verification, fill Google Tag Manager container ID (recommended) and save. Keep GTM only, install GA4 and ads inside GTM, and do not also turn on the platform’s direct GA4.
- Open Tracking event specs. Use the sidebar item Tracking event specs, or the link on Site SEO. Expand Platform standard events and each event’s specs.
- Create the trigger and tag in GTM. Choose a Custom Event trigger, and set the event name to the one listed in admin (for example
generate_lead). Use a GA4 Event tag. For an ads conversion, markgenerate_leadas a Google Ads conversion. Do not use a Page View of the booking-success page as the conversion. - Check with GTM Preview or Tag Assistant. In a private window, walk the public site once (open a booking or a site form, submit it successfully, click a LINE contact). Confirm the events reach GTM, then publish the container.
Events that are sent today
Treat the Live status on that admin page as the source of truth. When this was written, these four were Live:
| Event name | When it is sent | Typical use |
|---|---|---|
view_booking_form | The visitor opens or sees a booking form they can fill (a standalone page, an embed, or a popup) | Top of the funnel: open → submit |
view_form | The visitor sees a site form they can fill (the contact page, a page embed, or a popup) | Top of the funnel: view → submit |
generate_lead | A booking is submitted successfully, or a site form is submitted successfully through the platform | GA4 Lead, Google Ads conversion. Use lead_type to tell booking from form |
contact_line | The visitor clicks through to a LINE official account, add-friend, or a lin.ee short URL (header, footer, shortcut button, page section, and similar) | Measure the LINE contact CTA |
Also:
generate_leadcovers a successful booking (lead_typeisbooking) and a successful site-form submit (lead_typeisform: Contact us, a page embed, or a popup). Opening the visitor’s email app, shop checkout, and HTML forms on a static site do not send it.view_formandview_booking_formare not sent twice in the same open. A booking also does not sendview_booking_formwhen the URL restores the success screen.contact_lineis not sent for Share to LINE, LINE Login, or account linking.- A shop purchase conversion is not a platform standard event yet. Do not assume the public site already sends
purchase.
Booking entry points are in Bookings, in brief. Site forms are in Forms, in brief. LINE shortcut buttons are in Set up shortcut buttons.
How to check
- Site SEO has GTM filled in. In a private window, page source or Tag Assistant shows the container.
- In GTM Preview, opening the booking form should show
view_booking_form; seeing a site form you can fill should showview_form; a successful booking or site-form submit should showgenerate_lead; clicking a LINE official-account link should showcontact_line. - Admin paths (
/admin) and preview pages are not treated as public tracking pages.
When it gets stuck
| What you see | What to do |
|---|---|
| The page is missing in admin | Permission is too narrow, or you are on another site or sidebar section. See A feature is missing from the sidebar. |
| GTM never receives the event | The container ID was not saved, the published container is a different one, or the trigger name is wrong (case and underscores must match exactly). |
| Traffic or conversions look doubled | Direct GA4 from the platform and GA4 inside GTM are both on. Remove one of them. See Set up tracking and verification. |
| You are waiting for a completed purchase to count as a conversion | Shop checkout does not send a platform event automatically today. A successful site-form submit is already generate_lead (lead_type is form). |
| A LINE click produced no event | The link is not an official account, add-friend, or lin.ee link (for example a share row, or login linking). |