ZenotiHelp

Conversion tracking

ZTZenoti Docs Team Updated September 2, 2026 5 min readGuide

The Webstore supports conversion tracking through Facebook Pixel, Facebook Conversions API (CAPI), and GA4 to help you measure the effectiveness of advertising campaigns and attribute revenue to the correct channels.

Audience: Administrators and marketing managers who configure and monitor Webstore conversion tracking.


On this page


Before you begin

  • Conversion tracking requires configuration in the admin portal at Configuration > Online booking > Online booking settings > Webstore V2 > Analytics.
  • For Facebook tracking: have your Facebook Pixel ID ready. The field label in the admin portal is Facebook Pixel ID.
  • For GA4: have your GA4 Measurement ID ready.
  • Changes to tracking settings may take up to 30 minutes to propagate due to cache invalidation.

Facebook Pixel events

When configured, the Webstore fires two independently toggled event types. Both are enabled or disabled separately in Configuration > Online booking > Online booking settings > Webstore V2 > Analytics.

The following table describes each event, when it fires, and what data it carries.

Event Toggle name When it fires Transaction types Revenue parameters
Purchase event Purchase event Order confirmation page Service bookings, gift card purchases, membership purchases, series package purchases Yes β€” value and currency
Schedule event Schedule event Service booking confirmation page only Service bookings only No β€” no value or currency

Note: When both toggles are enabled, both the Purchase event and the Schedule event fire on the service booking confirmation page. For gift card, membership, and series package transactions, only the Purchase event fires β€” the Schedule event does not fire for those transaction types.

Tip: Use the Purchase event to measure revenue-generating conversions across all transaction types. Use the Schedule event to measure appointment volume independently of purchase value.

Worked example

Your organization runs a paid social campaign promoting a 60-minute facial. You enable both the Purchase event and the Schedule event toggles and enter your Facebook Pixel ID (for example, 654652347652578). When a guest completes the booking:

  • The Purchase event fires with value: 95.00 and currency: USD.
  • The Schedule event fires with no monetary parameters.

In Facebook Ads Manager, you can report on both the revenue attributed to the campaign (via Purchase) and the total appointment volume (via Schedule) as separate metrics.

Facebook Conversions API (CAPI)

The Webstore supports server-side event posting via the Facebook Conversions API. Conversion data is sent directly to the Facebook Graph API, bypassing the browser entirely.

This improves tracking accuracy in scenarios where browser-side tracking is restricted, including:

  • Guests using browsers that block third-party cookies
  • iOS 14+ environments subject to App Tracking Transparency restrictions
  • Ad blockers that prevent client-side pixel scripts from firing

Note: CAPI and browser-side Facebook Pixel can run in parallel. Running both is the recommended approach for maximum signal coverage and deduplication in Facebook Events Manager.

iOS 14+ compliance

Apple's App Tracking Transparency framework limits the conversion signals available to advertisers for iOS-targeted campaigns. To comply with Apple's Aggregated Event Measurement framework, you can configure up to 8 prioritized conversion events per domain in Facebook Events Manager.

Organizations running iOS-targeted paid campaigns alongside the Webstore should additionally consider:

  • Google Ads Enhanced Conversions β€” sends hashed first-party data for attribution. This is configured in your Google Ads account and is external to Webstore configuration.
  • Apple App Site Association file β€” supports App Tracking Transparency and SKAdNetwork attribution. This is tenant-managed and external to Webstore configuration.

Note: The Webstore data layer events feed these attribution mechanisms once they are configured on the respective platforms. The Webstore itself does not require additional configuration beyond enabling the relevant tracking toggles.

GA4 conversion events

The Webstore sends purchase and booking events to GA4, including revenue, transaction ID, and currency data. GA4 tracking uses the GA4 Measurement ID configured at the organization level.

Events are sent via the gtag function and include:

  • Revenue amount
  • Transaction ID
  • Currency code

Data layer variables

The Webstore exposes standard ecommerce variables for advanced Google Tag Manager (GTM)-based conversion tracking. These variables are available to GTM tags and triggers without additional configuration once GTM is connected.

The following variables are available in the data layer.

Variable Description
ecommerce.purchase.actionField.revenue Transaction revenue amount
ecommerce.purchase.actionfield.id Transaction ID
ecommerce.currencyCode ISO currency code for the transaction
eventtype Custom variable identifying the type of conversion event

Note: Do not reference or modify data layer variable names in help content or GTM configurations beyond what is listed here. Variable names are subject to change with Webstore releases.

Tips

  • Enable both the Purchase event and the Schedule event toggles if you want to report on appointment volume separately from revenue in Facebook Ads Manager.
  • Run Facebook Pixel (browser-side) and CAPI (server-side) in parallel to maximize signal coverage and reduce data loss from browser restrictions.
  • After saving any change to conversion tracking settings, allow up to 30 minutes before verifying that events are firing β€” the Webstore cache must invalidate before the new configuration is active.
  • Use the eventtype data layer variable in GTM to create separate tags for service booking conversions versus purchase conversions, enabling more granular campaign attribution.
  • If your organization runs iOS-targeted paid campaigns, configure Aggregated Event Measurement in Facebook Events Manager and prioritize your 8 conversion events by business value (for example, place the Purchase event at a higher priority than the Schedule event).

Troubleshooting

Purchase events are not firing after enabling the toggle. Allow up to 30 minutes for the cache to invalidate after saving the setting. If events still do not appear after 30 minutes, verify that the Facebook Pixel ID field in Configuration > Online booking > Online booking settings > Webstore V2 > Analytics contains the correct pixel ID with no extra spaces or characters.

The Schedule event is firing for gift card or membership purchases. The Schedule event fires only on the service booking confirmation page. It does not fire for gift card, membership, or series package transactions. If you are seeing unexpected Schedule events, verify that your Facebook Events Manager deduplication settings are not combining event types, and check that the pixel ID is not shared with another integration that fires Schedule events independently.

GA4 is not receiving purchase events. Confirm that the GA4 Measurement ID is entered correctly at the organization level. Also verify that the gtag script is loading on the Webstore confirmation page by checking your browser's network tab for outbound requests to google-analytics.com. If GTM is managing the GA4 tag, confirm that the GTM container is published and that the trigger fires on the confirmation page URL.

Data layer variables are not available in GTM. Confirm that the GTM container ID is configured at the organization level and that the container is published. Data layer variables are pushed at the time the confirmation page loads β€” if GTM loads after the page, the variables may not be captured. Use GTM's Preview mode to verify the sequence of events and data layer pushes on the confirmation page.

iOS 14+ campaigns show lower conversion counts than expected. This is expected behavior when App Tracking Transparency opt-out rates are high. Configure Aggregated Event Measurement in Facebook Events Manager and enable CAPI alongside browser-side pixel to recover server-side signals that are not subject to browser-level restrictions.

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