Within Nutickets, there are 2 methods by which you can integrate with your analytics.


The first method is to use Nutickets’ standard templates; this will use a pre-set code within the system to pass information through to your tracking system (Basic).


The second method is to use your own custom code in conjunction with Nutickets’ pre-set variables (Advanced).

We have outlined both methods below.


Pre-set Nutickets Web Analytics


You can apply Web Analytics in two areas:


  • Account Settings


Adding Web Analytics in the account settings area will apply the analytics across your entire account. 


  • Event Settings


Adding Web Analytics in the event settings area will apply the analytics to a specific event. 


To apply Web Analytics to your whole account go to: Dashboard > My Account > Web Analytics



To apply Web Analytics to a specific event, go to: Events > Manage Events > Select your event > Advanced >  Web Analytics


You then have two options:


  1. Add Analytics


    This will use Nutickets' pre-set Web Analytics variables (Basic)


  2. Templates 


    This will allow you to add your own custom code in conjunction with Nutickets’ pre-set variables (Advanced)


BASIC SETUP

 

Click on Add Analytics to open the below box:



Type ID and Tracking ID or Code


The Type ID refers to which provider you use for Web Analytics. There are a number of options available:


Google Tag Manager, Adobe Analytics, Twitter and Facebook Pixel.



Select a type ID, then - you need to add your Tracking ID or Code.


This is the code generated by your chosen Web Analytics provider.


What pages are covered? Page ID


The chart below displays all the variables, and which pages will be tracked.



This completes the basic method...


If you require more precision within your analytics you can use Nutickets' second method and code your own analytics.


NOTE


Without coding knowledge or an understanding of advanced analytics, we recommend that you avoid using the custom analytics feature.


Errors can lead to issues with your booking engine and can even cause your booking engine to fail.



ADVANCED SETUP


Click ‘Templates’ and the below box will appear.



Click ‘Templates’ And you will see the below box appear.



Click 'Add Template' and fill the required fields: Template name and content.



In content field you can add any java script.


Be aware not to add the tags in <script>.


If you copy and paste code this will likely by surrounded by tags. Within your code you can add placeholders that will be replaced with the matching values. Variable names should be surrounded by % marks i.e. %VARIABLE_EXAMPLE%. If value is not set (i.e. you try to use EVENT_ID variable on the event list page) we put a false boolean value. Full list of available values is documented at the end of this document.


Example Adobe Analytics:


alert('hello event' + '%EVENT_NAME%');
s.prop0 = %EVENT_ID%;
s.prop1 = '%TRANSACTION_REFERENCE%';

//You can also define a special callback function 'eventClickTracking' which will be called when you click an event on event list or map:
function eventClickTracking(link, clickSource, eventID) { 
    //…
}

//This function should be placed in a template attached to Event List page.


After you save your template you can click the Add Analytics button:



You can now attach the previously created templates to the pages:



List of available variables


EVENT_NAME i.e. „Test event”

EVENT_ID i.e. 82372

TRANSACTION_ID i.e. 12863723

TRANSACTION_REFERENCE i.e. „SRP-1F7FAC18AD”

TRANSACTION_TOTAL i.e. 14.20

PAGE_NAME i.e. „Example page”

PAGE_ID i.e. 123

ISO_CURRENCY_CODE i.e. „GBP”

ISO_COUNTRY_CODE i.e. „GB”

EMAIL_OPT_IN „Yes” or „No”

SMS_OPT_IN „Yes” or „No”

TELEPHONE_OPT_IN „Yes” or „No”


Variable output examples Adobe Analytics: (check console, usually F12 in browser)


console.log("%EVENT_NAME%")
console.log(%EVENT_ID%)
console.log(%TRANSACTION_ID%)
console.log("%TRANSACTION_REFERENCE%")
console.log(%TRANSACTION_TOTAL%)
console.log("%PAGE_NAME%")
console.log(%PAGE_ID%)
console.log("%ISO_CURRENCY_CODE%")
console.log("%ISO_COUNTRY_CODE%")
console.log("%EMAIL_OPT_IN%")
console.log("%SMS_OPT_IN%")
console.log("%TELEPHONE_OPT_IN%")


Examples with labels examples Adobe Analytics: (check console, usually F12 in browser)


console.log("Event name: %EVENT_NAME%");
console.log("Event ID: %EVENT_ID%");
console.log("Transaction ID: %TRANSACTION_ID%");
console.log("Transaction reference: %TRANSACTION_REFERENCE%");
console.log("Transaction total: %TRANSACTION_TOTAL%");
console.log("Page name: %PAGE_NAME%");
console.log("Page ID: %PAGE_ID%");
console.log("ISO Currency Code: %ISO_CURRENCY_CODE%");
console.log("ISO Country Code: %ISO_COUNTRY_CODE%");
console.log("Email opt. in: %EMAIL_OPT_IN%");
console.log("SMS opt. in: %SMS_OPT_IN%");
console.log("Telephone opt. in: %TELEPHONE_OPT_IN%");


Examples Adobe Analytics: (check console, usually F12 in browser)



Examples Adobe Analytics: (check console, usually F12 in browser)