This feature can be used with the following license packs: Professional, Enterprise

 

Introduction

This document serves as an instruction for implementing Google Tag Manager (GTM) and Google
Analytics (GA) to Lyyti services.

Create a new GTM container inside your account for Lyyti services. It is not advisable to add
customer site GTM tag to the lyyti.fi site.

Adding your site's own GTM container to Lyyti will make tag management of two different domains
complex.

If GA is used, cross domain tracking should be enabled as GA is unable to link users on different
domains. Successful cross domain tracking will require some modifications to customer GTM
container.

The following document describes tags, triggers and variables that are required for successful GTM + GA tracking between the customer site and lyyti.fi.

This document also contains analysis on the current GTM setup on the lyyti site.

Lyyti container configuration

The following configuration is required to the GTM container that will be installed to Lyyti site by the customer. A new container can be created in the GTM admin section. Remember to create the
container to the same account where the customer's website container is located.

 

Variables to the Lyyti container

The following variables are required for the implementation of GA tracking to the Lyyti site.

 

Google Analytics Settings variable

The Google Analytics Settings variable contains all the settings that are required for page view, event and ecom tracking. The Settings variable content for this implementation is slightly different from the standard because cross-domain tracking will be used.

For this implementation the settings variable should have the following configuration:

Name: [UA – Lyyti]

Tracking ID: [UA-XXXXXXX-X]
This should contain the Google Analytics property ID where customer is currently sending
data.

Cookie Domain: [auto]

Fields to set:

Field name	Value
allowLinker	true

 

This setting will allow Google to establish domain linking

Cross Domain Tracking: [customerSite.com, lyyti.in, lyyti.fi]
This should contain the customer domain name that contains the link to the lyyti site. If a lyyti.in link is used in customer site then lyyti.in domain should be added to the domain name list separated with a
comma.

 

Data Layer variable - page

For the actual event registration we require the page to be captured from data layer. This data layer variable (DLV) will be used to create the trigger for a registration. The variable contains the page name that is pushed into the data layer by Lyyti. 

Variable Type: Data Layer Variable
Name: DLV – pageName
Data Layer Variable Name: page
Data Layer Version: 2

 

Tags to Lyyti container

UA tag with cross domain enabled

This tag should fire on all pages so a predefined ”all pages” trigger should be used.
Data from the  Lyyti site should go into the same GA property as the customer site data.
Use the Google Analytics Settings variable (UA - Lyyti) that was defined in section
2.1.

Tag type: Google Analytics – Universal Analytics
Name: UA – Page View
Track Type: Page View
Google Analytics Settings: UA – Lyyti
Use the settings variable that created in section 2.1.1.
Trigger: All Pages
Use the automatically generated all pages trigger.

Event for successful registration

This tag should be fired when a user completes their registration. The tag requires a separate
trigger.

Tag type: Google Analytics – Universal Analytics
Name: UA – Event for registration
Track Type: Event
Event Category: Registration

Event Action: Sent
Event Label: [descriptive event name]
Google Analytics Settings: UA – Lyyti
Use the settings variable that created earlier.
Trigger: Event registration
(See below)

An event registration trigger

A registration trigger should be created so that it will fire the registration tag event when a user
has completed the registration process. Current data layer implementation does not allow for a
simple solution for tracking individual Lyyti events.

 

Event type: Page View – DOM Ready

This trigger will fire on:

DLV - pageName

equals

done

 

Customer site container configuration 

Customer's current GTM container requires modification in order for the cross domain
tracking to work between lyyti.fi and the customer site.

Variables to the customer container

The following variables are required for the implementation of GA tracking to the customer site.

Google Analytics Settings variable

Customer site container requires its own settings variable that will differ from the lyyti.fi
container variable. Cross-domain tracking will also require some additional parameters.  A new
variable is not required if the container already has this variable. Make sure the existing variable
follows the configuration below.

The settings variable should have the following configuration:

