Usage Analytics Data Retention
Usage Analytics Data Retention
Coveo typically retains usage analytics data for an extended period to allow you to produce reports showing long-term trends and comparing similar periods over months, quarters, and even years.
However, usage analytics data is retained for a finite period to maintain performances and keep the database size manageable. As shown in the following table, the data retention period is shorter for some specific dimensions (see Usage Analytics Concepts).
|Coveo usage analytics data retention|
|Typical period||Data description|
|3 years||Standard and custom events with associated dimensions|
The data retention period starts for a specific data set when the corresponding usage analytics event occurs.
Coveo can permanently delete usage analytics data when the data retention period ends.
You started gathering usage analytics data on May 4th, 2015. With a 3-year data retention period, data recorder on May 4th, 2015, can be permanently deleted starting on May 5th, 2018.
Your subscription agreement with Coveo may specify other usage analytics data retention periods.
You can always contact Coveo Support to request the permanent deletion of specific periods of your usage analytics data.
customData object contains a set of metadata (key-value pairs) in JSON format (see Usage Analytics Concepts). The
customData object has a shorter retention period because in the usage analytics database, its content is generally replicated in individual custom dimensions and the original JSON raw data increases the database size without adding value.
Picture the usage analytics database as a table. Each row corresponds to an event and each column contains the value of one dimension. The
customData object is however special as it’s stored in one column as a whole in JSON format.
When an administrator maps one of the
customData metadata to a custom dimension (see Manage Dimensions on Custom Metadata), a column is created in the database for the custom dimension and is populated with the corresponding values from past and future events, therefore duplicating the data. The 3-year data retention period applies to custom dimensions.
Consequently, when all
customData metadata are mapped to a custom dimensions within a year from the time they start to be collected, the
customData 1-year data retention period has no data availability impact, and can even contribute to improve performance.
About the Advanced Query Expression dimension
The Advanced Query Expression dimension has a shorter retention period because it impacts database size and performance and is typically useful mainly for debugging purposes and only shortly after event occurrences.
The Advanced Query Expression dimension contains the part of the query that’s hidden and typically includes filters for the search interface scope and facet selection (see Search Dimensions). This expression can often be long, increase the database size, and rarely used in filters, but when it is, parsing its content may affect performances.