ZenotiHelp

Configure Webstore conversion tracking

ZTZenoti Docs Team Updated August 24, 2026 7 min readHow-to

Set up Google Analytics 4 (GA4), Google Tag Manager (GTM), and Facebook Pixel to track guest activity, measure conversions, and attribute revenue from your Webstore.

Note: For conceptual background on the Webstore and its configuration layers, see Webstore Overview.


On this page


Before you begin

  • You need configuration access in the Zenoti admin portal.
  • For GA4: have your GA4 Measurement ID ready.
  • For GTM: have your GTM container ID and the head/body code snippets ready.
  • For Facebook: have your Facebook Pixel ID ready. For server-side tracking, you need a Facebook Conversions API access token.

Steps

Follow the steps below to configure each tracking integration.

Configure GA4

  1. In Google Analytics, create or open the GA4 property for your Webstore.
  2. Copy the Measurement ID (format G-XXXXXXXXXX) from the GA4 property's Data Streams page.
  3. Navigate to Configuration > Online booking > Online booking settings > Webstore V2 > Analytics.
  4. Enter the GA4 Measurement ID.
  5. Select Save.
  6. After the cache propagation delay (up to 30 minutes), open the GA4 property's DebugView and complete a test booking on the Webstore. Verify that page-view and purchase events arrive in DebugView with the expected revenue, transaction ID, and currency.

The Webstore sends purchase and booking events to GA4 via the gtag function, including revenue, transaction ID, and currency data.

Cross-domain tracking (embedded Webstores)

If you embed the Webstore in your business website (iframe or subdomain), configure cross-domain tracking in GA4 to prevent session fragmentation when guests navigate from the parent site into the Webstore. Without it, a guest who arrives from a paid ad and traverses business-website β†’ Webstore appears in GA4 as two separate sessions, breaking ROAS attribution.

In GA4, navigate to GA4 > Admin > Data Streams > [your stream] > Configure tag settings > Configure your domains and add both your business website domain and the Webstore domain.

Worked example: Your business website is www.luxespa.com and your Webstore is hosted at book.luxespa.com. Add both domains to the GA4 cross-domain configuration. A guest who clicks a paid Instagram ad, lands on www.luxespa.com, then navigates to book.luxespa.com and completes a $120 facial booking is now attributed as a single session with $120 revenue β€” rather than two sessions with $0 and $120 respectively.

Configure Google Tag Manager

  1. Navigate to Configuration > Online booking > Online booking settings > Webstore V2 > Analytics.
  2. Enter the GTM Head Snippet β€” the code that goes in the <head> section.
  3. Enter the GTM Body Snippet β€” the code that goes in the <body> section.
  4. Select Save.

Both snippets are inserted into the Webstore pages at runtime.

Data layer events

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

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

The Webstore also fires four custom booking completion events:

  • bookingCompletedService
  • bookingCompletedGiftCard
  • bookingCompletedMembership
  • bookingCompletedPackage

Data layer variables

The data layer exposes standard ecommerce variables for advanced GTM-based conversion tracking:

  • ecommerce.purchase.actionField.revenue β€” Transaction revenue.
  • ecommerce.purchase.actionField.id β€” Transaction ID.
  • ecommerce.currencyCode β€” ISO currency code.
  • eventtype β€” Custom variable identifying the event type.

Tip: Zenoti provides a preconfigured JSON file containing approximately 35 ready-to-use GTM tags and triggers covering the standard Webstore events listed above. Contact your Zenoti representative for the current import file. Importing the package replaces hours of manual GTM tag creation and ensures coverage of all data layer events including the ecommerce events and custom booking completion events described above.

GA4 measurement is distinct from Google Ads conversion tracking. Organizations running paid Google Ads campaigns should additionally configure Google Ads conversion tracking so Smart Bidding strategies (Target ROAS, Target CPA) have data to optimize from.

  1. In Google Ads > Tools and Settings > Conversions, create a conversion action for the Webstore booking completion.
  2. Copy the Conversion ID and Conversion Label.
  3. In your GTM container, configure a Google Ads Conversion Tracking tag using the Conversion ID and Conversion Label, and trigger it on the booking-completion data layer event(s).
  4. Optionally, link your GA4 property to Google Ads (in the GA4 Admin β†’ Product Links β†’ Google Ads link) for imported conversions, so GA4 audiences and conversions can be used in Google Ads bidding.

Without Google Ads conversion tracking, ad spend efficiency suffers β€” Smart Bidding cannot optimize against unmeasured conversions.

