In private session state, all data related to a specific interaction, such as viewed pages, converted goals, triggered campaigns, or accumulated engagement points, is collected and saved to the session state database.
If you are using a Redis session provider, all content delivery servers must use the same provider pointing to the same database.
Deploy a private Redis session database
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.
Note Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during run time.
Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during run time.
To deploy a Redis session database:
- 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.
- Go to App_Config
ConnectionStrings.configfile, and add the following connection string:
<add name="session" connectionString="_host_:_port_number _" />
- Configure the connection string so that it points to your session database.
- Save your changes.
To configure Sitecore to use the private session state store provider for Redis:
- Go to your site root folder, open the
web.configfile and locate the
<sessionState mode="InProc" cookieless="false" timeout="20">
- Update the
sessionStatesection to use the Redis provider instead of InProc, as shown in the following example. Also, change the name attribute value to
<sessionState mode="Custom" customProvider="redis" timeout="20">
Adjust the Redis provider settings
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.