Enhanced e-commerce data layer full documentation

This guide describes step-by-step how to migrate to the Google Analytics Enhanced E-commerce Tracking from the traditional E-commerce tracking, a new feature that SecuTix supports in Whymper V2. We recommend migrating your Google Analytics E-commerce today to take advantage of the new key features Prerequisite Please note that our Enhanced E-commerce Tracking is only supported if you are using Google Analytics tracking and Google Tag Manager. 1. Activate Enhanced E-commerce for the Point of Sales  Wait for a few minutes for the corresponding PoS to be updated with the latest parameters. Verification Once the PoS parameter is successfully updated, you could verify whether your activation works by doing a test purchase. When you reach the Confirmation Page of your test purchase, do the following: press the "F12" key to open the Console (or right click the mouse and choose "Inspect Element") type "dataLayer" in the Console and press the "Enter" key if you can find the JavaScript object called "ecommerce" inside the dataLayer object (as highlighted below), then that means the activation step works. 2. Activate En

New Google Analytics Reports If you activate Enhanced E-commerce in your Google Analytics Admin page, you will notice that Google now offers double the number of e-commerce reports compared to traditional e-commerce. However those new reports need the corresponding data to be properly tracked on the ticket shop side. With your best interests in mind, our goal is to track and send more detailed user online shopping engagement data in order to enable these new enhanced e-commerce reports one by one. With the release of Whymper V2, a first set of the new reports, including Order Coupon, Product Coupon, Affiliate Code and Product Brand reports, will finally be filled with the correct data! Traditional E-commerce  Enhanced E-commerce Measuring External Marketing Effort and Coupon Usage Do you ever wonder the following questions? How are my coupons (either at a product level or an order level) being used by online customers? How effective are these coupons? How often are they being used? You can now have a more insightful understanding on how well each of your promotional codes and advantages performs through the Order Coupon, Product Coupon reports. Order Coupon report groups and compares the sales by the promotional code used by the user at order-level (on Order Summary Page). Product Coupon report provides the same insights but for advantages used at the product-level. Both reports help you measure your external marketing effort in promoting the coupons and advantages and understand how they are used by users. Analyzing the data could also help you take necessary actions to improve the performance. Order Coupon Report Example Product Coupon Report Example Comparing Sales Performance Among Multiple Online Shops Besides measuring coupon usage, the new Affiliation report offers a way to easily compare sales performance among multiple online shops, if you have more than one configured. Affiliation Report Example Measuring Sales Performance At The Product Family and Topic Level The traditional e-commerce report offers sales performance comparison at the product level. But sometimes in order to observe the trend, it is also important to compare things at an aggregate level. The new Product Brand report is there to answer this need. Note that the brand of a ticket shop product is defined as "Product Family Type / Topic (if configured)". This report provides you possibilities to track e-commerce success of different product family and topic combinations and take actions if necessary.  Product Brand Report Example New DataLayer With the support of enhanced e-commerce data tracking, more accurate and detailed transaction data are added to the DataLayer, which is pushed every time when an online user pays for an order successfully and reaches the Order Confirmation Page.  On top of existing e-commerce data, the following new information are now tracked: Tax - the tax (VAT) amount of the order Order Coupon - the promotional code used by user to get a order-level discount on the Order Summary Page  Product Brand - information about product family type and topic of the product if a topic configured  Product Variant - information about the cross-selling type (including up-selling, cross-selling, cross-selling via one click, hit offer, post-selling) and ID of the parent product if a product is purchased via

Push contact's information (contact Number, hash Email) for all online journeys. Product details impression DataLayer Example <script> dataLayer.push ({ 'event':'ee-productClick' 'ecommerce':{ 'user':[{ 'contactNumber':'3010', // logged in's contact number 'hashEmail':'a73070283a933005e429eda4ad2e219ce304404dbd518dd6f9624e64a8ea52eb', // encrypted contact's email }] } }); </script> If you need the "hashEmail" field, please consult Share email of logged in internet user with third party software.

