Option #1 – auto bootstrapping
...
Eventgiven in the example is a test one and it uses the default configuration (colours, 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
...
var trackerGenerator = new STATSCORE.LSP.Generator();
IMPORTANT:
Please keep in mind that trackers should be placed accordingly to the documentation. We can't guarantee that everything will work if the script is copied from another website.
...
Example 1
trackerGenerator.create('#trak', 'tracker1', 1653325, 169, {
useMappedId:'1',
})
To switch between your ids or our ids on the fly, you can use the 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 decides about tracker header visibility |
showTimeline Type: bool | This option decides about tracker timeline visibility |
showAds Type: bool | This option decides about tracker advertisement visibility |
mainMenu Type: string Possible values: | Here you can specify which tabs should be shown in the main box |
additionalMenu Type: string Possible values: | Here you can specify which tabs should be shown in the additional box (this is a 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: | This option is the same as mainMenu but it's considered only in basic relation mode. By default basic relation uses BasicEvent instead of Event tab. |
basicRelationAdditionalMenu Type: string Possible values: | This option is the same as additionalMenu but it's considered only in basic relation mode. |
mainBoxInitializationTab Type: string Possible values: | This configuration decides which tab should be loaded as first on tracker initialization |
additionalBoxInitializationTab Type: string Possible values: | This configuration decides which tab should be loaded as first in the additional box on tracker initialization |
mainBoxBasicRelationInitializationTab Type: string Possible values: | This option is same as mainBoxInitializationTab but its considered only in basic relation mode. |
additionalBoxBasicRelationInitializationTab Type: string Possible values: | This option is the same as additionalBoxInitializationTab but it's considered only in basic relation mode. |
leftBannerImg Type: string | URL to an image which should be used as a left banner on Live tab. It should be a 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 the left banner |
rightBannerImg Type: string | URL to an image which should be used as a 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 the right banner |
...