Platform Administration and Architecture

Walkthrough: Configuring a shared session state database using the Redis provider


How to use Redis as your shared session state store.

In a shared session state, all data that can be shared across multiple sessions, for example, the data related to contacts and devices, is collected and saved to the session state database. 

A contact can make multiple parallel visits to a website, in which case each visit has its own private session state. However, some data can be shared between visits, such as device and contact related information.

Information that is shared between parallel visits by the same contact is stored in the shared session state store. This data is still private to the contact but it is accessible from all current sessions made by the same contact.

This walkthrough describes how to use Redis as your out of process shared session state store using the Sitecore session state provider for Redis, and describes how to: Deploy a shared Redis session database, configure Sitecore, configure a dedicated Redis Session Processing server, and adjust the Redis provider settings.

The Sitecore ASP.NET session state store provider for Redis enables you to use Redis as your session state store. The provider supports the SessionEnd event, which the xDB needs to track website visits.


Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during runtime.

To deploy a Redis session database:

  1. Choose between Azure Redis or Redis on premise. You can provision Azure Redis by using the instructions on the Microsoft Azure website or with Azure PowerShell.

  2. Go to <sitename>\Website\App_Config, open the ConnectionStrings.config file, and add the following connection string:

    umber _" />
  3. Configure the connection string so that it points to your session database.

  4. Save your changes.


Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during run time.

The default shared-session store uses the in process provider which stores data in memory and is implemented in the internal ASP.NET class InProcSessionStateStore:

<sharedSessionState defaultProvider="inProc">
    <add name="inProc"

To configure Sitecore to instead use the shared session state provider for Redis you must:

  1. In your website root folder, go to the App_Config\Sitecore\Marketing.Tracking.

  2. Open the Sitecore.Analytics.Tracking.Config file.

  3. Locate the line where you can define the default shared session state provider using the path: sitecore/tracking/sharedSessionState.

  4. Update the sharedSessionState section to use Redis as the defaultProvider , not InProc as shown in the following example. You must also, change the name attribute value to redis,

    <sharedSessionState defaultProvider="redis">
            <clear /> 
            <add name="redis" 
    Sitecore.SessionProvider.Redis " connectionString="sharedSession" pollingInterval="2" 
    applicationName="shared" />

The Sitecore Experience platform supports a dedicated Redis server. This means that if you have an environment using a cluster of CD servers, you can configure some of the servers to only serve content but not to process the session state data by using the pollingEnabled setting.

With the pollingEnabled setting you can enable/disable expired session processing. For example, you can enable it on the CD servers that are dedicated to expiring sessions and disabled it on the live CD servers, (that serve content to visitors).

To configure the pollingEnabled setting for a shared session state:

  • Disable shared sessions processing: In the Sitecore.Analytics.Tracking.config file, set the pollingEnabled value to false for your dedicated CD servers and leave it set to true for your live servers.

                <sharedSessionState defaultProvider="redis">
                        <add name="redis" type="Sitecore.SessionProvider.Redis.RedisSessionStateProvider, Sitecore.SessionProvider.Redis"
    connectionString="redis.sessions"   pollingEnabled="false" pollingInterval="2" applicationName="shared"/>

Use the Redis provider settings reference to configure your session state.

If you have configured everything correctly, session records should appear in your Redis session database after the first web request.