Prerequisite
Please note that our Enhanced E-commerce Tracking is only supported if you are using Universal Analytics tracking and Google Tag Manager. If you have not yet activated the Enhanced E-commerce Tracking, please get in touch with our service team to ensure a proper setup.
You are a strong user of the Google Analytics enhanced e-commerce tracking and you want to gain a deeper understanding of your visitors behavior especially on the calculated season tickets sales. Our Enhanced E-commerce feature has been further extended and is here to provide you with all those details.
Following the deliveries of Cart and user info tracking on Enhanced E-commerce in Whymper V3 and Google Analytics improved data layer for products and checkout in Bishorn V1, we have continued our journey to enrich the e-commerce tracking data for our online sales platform in Bishorn V2. This time, we focus on understanding your season ticket holders journey.
Product families supported
Applies for all internal sales channels that enables the pos-param "Enable enhanced e-commerce tracking", applies for all product families (includes Season ticket, Hospitality)
The SecuTix data layer is not pushing data on the self-exchange online pages.
1.Contact number and order type available to all data pushes existing already
2.Push date time of dated product from addToCart datalayer to all
For dated product (match, performance, timeslot) a new field "date" in addTocart and later processes like checkout and confirmation is added
3a.Push data for Subscription journey
A new datalayer addSubscription is now available when purchasing a season ticket.
Data are pushed to the data layer first once a visitor enters the Season ticket first page (product description page) and second after the vistor clicks on "Subscribe now".
3b. A new datalayer validateSubscription and cancelSubscription are available
- validateSubscription is fired when user confirms the Subscription (click on VALIDATE SUBSCRIPTION)
- The data are pushed again if the user modify seats of some performances and VALIDATE again
3c. A new datalayer cancelSubscription is fired when the visitor cancel the Subscription (same structure and data as validateSubscription except the event cancel is pushed)