Configure a Reporting Service server

The Sitecore Reporting Service fetches reporting data from various data sources, for example, the collection and reporting databases, to use in Sitecore reporting applications, such as Experience Analytics. The Reporting Service can run on a server alongside other server features or independently on a dedicated server.

In the reporting architecture, the Reporting Service sits between the reporting applications and the rest of the Sitecore Experience Database (xDB) architecture and handles the processing of all your report queries.


  • If you run the xDB Cloud edition, you must configure your Reporting Service environment according to the instructions in this topic and the instructions for configuring xDB Cloud.


You should synchronize all servers to a single reliable time source, such as with the Network Time Protocol (NTP). Engagement automation state aggregation depends on the system time. Inconsistency in time sources can lead to incorrect aggregation results or loss of data.

Configuration and connections

Before you install a Sitecore server you must read the hardware guidelines for Sitecore Hosting Environment Requirements and Sitecore Client Requirements sections from Installation Guide 9.0. You can download the guide from the Sitecore Downloads page.

You can install a Sitecore server either manually or by using the Sitecore Installation Framework. We recommend you use the Sitecore Installation Framework according to the instructions in the Installation Guide 9.0. The Sitecore Installation Framework automatically configures your Sitecore server for the role you select.

If you install the server manually, you must configure it for the Reporting Service role:

  1. Use rule-based configuration to configure the server to fulfill only the reporting role by including this line in the web.config file:

    <add key="role:define" value="Reporting" />
  2. Ensure the following connection strings are set in the \App_Config\ConnectionStrings.config file:

    Name Type Notes
    core SQL  
    master SQL  
    web SQL  
    reporting SQL  
    reporting.apikey Unique string If you use a dedicated Reporting Service or processing server.
  3. Open the \App_Config\ConnectionStrings.config file and configuring the reporting API key:

    <add name="reporting.apikey" connectionString="a0123456789abcdefghijklmn9876543210z" />

Configure Path Analyzer

Path Analyzer is enabled by default on the Reporting role. No additional configuration is required.


Refer to the Security Hardening Guide for comprehensive security hardening instructions.