Tagging the store pages for the external analytics system

Tag each store JSP file with the vendor-specific tag library created. When customers browse these tagged pages in the WebSphere Commerce site, data is collected and sent to the external analytics system based on the programming logic in the vendor-specific tag classes. The external analytics system can then use this data to perform its analytics work.

Procedure

1. Navigate to the directory containing the site JSP files. For example, the JSP files for the Aurora starter store, are in the
   workspace_dir/crs-web/WebContent/AuroraStorefrontAssetStore folder.

2. If the name that we use for the page view tag is pageview, we can use the auto tagging utility to tag your JSP with this tag. See Running the auto tagging utility.

3. Add the appropriate vendor-specific tags to the bottom of each relevant store JSP file. Store JSP files must also refer to the tag library definition file you created. Place the tags immediately above the </body> tag in the JSP file, as shown in the following example for a product display page:

   ...
   ...
   <%@ taglib uri="http://commerce.your_company_name.com/mytld"  prefix="mytld" %>
   ...
   ...
   ...
   <!-- Vendor-specific analytics tags -->
   <mytld:product databean="${product}" />
   <mytld:pageview />
   </body>
   ...
   ...

   Note: The previous code snippet assumes created two tags named pageview and product.

Previous topic: Updating the biConfig.xml file

Related tasks
Specifying multiple analytics providers in store page analytics tags