ZenotiHelp

GA4 and Google Tag Manager integration

ZTZenoti Docs Team Updated September 2, 2026 7 min readGuide

The Webstore integrates with Google Analytics 4 (GA4) and Google Tag Manager (GTM) to track guest behavior, measure conversions, and support paid advertising campaigns.

Audience: Webstore administrators and marketing teams responsible for analytics configuration.


On this page


Before you begin

  • You need configuration access in the Zenoti admin portal to set up analytics integrations.
  • For GA4: create a GA4 property in your Google Analytics workspace and have your Measurement ID ready (format: G-XXXXXXXXXX).
  • For GTM: have your GTM container head and body code snippets ready from your GTM workspace.
  • Changes to Webstore analytics settings may take up to 30 minutes to propagate due to cache invalidation.

Connect GA4 to the Webstore

  1. In the Zenoti admin portal, navigate to Configuration > Online booking > Online booking settings > Webstore V2 > Analytics.
  2. Enter your GA4 Measurement ID in the designated field (format: G-XXXXXXXXXX).
  3. Save your changes.
  4. To verify the connection, open GA4 DebugView in your Google Analytics workspace and complete a test booking on the Webstore. Confirm that page view and conversion events appear in DebugView.

Note: Changes take up to 30 minutes to appear on the Webstore due to cache invalidation.

Tip: The GA4 Measurement ID is found in your Google Analytics workspace under Admin > Data Streams > [your stream] > Measurement ID.

Set up Google Tag Manager

  1. Navigate to Configuration > Online booking > Online booking settings > Webstore V2 > Analytics.
  2. Paste your GTM container head code snippet into the head snippet field.
  3. Paste your GTM container body code snippet into the body snippet field.
  4. Save your changes.

Both snippets are inserted into Webstore pages at runtime. After saving, allow up to 30 minutes for the changes to take effect.

Data layer events

The Webstore pushes ecommerce events to the GTM data layer in the Universal Analytics enhanced ecommerce format. The following events are included:

Event When it fires
Product Impressions When services, memberships, or packages are displayed to the guest
Add to Cart When a guest adds an item to their booking
Remove from Cart When a guest removes an item from their booking
Checkout When the guest enters the checkout flow
Purchase When a transaction completes successfully

The Webstore data layer also emits additional events that can be used for detailed funnel analysis. The following events include relevant ecommerce parameters such as transaction ID, revenue, currency, and item details where applicable:

Event Description
webstore_page_view Guest views a Webstore page
service_view Guest views a service detail
provider_selected Guest selects a provider
time_selected Guest selects a time slot
addon_added Guest adds an add-on to their booking
checkout_started Guest begins the checkout flow
purchase_completed Guest completes a purchase
login_completed Guest signs in to their account
register_completed Guest signs up for a new account
waitlist_joined Guest joins a waitlist
gift_card_purchased Guest purchases a gift card
membership_purchased Guest purchases a membership
series_package_purchased Guest purchases a series package

Note: The event list above is representative. Additional events may be present depending on your Webstore configuration.

Custom booking completion events

Four custom events fire via the data layer when a booking is completed. Use these events in GTM to trigger tags specific to each booking type:

Event name Fires when
bookingCompletedService A service booking is confirmed
bookingCompletedGiftCard A gift card purchase is completed
bookingCompletedMembership A membership purchase is completed
bookingCompletedPackage A series package purchase is completed

These events map to the tags included in the preconfigured GTM import package described below.

Import the preconfigured GTM package

Zenoti provides a preconfigured JSON file containing approximately 35 ready-to-use GTM tags and triggers that cover the standard Webstore events. Importing this package into your GTM container reduces setup time and ensures the tags are correctly mapped to the Webstore data layer events.

To obtain the import file, contact your Zenoti representative.

To import the package into GTM:

  1. In your GTM workspace, select the container where you want to import the tags.
  2. Navigate to Admin > Import Container.
  3. Upload the JSON file provided by your Zenoti representative.
  4. Choose whether to merge with or overwrite existing tags, then confirm the import.
  5. Publish the container to make the tags active.

Tip: Import the package into a GTM preview environment first to verify tag firing before publishing to production.

Worked example: An organization imports the Zenoti GTM package and sees 35 tags created, including tags for bookingCompletedService (mapped to a GA4 event tag), purchase_completed (mapped to a Google Ads conversion tag with Conversion ID AW-123456789 and Conversion Label abc123), and gift_card_purchased (mapped to a Facebook Pixel event). The organization publishes the container and verifies all three tags fire correctly using GTM Preview mode during a test booking.

