CMS Usage Statistics

Overview

Bloomreach Content collects usage statistics from the CMS user interface to inform ongoing UI improvements. This data helps Bloomreach understand how users interact with the system and guides future enhancements. Collected metrics include application usage patterns and UI event data, such as which applications are opened and which buttons are clicked. No customer content or configuration data is transmitted. Usage statistics are used exclusively to improve Bloomreach products and services. For details on data handling, refer to the Bloomreach Privacy Policy.

Collected Information

Bloomreach Content collects the following usage data in addition to standard browser information (such as IP address and browser type):

Bloomreach Content version number
Content type and event details
CMS language setting
Unique user identifiers

The set of collected events may expand in future releases. For more information on data usage, see the privacy policy.

Disabling Usage Statistics Collection

By default, usage statistics collection is enabled. You can disable this feature using either a repository configuration property or a Java system property. Disabling statistics collection prevents Bloomreach from gathering data on your users' interactions with Experience Manager.

Repository Configuration Property

Control usage statistics collection with the following boolean repository configuration property:

/hippo:configuration/hippo:frontend/settings/@send.usage.statistics.to.hippo

The default value is true. To disable statistics collection, set this property to false. The following YAML definition demonstrates how to configure this setting:

definitions:
  config:
    /hippo:configuration/hippo:frontend/settings:
      send.usage.statistics.to.hippo: 'false'

Java System Property

Alternatively, you can disable usage statistics collection by setting the Java system property send.usage.statistics.to.hippo to false. For local development, configure this property in the systemProperties section of the Cargo plugin configuration in your project's root pom.xml file. Example:

<profiles> 
  <profile>
    <id>cargo.run</id>
    <build>
      <plugins>
        <plugin>
          <configuration>
            <container>
              <systemProperties>
                <send.usage.statistics.to.hippo>false</send.usage.statistics.to.hippo>
              </systemProperties>

Technical Details

The CMS frontend publishes client-side events to a JavaScript event bus. Other JavaScript components within the CMS can subscribe to and react to these events. When usage statistics collection is enabled, the CMS loads an external JavaScript file that monitors all published events and forwards them to the Bloomreach data service. This external file is loaded asynchronously to avoid impacting CMS UI performance.