Relevance Data Stores

Overview

Configure the data stores for each type of data collected by the Relevance Module.

Data Classes Collected by the Relevance Module

The Relevance Module collects and stores four distinct types of data. Each type has specific requirements for performance, reliability, and querying. To meet these requirements, the module supports multiple backend systems.

• Requests
  Stores raw request data. The Real Time panel in the Content Audiences application uses this data, and it also serves as the basis for deriving other data types such as Visits.
• Visits
  Aggregated from request data. The Experiments charts and Trends panel in the Content Audiences application query this data.
• Visitors
  Contains information about individual visitors who are currently active on the site. This data is queried and may be updated on every page request, so the data store must provide fast access.
• Statistics
  Holds statistical information about personas and characteristics. The system uses this data to determine which persona best matches a visitor.

Each data class is assigned to a specific data store. Configure these data stores in the Console application at the following repository nodes:

/targeting:targeting/targeting:datastores:
  /targeting:requestlog:                (requests)
  /targeting:statistics:                (statistics)
  /targeting:targetingdata:             (visitors)
  /targeting:visits:                    (visits)
copy

Supported Data Store Types

The Relevance Module requires two types of data stores:

• SQL Database Data Store
  Use an SQL database to store Requests, Statistics, and Visitors. The SQL data store cannot be used for Visits due to its querying limitations.
• Elasticsearch Data Store
  Use Elasticsearch to store Visits. Elasticsearch is required for Visits because of its advanced querying capabilities.