Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Option #1 – auto bootstrapping

Insert the following code where you want to place the tracker: 

...

  • id - it's the HTML element identifier. In case where few trackers will be visible on the same page, each id should have different value f.e. "tracker-2", "tracker-3" etc.
  • data-event - this value should include STATSCORE event ID or CUSTOMER event ID.
    Please note: To force the script to use CUSTOMER event ID attribute "data-use-mapped-id" should have value = 1.
  • data-lang - sets language for tracker
  • data-config - configuration id, different for each customer
  • data-zone - sets time-zone for the tracker. If empty local time-zome will be detected automatically.
  • data-use-mapped-id - switch tracker to use STATSCORE or CUSTOMER event id in data-event parameter to display visualization.
    Possible values:
    "0" - in this case data-config parameter should store STATSCORE event ID to display visualisation.
    "1" - in this case data-config parameter should store CUSTOMER event ID to display visualisation and CUSTOMER event ID should be mapped with STATSCORE event ID in STATSCORE system.
     

Eventgiven in the example is a test one and it uses default configuration (colors, fonts and other visual components) which cannot be changed by passing another configuration id. Final (production) configuration could be customized according to customer expectations.

Option#2 – manual initialization and tracker management

...


Example 1

trackerGenerator.create('#trak', 'tracker1', 1653325, 169, {
useMappedId:'1',
})

To switch between yours ids or ours ids on the fly, you can use following methods on tracker object:

  • useRegularEventId()

  • useMappedEventId()

After using those methods remember to change event id and call refresh method.


Example 2 

var tracker = trackerGenerator.get({string} identifyingName);
tracker.useRegularEventId().setEvent({number} new event id).refresh();

...

Example 1:
trackerGenerator.create('#trak', 'tracker1', 1653325, 169, {
lang:'pl',
timezone:'Local',
configuration:{
showHeader: true
}
});

Available configuration options

Option

Description

showHeader


Type:  bool

This option decide about tracker header visibility

showTimeline


Type: bool

This option decide about tracker timeline visibility

showAds


Type: bool

This option decide about tracker advertisment visibility

mainMenu


Type: string

Possible values: 
Tab names from TabList table separated by comma

Here you can specify which tabs should be shown in main box

additionalMenu


Type: string

Possible values: 
Tab names from TabList table separated by comma

Here you can specify which tabs should be shown in additional box (this is right box in horizontal mode or lower box in vertical mode) This configuration is available only when your template has 2 boxes.

basicRelationMainMenu


Type: string

Possible values: 
Tab names from TabList table separated by comma

This option is the same as mainMenu but its considered only in basic relation mode. By default basic relation uses BasicEvent instead of Event tab.

basicRelationAdditionalMenu


Type: string

Possible values: 
Tab names from TabList table separated by comma

This option is same as additionalMenu but its considered only in basic relation mode.

mainBoxInitializationTab


Type: string

Possible values: 
Tab names from TabList table

This configuration decide which tab should be loaded as first on tracker initialization

additionalBoxInitializationTab


Type: string

Possible values: 
Tab names from TabList table

This configuration decide which tab should be loaded as first  in additional box on tracker initialization

mainBoxBasicRelationInitializationTab


Type: string

Possible values: 
Tab names from TabList table

This option is same as mainBoxInitializationTab but its considered only in basic relation mode.

additionalBoxBasicRelationInitializationTab


Type: string

Possible values: 
Tab names from TabList table

This option is same as additionalBoxInitializationTab but its considered only in basic relation mode.

leftBannerImg


Type: string

Url to image which should be used as left banner on Live tab. It should be valid url to image resource hosted under https protocol. Note that not every configuration supports ads on Live tab and showAds option should be enabled for this to work.

leftBannerLink


Type: string

Url which user is redirected to after he clicks on left banner

rightBannerImg


Type: string

Url to image which should be used as right banner on Live tab. It should be valid url to image resource hosted under https protocol. Note that not every configuration supports ads on Live tab and showAds option should be enabled for this to work.

rightBannerLink


Type: string

Url which user is redirected to after he clicks on right banner

...