Configure Facebook Pixel

  1. Navigate to Configuration > Online booking > Online booking settings > Webstore V2 > Analytics.
  2. Enter your Facebook Pixel ID in the Analytics section.
  3. Enable the Purchase event toggle to fire a Purchase event on the order confirmation page.
  4. Enable the Schedule event toggle to fire a Schedule event on the service booking confirmation page.
  5. Select Save.

The Webstore fires events based on the toggles you enable:

Event Confirmation page Transaction types Revenue parameters
Purchase Order confirmation Service bookings, gift card purchases, membership purchases, series package purchases Yes β€” value and currency
Schedule Service booking confirmation only Service appointments only No β€” no value or currency

Important: When both the Purchase event and Schedule event toggles are enabled, both events fire on the service booking confirmation page. The Schedule event does not fire for gift card, membership, or series package transactions.

Facebook Conversions API (CAPI)

For server-side event posting (recommended for iOS 14+ environments):

The Webstore supports Facebook Conversion API, which sends conversion data directly to the Facebook Graph API. This improves tracking accuracy for guests using browsers that restrict third-party cookies.

iOS 14+ compliance

For organizations targeting iOS users, configure up to 8 prioritized conversion events per domain in Facebook Events Manager to comply with Apple's Aggregated Event Measurement framework. Without this, conversion attribution from iOS guests is significantly under-counted, causing ad-bidding algorithms to undervalue iOS traffic.

For organizations running iOS-targeted paid campaigns, also consider:

  • Google Ads Enhanced Conversions β€” uses hashed first-party data (email, phone) to attribute conversions even when third-party cookies are unavailable. Configure in Google Ads > Conversions > [your action] > Enhanced conversions.
  • Apple App Site Association file β€” required if your business has an iOS app and you want SKAdNetwork attribution to flow through to ad campaigns.

These are tenant-managed and external to the Webstore configuration; the Webstore's data layer events feed these mechanisms once configured.

Note: Changes to analytics settings may take up to 30 minutes to propagate to the Webstore due to cache invalidation.

Tips

  • Use the preconfigured GTM package first. Before building custom GTM tags, import the Zenoti-provided JSON file (contact your Zenoti representative). The approximately 35 prebuilt tags cover all standard Webstore data layer events and save significant setup time.
  • Test in GA4 DebugView before going live. After saving your GA4 Measurement ID, wait up to 30 minutes for cache propagation, then complete a test booking. Confirm that purchase events appear in DebugView with the correct revenue, transaction ID, and currency values before directing real traffic.
  • Enable both Facebook event toggles for complete attribution. If you run paid campaigns that drive both service bookings and gift card or membership purchases, enable the Purchase event toggle to capture revenue across all transaction types. Enable the Schedule event toggle in addition if you want a separate signal for service appointment completions.
  • Configure cross-domain tracking for embedded Webstores. If your Webstore is embedded in or linked from your main business website, add both domains to GA4's cross-domain configuration to prevent session fragmentation and preserve accurate ROAS attribution.
  • Link GA4 to Google Ads for Smart Bidding. Importing GA4 conversions into Google Ads allows Smart Bidding strategies to optimize against actual booking revenue rather than proxy signals like clicks or page views.

Troubleshooting

Problem Likely cause Resolution
GA4 events not appearing in DebugView after saving the Measurement ID Cache has not yet propagated Wait up to 30 minutes after saving, then retest. Confirm the Measurement ID format is G-XXXXXXXXXX with no extra spaces.
Facebook Purchase event not firing on gift card or membership confirmation pages Purchase event toggle is disabled Navigate to Configuration > Online booking > Online booking settings > Webstore V2 > Analytics and confirm the Purchase event toggle is enabled.
Facebook Schedule event firing on gift card or membership confirmation pages Expected behavior misunderstood The Schedule event fires only on the service booking confirmation page. It does not fire for gift card, membership, or series package transactions β€” this is by design.
GTM tags not firing after entering head and body snippets Snippets entered in wrong fields, or cache delay Confirm the head snippet is in the GTM Head Snippet field and the body snippet is in the GTM Body Snippet field. Wait up to 30 minutes for cache propagation. Use GTM Preview mode to verify tag firing.
Custom booking completion events (bookingCompletedService, etc.) not visible in GTM GTM container not configured to listen for these events Import the Zenoti-provided preconfigured JSON file, or manually create GTM triggers listening for these custom event names. Contact your Zenoti representative for the current import file.
Revenue data missing from GA4 purchase events GA4 Measurement ID saved but gtag not receiving data Verify the Measurement ID is correct and that no browser extensions (ad blockers) are interfering during testing. Use an incognito window without extensions for DebugView testing.
Was this article helpful?
Your feedback helps us improve our documentation.