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
Record caching keeps records of your recently active visitors in the real-time layer and allows instant personalization on the first page of your website or app. When record caching is enabled, profile and entity data for your recently active known visitors remains available in the real-time layer and does not require a fetch from the Data360 Lake House layer during a live session.
If record caching is disabled, the first page visited by your known visitors might not show personalization immediately because profile data must first come from the Data360 Lake House layer. Depending on system conditions, this fetch can take time before personalization appears.
When record caching is disabled, your sub-second real-time profiles and entities entitlements do not get consumed for the months in which caching remains disabled.
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.
