Analyze user behavior by Active Site Analytics

We can collect data about user behavior in the portal and senthat data to a service for analysis. For this purpose the portal provides Active Site Analytics (ASA).

The portal provides a rich set of page metadata as part of its themes and skins. Examples are:

• Page title

• Page identifier

• Portlet title

• Portlet identifier.

We can write scripts to retrieve the data. Such scripts are called aggregators. WebSphere Portal provides several sample aggregators. They are located in the PORTAL_HOME/doc/js-samples directory of the portal installation. We can customize these or write our own aggregators to collect page metadata and more. For the samples, refer to the topic Writing an aggregator for active site analytics.

Administrators add the aggregator scripts to pages as required. When they do this, the aggregator is injected into markup of the page the next time it is rendered. We can select the point of injection arbitrarily; for example, this can be just before the closing body tag of the HTML markup. Refer to the following flow graphic:

• Collect analytics data
  Before we can send data about user behavior in the portal to a service for analysis, you need to collecthat data.

  See the following topics for information about how to do this.

• Display overlay analytics reports
  We can use Active Site Analytics to show graphical statistics reports about individual portal resources, such as pages or portlets. These reports are called Active Site Analytics overlay reports.
• Analytics tags and site promotions
  To obtain further analytics information from the portal, we can use analytics tags for the portal resources. We can also use analytics tags for site promotions.

Parent: Analyzing portal usage data