Specifying multiple analytics providers in store page analytics tags
After you update the <biproviders>
element
in your biConfig.xml configuration file, you
must specify the analytics provider in your store page analytics tags. This
distinguishes those tags from your default analytics provider tags
that are indicated in your biConfig.xml configuration
file.
About this task
Procedure
Example
1
<cm:output section="header" biprovider="coremetrics"/>
<cm:product databean="${product}" extraparms="null, ${cookie.analyticsFacetAttributes.value}" biprovider="coremetrics"/>
<cm:pageview biprovider="coremetrics"/>
<cm:output section="footer" biprovider="coremetrics"/>
2
<mytld:output section="header" biprovider="additionalprovider"/>
<mytld:product databean="${product}" extraparms="null, ${cookie.analyticsFacetAttributes.value}" biprovider="additionalprovider"/>
<mytld:pageview biprovider="additionalprovider"/>
<mytld:output section="footer" biprovider="additionalprovider"/>
- In line 1, the store page analytics
tags indicates coremetrics as a biprovider. Coremetrics is
the first analytics provider that is defined in the
biprovider
tag in the biConfig.xml configuration file. - In line 2, the store page analytics
tags also indicates additionalprovider as the biprovider. Additionalprovider is
the second analytics provider that is defined in the
biprovider
tag in the biConfig.xml configuration file.
Because there are two biproviders that are specified for this
store page, the default provider is overridden and both the analytics
providers that are specified in the biprovider
tags
take precedence over the default provider.
Note: The
biprovider="coremetrics"
parameter
is not mandatory if IBM Digital Analytics ("coremetrics") is
specified as the default analytics provider in biConfig.xml configuration
file.The mytld
in line 2 represents
the prefix for an additional analytics provider. You must use the
prefix that is defined in your JSP page for your own additional analytics
provider