Collecting analytics data about page interactions

If we use an analytics vendor other than , we can customize the framework that tracks page interactions in starter stores to work with the alternative analytics vendor.

Scenario A

The new vendor supports all of the places and actions for which Web 2.0 starter stores are currently tagged. This scenario is the simplest scenario as it requires no changes to the store pages. There are two required changes:

1. Create an implementation class of the wc.analytics.GenericEventListener for the new vendor. This class includes the implementation of the event handler methods.

2. Map the analytics view to different view JSP files (for example, crs-web/WebContent/storedir/ABCAnalyticsPageView.jsp) where the specific JSON object for the vendor can be generated.

Scenario B

The new vendor does not support all of the places and actions for which Web 2.0 starter stores are currently tagged, or there are more actions for which tags are required. This scenario is a little more complex:

1. Modify the starter store pages to either add or remove event triggers as appropriate.

2. Create an implementation class of the wc.analytics.GenericEventListener for the new vendor. This class includes the implementation of the event handler methods, and should be extended to include methods to handle any additional events.

3. Map the analytics view to different view JSP files (for example, crs-web/WebContent/storedir/ABCAnalyticsPageView.jsp) where the specific JSON object for the vendor can be generated.

Related reference
Sending additional data to IBM Digital Analytics for a IBM Digital Analytics event
Customizing the IBM Digital Analytics event listener