Setting Up to Record Analytics Data

You set up the feature by configuring a connection to the database you'll be using to store the collected data, specifying whether to purge old data, and selecting activity you want to store data for. Note that only Oracle and PostgreSQL are supported as DBMSes for analytics data.

Attention: When you provision the database you'll be using for analytics data, be sure that it supports stored procedures. For example, on PostgreSQL you can use the CREATE LANGUAGE command on your server to register the needed procedural language:
CREATE LANGUAGE plpgsql
  1. On the Database tab, configuring connection settings for the analytics database.
    1. In the admin console, on the Analytics page, click the Database tab.
    2. Under Database Settings, select or enter connection settings for the database you'll be using to store analytics data.
      Database Settings
      Setting Description
      Database Driver Presets Select your DBMS (Oracle or PostgreSQL) to automatically populate a JDBC driver class name and database URL template. Be sure to edit the database URL so that you have a valid connection the database.
      JDBC Driver Class This fully-qualified name of the database driver class is entered for you when you select a database driver preset.
      Database URL The URL for connecting to the database is entered for you when you select a preset.
      Username A username that's valid for connecting to the database.
      Password A password that goes with the username.
      Min Connections The minimum number of connections that the application can make to the database.
      Maximum Connections The maximum number of connections that the application can make.
      Connection Timeout The amount of time after which an unused connection will be dropped.
    3. Click Test Connection to confirm that the application can connect to the database with the settings you entered.
    4. Click Save when you've successfully tested the connection.
  2. On the Data Load tab, configure data loading and purging.

    With the analytics feature enabled, the application will automatically extract and transform data from the application database into the analytics database each morning at 2 a.m., system time (you can't currently set the extraction time). At other times, you can begin extraction on this page.

    To control database size, you can have data purged from the analytics database when it has passed a certain age.

    1. Click the Data Load tab.
    2. Configure data purging.
      Important: Before you click Run ETL now to start copying data into the analytics database, be sure (in the next steps) that you're collecting only the data you want.
      Setting Description
      Purge Old Activity Click Enabled to have data purged according to the age limit you set.
      Older than (months) Select the highest number of months that each piece of activity data should be stored before it's purged.
      Run ETL Now Click Run to begin copying data to the analytics database.
  3. On the Events tab, select the application events you want to keep track of.
    1. Click the Events tab.
    2. In the Captured column, clear check boxes for those actions you don't want as part of your analysis. To start with, it's probably a good idea to collect as much as you can. You can always stop collecting certain items later.
    3. To enable analytics and start copying data, under Analytics Settings, click Enabled.