You are here:
Record Caching and User Session Length in Real-Time Data Graphs
Configure your real-time data graph to manage the number of records held in the cache and user session length.
Record Caching
Using record caching keeps records of recently active users in the real-time layer, allowing instant personalization from the first page of your website. You can configure the maximum number of records to hold in the cache, and the maximum length of time that records are considered active and retained in the cache. When the cache is large and retained over a long period, more users are greeted with a personalized first page. Reducing the maximum number of records and cache duration reduces consumption costs.
The real-time layer’s data cache can hold a maximum of 100 million records. The maximum duration that a record can be held in the cache is 180 days. To disable record caching, select the Disable Record Caching checkbox. If record caching is disabled, records remain in the cache only during the consumer’s active session. To enable session extension in data graphs, deselect the Disable Record Caching checkbox.
User Session Length
The session length defines the amount of time after a user stops engaging with your website that the session is considered to be active. If you set the timeout period to 30 minutes, a user’s session is inactive 30 minutes after the most recent engagement from the user. Any engagement that happens at 31 minutes or after is a new session.
Data 360 maintains the required session length under normal conditions. However, if a significant spike in web traffic occurs, sessions can end earlier than expected.
The industry standard for session expiration is 30 minutes of inactivity. The maximum supported session duration is 48 hours.