Impressions and clicks On the landing page : Clusters & sections views: push all products' impression data (including all products in the List view, even if the "Load more" button has not been clicked.) For the carousel or slider sections, we push all products inside the slider, no matter when user clicks on an arrow to see the other products or not. Meaning that if the product is in the slider, it will considered as an impression.)  Product type view: push all products belonging to the current Product Type selected (e.g push all products of the EVENT tab, when user clicks on the VISIT tab, and then pushing all VISIT tab products) On Landing page section view, sending data also depends on scroll depth. This means that the data will be pushed as the user scrolls the landing page. If a product card on the landing page is a Tour, we push the Tour id as the product Id. If a product card is a list of timeslots/performancse, we push its' product Id (Event Id or Visit pass Id). Data are also sent after user clicks on a product/promotion, and in the product/promotion details page (page just before the shopping cart) 1. Product impression Push product impression data to datalayer. Product impression DataLayer Example <script> dataLayer.push ({ 'event':'ee-productImpression' 'ecommerce': { 'impressions': [{ 'id':'12345678', // Product ID, Tour ID. If on landing display multiple timeslots or multipl

1. Add or Remove products from Cart Push data when a product is added to cart, or remove from cart Add to Cart DataLayer Example // Measure adding a product to a shopping cart // and a list of product. dataLayer.push({ 'event': 'addToCart', 'ecommerce': { 'currencyCode': 'EUR', // Currency code used for the PoS 'add': { // 'add' actionFieldObject measures. 'products': [{ // List of product items added to the shopping cart. 'name': 'Museum Pass', // Product Name 'id': '1234-567-987', // Unique SKU of the product item, i.e. product id - item id (if product is non-dated product) - performance id (if product is of event or parking or visit type) - seat category id - tarrif type id - timeslot id (if product is timeslot) - advantage id (if any) (same as enhanced e-commerce dataLayer) 'price': '15.25', // Unit Price 'brand': 'Visit Pass / Exhibition', // Product Family Type / Topic of the product (if set) (same as enhanced e-commerce dataLayer) 'category': 'Cat A / Normal', // Seat category / tarrif type 'variant': 'Cross-sell 1-click / 1234', // Cross selling type / parent product id (if added to cart via cross-selling) 'quantity': 1 // Quantity added to cart for this product item 'url': 'https://mosa.int1-shop.secutix.com/selection/timeslotpass?productId=101047223156' // URL pointing to the corresponding product item selection page which can be used by 3rd-party email retargeting tools

We've added a new parameter at point of sale level to define the way the data layer is structured for packages before sending the data to Google Analytics. With this new parameter, package quantity is calculated based on the number of tickets in the package before sending the data to Google Analytics.

The Tournament Lottery module also provide specific events to track the behaviour of users of the lottery module. Events that are tracked and pushed to the data layer are listed below. Event tracking on the application page Events are fired to track the progress of the user on the application page when creating and/or updating an application. Note that the events are designed to track the behaviour of the user on the screen as the lottery application page is a one-page-application where all interactions are purely handled on the front-end side until the submission. It is not intended to provide reliable information about actual, valid application content nor e-commerce-like tracking as they are fired upon clicks on the front-end application, before the data is ultimately saved at the end of the process. Event Event Category Event Action  Event Label Trigger APPLICATION_EVENTS 1 - Ticket request Confirm a ticket request Product type - Match - Category (e.g. IMT - Match 6 - Category 1) User adds or updates a ticket request to his application in the front-end APPLICATION_EVENTS 1 - Ticket request Edit a ticket request - Users clicks on edit on an existing ticket request within his application in the front-end APPLICATION_EVENTS 1 - Ticket request Delete a ticket request Product type - Match - Category (e.g. IMT - Match 6 - Category 1) Users clicks on delete on a ticket request in his application in the front-end APPLICATION_EVENTS 2 - Profile Details Edit profile details - User clicks on "Edit profile details" in his application in the front-end APPLICATION_EVENTS 2 - Profile Details Save profile details - User clicks on "Save" in the ticket details section of  his application in the front-end APPLICATION_EVENTS 3 - Submit Application Submit Clicked - User clicks on "Submit/Update" in his application to submit a new application or update its application  APPLICATION_EVENTS 3 - Submit Application Submit Succeeded - The submission of the application succeeds after the user clicks on "Submit/Update" (for new application and updates) APPLICATION_EVENTS 3 - Submit Application Submit Failed Error message The submission of the application failed after the user clicks on "Submit/Update" (for new application and updates) APPLICATION_EVENTS 4 - Reset Application The user withdraws his existing application by clicking on the delete button.