| Note |
|---|
|
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. |
| Excerpt |
|---|
| Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | NEW V2.6 |
|---|
|
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. |
| Info |
|---|
| title | 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. |
| Code Block |
|---|
| language | js |
|---|
| title | Product click DataLayer Example |
|---|
| collapse | true |
|---|
|
event:"ee-productClick"
ecommerce:Object
click:Object
user:Object
contactNumber:"3010" // add the contactNumber after user logged in, this can be empty due to guest
hashedEmail:".." // only push when activate webTracking.userInfoTrackingType
actionField:Object
list:"Plan your visit"
products:Array[1]
0:Object
id:"101061827659"
name:"West Hall - Guided visit"
brand:"Visit pass"
variant: "SALE" // add the orderType from the action productClick (exclude datalayers which already done)
position:0 |
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
| Code Block |
|---|
| language | js |
|---|
| title | Checkout DataLayer Example |
|---|
| collapse | true |
|---|
|
event:"ee-checkout"
ecommerce:Object
checkout:Object
user:Object
contactNumber:"3010"
actionField:Object
products:Array[3]
0:Object
name:"Museum Ticket"
date:"15/04/2021 - 15:30" //date time of timeslot, performance, match
category:"Adult"
price:"14.00"
quantity:2
id:"101049282449-101049310928-306159078-101049317318"
brand:"Visit pass"
variant:"SALE" |
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".
| Code Block |
|---|
| language | js |
|---|
| title | AddSubscription DataLayer Example |
|---|
| collapse | true |
|---|
|
event:"ee-addSubscription"
ecommerce:Object
add:Object
user:Object
contactNumber:"3010"
products:Array[1]
0:Object
id:"466508722"
name:"Open Season Ticket"
brand:"Season tickets"
quantity:2
variant:"SALE" |
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
| Code Block |
|---|
| language | js |
|---|
| title | validateSubscription DataLayer Example |
|---|
| collapse | true |
|---|
|
event:"ee-validateSubscription"
ecommerce:Object
currencyCode:"EUR"
validate:Object
user:Object
contactNumber:"3010"
products:Array[1]
0:Object
id:"466508722"
name:"Open Season Ticket"
brand:"Season tickets"
quantity:2
variant:"SALE"
performance:Array[3]
0:Object
id:"466498532"
name:"Swan Lake"
date:"15/04/2021 - 15:30"
category:"Cat 1 / Subscriber - Adult"
price:"14.00"
quantity:1
brand:"Event"
variant:"SALE"
1:Object
id:"466498533"
name:"La Travia"
date:"16/04/2021 - 15:30"
category:"Cat 1 / Subscriber - Adult"
price:"14.00"
quantity:1
brand:"Event"
variant:"SALE"
2:Object
id:"466498535"
name:"Romeo&Juliet"
date:"17/04/2021 - 15:30"
category:"Cat 1 / Subscriber - Adult"
price:"14.00"
quantity:1
brand:"Event"
variant:"SALE" |
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)
| Code Block |
|---|
| language | js |
|---|
| title | cancelSubscription DataLayer Example |
|---|
| collapse | true |
|---|
|
event:"ee-cancelSubscription"
ecommerce:Object
currencyCode:"EUR"
cancel:Object
user:Object
contactNumber:"3010"
products:Array[1]
0:Object
id:"466508722"
name:"Open Season Ticket"
brand:"Season tickets"
quantity:2
variant:"SALE"
performance:Array[3]
0:Object
id:"466498532"
name:"Swan Lake"
date:"15/04/2021 - 15:30"
category:"Cat 1 / Subscriber - Adult"
price:"14.00"
quantity:1
brand:"Event"
variant:"SALE"
1:Object
[...] |
| Code Block |
|---|
| language | js |
|---|
| title | addToCart DataLayer Example |
|---|
| collapse | true |
|---|
|
event:"addToCart"
[...]
name:"Open Season Ticket"
brand:"Season tickets"
quantity:2
variant:"SALE"
performance:Array[3]
0:Object
id:"466498532"
name:"Swan Lake"
date:"15/04/2021 - 15:30"
category:"Cat 1 / Subscriber - Adult"
price:"14.00"
quantity:1
brand:"Event"
variant:"SALE"
1:Object
id:"466498533"
name:"La Travia"
date:"16/04/2021 - 15:30"
category:"Cat 1 / Subscriber - Adult"
price:"14.00"
quantity:1
brand:"Event"
variant:"SALE"
2:Object
id:"466498535"
name:"Romeo&Juliet"
date:"17/04/2021 - 15:30"
category:"Cat 1 / Subscriber - Adult"
price:"14.00"
quantity:1
brand:"Event"
variant:"SALE" |
Before starting with the content:
- Title should be concise, in the same style as the other title. Keep in mind that we are showing both the title and the excerpt below on the release note page - so no need to be too long. Always create the page first in the "Work in progress (not public)" page, "Sprint x -" prefix and inside one of the "component (WIP)" page. If you feel a component is missing, ask GTH.
- Put labels on the page, especially the ones used in the "Guide" section. This will make your release note show up in the Guide section of the website.
- Delete this instructions of course
Context
| Excerpt |
|---|
| MANDATORY - Short description of the business need, value and high-level solution, written from the perspective of an operator. Keep it concise and put the new feature in the business context of customers. Status should be for features released in more than one sprint, | Status |
|---|
| subtle | true |
|---|
| colour | Blue |
|---|
| title | UPCOMING |
|---|
|
for features coming in the current sprint. Feel free to add a second tag in front of a second paragraph if you re-use the page over several sprints. |
Solution
RECOMMENDED - Description in more details about what the feature is. Keep it more operator-oriented, not overly "marketing".
| Warning |
|---|
| title | Important information |
|---|
|
Communicate also in this section important limitations or information that the customer should not miss. |
| Info |
|---|
|
Use info box if you want to highlight a particular point. |
Getting started
MANDATORY - What is the setup required to use the feature (even if none, please mention)? Where can I see the feature? (this is intended to be a short guide). At least one screenshot should be provided, at latest for the finalized release note at sprint end.
Examples
...