Configure cross-domain tracking

If your Webstore is embedded within your business website using an iframe or subdomain configuration, guests navigate between your parent site domain and the Webstore domain during a session. Without cross-domain tracking, GA4 treats this as two separate sessions, fragmenting your analytics data.

To configure cross-domain tracking in GA4:

  1. In your Google Analytics workspace, navigate to Admin > Data Streams > [your stream] > Configure tag settings > Configure your domains.
  2. Add both your parent site domain and your Webstore domain to the domain list.
  3. Save your changes.

After configuration, GA4 recognizes cross-domain sessions as a single continuous session, preserving traffic source attribution across the guest's booking journey.

Set up Google Ads conversion tracking

If you run paid Google Ads campaigns, configure Google Ads conversion tracking separately from GA4 measurement. Google Ads conversion tracking is required for Smart Bidding strategies such as Target ROAS and Target CPA to function effectively.

To set up Google Ads conversion tracking:

  1. In your Google Ads account, create a conversion action for Webstore bookings and note the Conversion ID and Conversion Label provided.
  2. In your GTM container, configure the corresponding Google Ads conversion tag using the Conversion ID and Conversion Label from step 1. Map the tag to the appropriate booking completion event (for example, bookingCompletedService or purchase_completed).
  3. Publish the GTM container.
  4. In your Google Analytics workspace, link your GA4 property to Google Ads by navigating to Admin > Google Ads Links and following the linking steps. This enables imported conversions from GA4 to appear in Google Ads.

Note: Google Ads conversion tracking and GA4 measurement serve different purposes. GA4 provides behavioral analytics; Google Ads conversion tracking feeds bidding algorithms. Both are recommended for organizations running paid campaigns.

Tips

  • Verify tag firing with GTM Preview mode before publishing your GTM container to production. GTM Preview mode shows which tags fire on each Webstore page and event, helping you catch misconfigured triggers before they affect live data.
  • Use GA4 DebugView for end-to-end testing. After configuring your GA4 Measurement ID, complete a full test booking on the Webstore while DebugView is active. Confirm that events such as checkout_started and purchase_completed appear with the correct parameters.
  • Configure cross-domain tracking before launching campaigns. If your Webstore is embedded or hosted on a subdomain, set up cross-domain tracking in GA4 before driving paid traffic. Without it, traffic source attribution is lost when guests move from your parent site to the Webstore domain, making campaign performance data unreliable.
  • Keep your GTM import package current. When Zenoti releases updates to the preconfigured GTM package, contact your Zenoti representative to obtain the latest version and re-import it into your GTM container to ensure all new Webstore events are covered.
  • Link GA4 to Google Ads for imported conversions. Even if you configure Google Ads conversion tags in GTM, linking your GA4 property to Google Ads gives you a secondary conversion source and enables audience-based remarketing using GA4 segments.

Troubleshooting

GA4 events are not appearing in DebugView after saving the Measurement ID. Allow up to 30 minutes for the Webstore cache to clear after saving analytics settings. If events still do not appear after 30 minutes, confirm that the Measurement ID is entered correctly in Configuration > Online booking > Online booking settings > Webstore V2 > Analytics and that the GA4 property is active in your Google Analytics workspace.

GTM tags are not firing on the Webstore. Confirm that both the head and body GTM code snippets are saved in the Webstore analytics configuration. Use GTM Preview mode to verify that the GTM container is loading on Webstore pages. If the container does not appear in Preview mode, check that the snippets were copied in full from your GTM workspace without truncation.

Cross-domain sessions are still appearing as separate sessions in GA4. Verify that both your parent site domain and your Webstore domain are listed under Admin > Data Streams > [your stream] > Configure tag settings > Configure your domains in GA4. Ensure the GTM container is published after any tag or trigger changes, as unpublished changes do not affect live traffic.

Google Ads Smart Bidding is not optimizing as expected. Confirm that your Google Ads conversion action is correctly mapped to a GTM tag that fires on booking completion events. Verify that the GTM container is published and that the conversion tag is firing in GTM Preview mode during a test booking. Also confirm that your GA4 property is linked to Google Ads under Admin > Google Ads Links.

The bookingCompletedService event fires but the purchase_completed event does not. These are separate events that fire in different contexts. bookingCompletedService fires on service booking confirmation; purchase_completed fires when a transaction is finalized at checkout. Verify that your GTM triggers are mapped to the correct event names and that the guest completed the full checkout flow during your test.

Was this article helpful?
Your feedback helps us improve our documentation.