Name: [UA – ID]
Tracking ID: [UA-XXXXXXX-X]
This should contain the Google Analytics property ID. This ID has to be the same as in the Lyyti
container.
Cookie Domain: [auto]
Fields to set:

Field name	Value
allowLinker	true

 

 

This setting will allow Google to establish domain linking.

Cross Domain Tracking: [lyyti.fi, lyyti.in]
This should contain the Lyyti domain name. If lyyti.in link or lyyti.com is used in the customer site then those domains should also be added to the domain name list separated with a comma.

Tags to customer container

Customer site container only requires Google Analytics page view tag in order for the
cross-domain tracking to work. All customers using Google Analytics already have this tag
so if a tag exists it is not necessary to create a new one. Make sure the configuration
variable follows the configuration described in the previous section.

UA tag with cross domain enabled

This tag should fire on all pages so a predefined ”all pages” trigger should be used.
Data from the customer site should go into the same GA property as the lyyti.fi data.
Use the Google Analytics Settings variable (UA – ID ) 

Tag type: Google Analytics – Universal Analytics
Name: UA – Page View
Track Type: Page View
Google Analytics Settings: UA – ID
Use the settings variable that created in section (Google Analytics Settings variable)

Trigger: All Pages
Use the automatically generated all pages trigger.

Google Analytics configuration

Customer's current Google Analytics account requires modifications in order for the cross-
domain tracking to work. Below are the most important configuration items that need to be in
place.

Property and view structure

Each property should have at least two views, one for unfiltered and one for filtered data. Google
offers the following view structure it would like GA users to use. All goals should be
created to User data view.

 

Property	View name	Global Settings
CustomerSite.com	00 Master data - customerSite.com MM/YY	No filters in this view.
CustomerSite.com	01 Basic data - customerSite.com MM/YY	Bots, internal traffic filtered.
CustomerSite.com	02 User data - customerSite.com MM/YY	Same than 01 but custom filtering, goals etc.

 

Property settings

Property (domain level) settings should use the following configuration:

Property Name: [customerSite.com]
Default URL: [customerSite.com]
Default View: [Main reporting view]
User data view that was described in earlier section should be used here.
Industry Category: [Customers industry]
Enable Demographics and Interest Reports:

View settings

View settings for Master data and User Data are rather similar excluding bot filtering that
should not be enabled for Master data.

Configuration:

View Name: [Descriptive view name]
View naming that was described earlier can be used here too
Website’s URL: [customerSite.com]
Use customers site URL in here.
Time zone country or territory: [e.g. Finland]
Use customers country.
Currency displayed as: [e.g. EUR]
Use customers currency.
Bot filtering: [enable]
Remember not to enable this in Master Data view.
Query parameter: [Parameter for internal search query]
This can be left empty if no parameter is set in URL.

Referral exclusion

Referral exclusion list needs to contain both Lyyti (if redirect from lyyti.in is used) domains
and the customerSite.com domain in order for the cross-domain tracking to work.
Referral exclusion is done on a property level.
Exclusion lists can be found from the admin panel: Tracking Info -> Referral Exclusion List

Conversion for registration

In order to use GA conversion reporting a goal needs to be created to User Data
reporting view.

We need to use the event that was created previously. Goals are created in view
level and configuration can be found from Admin panel -> Goals
Goal for the event that we created should use the following configuration:

Custom Goal
Goal Name: [Descriptive name for the event]
Goal Slot ID: [Select the first free goal ID]
Remember not to overwrite existing ones.
Type: Event

Category	Equals to	Registration
Action	Equals to	Sent
Label	Equals to	Aamupala

Values that were given in section "Event for successful registration" for the event should be used here.

Tracking ticket revenue

When customer uses the possibility to order tickets from Lyyti then GA Ecommerce setup
needs to be in place. An efficient way of collecting ecommerce data requires the creation of a data
layer push that contains product info, amount of tickets and revenue. This event needs to be
sent after the actual purchase. Created tags capture the ecommerce data after the feature has been enabled. 

https://support.google.com/tagmanager/answer/6107169?hl=en