BTT Page Tag for Unica NetInsight

Unica NetInsight is one of IBM Unica product family, that provides the critical information and insight customer need to improve website design, internet marketing effectiveness, and your customer's experience. Unica NetInsight provides page tag, log import, reporting and analyzing functions to support the business purpose.
BTT application is one type application to be analyzed by Unica Netinsight. To let the Netinshgt understand BTT application more accuracy, BTT provides BTT page Tag based on Unica Page Tag and capture following data:
  • BTT Transition Event
  • BTT Transaction and steps
  • Extra BTT parameters

Unica NetInsight introduction

There are 3 steps in a typical interactive marketing solution:
  1. Awareness. Sellers will use customer analytics, web analytics event detection and predictive analytics to aware customer need.
  2. Decisioning. Sellers will do segmentation, contract refinement, offer management and real-time targeting using the data from previous step.
  3. Execution. At last, sellers need do real execution like email or telephone marketing to sell the refined offers to end customer.
Unica NetInsight helps customer on step 1, it analyzes online campaigns (including media buys, email, and search engine marketing) and offline campaigns (including direct mail, catalog, and call center activities). It can even analyze the response to campaigns across channels.

Unica NetInsight uses web access log files as data source to perform the analysis. To capture all the user visit data, end users need put Unica Page Tag Javascript snippet at their JSP code. The JavaScript will capture the default user behavior, and provide extended APIs for customer for customization. BTT page tag is one of the customization JavaScript that uses the APIs to capture the BTT specified information to web access log file.

BTT Page Tag for Unica NetInsight introduction

BTT application access path has its own characters, which is single URL, all request to BTT application will be like www.btt.com/appname/request. While the real transactions and pages are submitted by form hidden field, Unica page tag could not track this and need customer write javascript-based Unica Netinsight to capture the real access path and other parameter.

Without the customization, the WWW access is hard to distinguish them raw log. in order to help customer fast track BTT applications, BTT provides the BTT Pag Tag that enrich Unica Page Tag functions to track BTT application path.

The BTT page tag extends Unica Netinsight page Tag, uses ntptEvent API to store the path and event name. Also the source was attached to help customer understanding the approach and capture their own properties.

How to use BTT Page Tag for Unica

BTT Page Tag usage is similar as Unica NetInsight Tag, see following code snippet:




Put the javascript file location in your JSP file and it’ll auto track the WWW access.

Note: Unica page tag javascript file (ntpagetag.js) must be front of BTT page tag because BTT page tag leverage Unica page tag APIs to do the log.


If you want to enable the tracking on all pages, you need to modify the generation template, for example: template.ftl under templates directory. BTT suggest to put the 2 lines at last your HTML body to reduce the load time. Because put it at <header> will slightly increase the load time.
<body class="claro" style="visibility:hidden">
<#if js_file??>
<script type="text/javascript" src="${js_file}"></script>
</#if>
${content}
<script type="text/javascript" src="scripts/ntpagetag.js"></script>
<script type="text/javascript" src="scripts/bttpagetag.js"></script>
</body>
</html>
Because Unica support cloud and on-premise solutions, so you need customize how Unica page Tag record the access log. Actually the 1 pixel image address, it’s address at header of ntpagetag.js , point it to real 1 pixel image address of your solution. For example:
<p>NTPT_IMGSRC = 'http://Your Unica Log Site/ntpagetag.gif';</p>

Also for BTT application, the location is mostly the same URL so suggest to do not record the location info by disable it in ntpagetag.js as following
<p>NTPT_FLDS.lc = false; // Document location</p>

BTT page tag has following customization point for customer to adjust to their real environment. To change the values, you need to modify bttpagetag.js and it’ll take effect at next load.

Table 1.
Property Description
BTT_EVENT The BTT_EVENT property specifies whether you need to record direct, internal or ajax server call or not. The default value is "true".
BTT_REMAPURL The BTT_REMAPURL property specifies whether you need to remap BTT URL to another meaningful URL or not. BTT suggest to set "true" as value. The default value is "true".
BTT_EXTRAPARAMS The BTT_EXTRAPARAMS property specifies whether you need to capture all BTT parameters for further analyze or not. These parameters store in form hidden field or link URL. Default value is "true".
BTT_ID_OPNAME The BTT_ID_OPNAME property specifies the default identifier to capture BTT operation name. The default value is "dse_operationName". Do not change this value until you overwrite BTT channels logic.
BTT_ID_STATE The BTT_ID_STATE property specifies the default identifier to capture BTT operation state. The default value is "dse_processorState". Do not change this value until you overwrite BTT channels logic.
BTT_ID_PAGE The BTT_ID_PAGE property specifies the default identifier to capture BTT page sequence. The default value is "dse_pageId". Do not change this value until you overwrite BTT channels logic.
BTT_ID_REQUEST The BTT_ID_PAGE property specifies the default identifier to capture BTT server URL. The default value is "Request". Do not change this value until you overwrite BTT channels logic.