v1.0.2 - October 2026
Last updated: October 26, 2026
Release date: 31 October 2026
Status: Upcoming release
This release adds standardised ecommerce tracking for the Booking Site and printable membership cards, alongside fixes to recurring membership payments, booking and checkout behaviour, and online card visibility.
Summary
Category | Summary |
|---|---|
Analytics and tracking | Google Tag Manager and GA4 ecommerce events enabled for all Booking Sites |
Memberships | Printable membership card PDFs with QR codes |
Payments | Recurring membership payment fix (Adyen) |
Bookings and checkout | Duration retention, single-option visibility and embedded webview fixes |
Cards and integrations | Online card visibility and Sacoa history fixes |
New Features
Analytics and tracking
Google Tag Manager and GA4 ecommerce tracking
The Booking Site now pushes a standard set of ecommerce events to the Google Tag Manager data layer for GA4, covering the full journey from browsing options through to order confirmation. Every event carries a unique event identifier and timestamp, the ecommerce payload is cleared before each new ecommerce event, and item events are not sent when there are no recognised items.
Events
Event | When it fires | What it includes |
|---|---|---|
| On page load and when booking or marketing-consent state changes | Identification state, marketing opt-in, previous booking count and optional hashed matching data |
| When a booking, product or gift-voucher list is shown or refreshed | Venue, currency, list and visible items, including booking date, time and duration where available |
| When a customer selects an option or increases it from zero | Selected item, list and position |
| When a successful cart refresh shows increased quantities | Added quantities and combined item value (the first cart snapshot sets a baseline and does not fire) |
| When a successful cart refresh shows reduced quantities | Removed quantities and combined item value |
| Once, when an eligible payment page is reached with cart items | Item subtotal, grand total, tax, shipping, transaction fee, discount, coupon and items |
| Once, when the selected payment workflow starts processing | Checkout values and normalised payment type (Credit Card, Apple Pay, Google Pay, Afterpay, PayPal) |
| Once, on an eligible order confirmation page | Order number, payment reference, payment type, subtotal, grand total, tax, shipping, fees, discounts, coupons and items |
| On page load after a successful member login | User type only; no personal data |
Defaults and controls
Tracking is on for all Booking Sites after this release, with all nine events enabled.
To disable all tracking, set
window.venueSumoTrackingAutoEnabled = falsebefore the tracking scripts load, or ask VenueSumo to apply it for you.Known email, name and phone values are only ever included as normalised SHA-256 hashes. Plain-text contact details are never sent.
valueis the item subtotal;grand_totalis the complete order total. Choose which your GA4 revenue mapping uses and apply it consistently.
Memberships
Printable membership cards
Authorised staff can generate a membership card PDF, including a QR code, from a member’s details, from an individual membership on an order, or for every assigned membership on an order in one PDF. Cards use the venue’s active Member Card template. Memberships without an assigned member are skipped.
Fixes
Payments
AdyenDeclined or non-authorised recurring membership payments are now recorded as failed, with the refusal reason where available, instead of being marked successful.
Bookings and checkout
A facility with only one available booking option now keeps that option visible.
Loading additional booking dates retains the duration the customer already selected.
Generic embedded webviews no longer receive the open-in-another-browser prompt. Named social and messaging app browsers, such as Meta and Instagram, still do.
Payment pages stay within the integrated checkout when the provider does not require an external redirect.
Cards and integrations
Card products stopped for sale, or restricted to Back Office, no longer appear online.
Card categories with no available online products are hidden from customers.
Sacoa card history preserves fractional quantities and displays monetary values consistently.
After Updating
Check for duplicate purchase events. Existing footer purchase scripts and GTM tags listening to older purchase flows will keep running. Compare them against the new
purchaseevent and remove or disable the old tracking.Validate the GTM container before reporting. Walk a test booking through list, selection, cart, checkout, payment and confirmation with GTM Preview connected and confirm each event fires once, in order.
Reconcile revenue. If GA4 revenue differs from VenueSumo, check whether the tag maps to
valueorgrand_total, then fees, shipping, discounts and coupons.Membership card action missing? Check role access (View Member Cards) and that the Member Card template is active. A blank QR code points to the template content or the member value it reads.