What factor does NOT typically influence the data storage consumption of sessions replay?

The factor that does not typically influence the data storage consumption of session replay is the geographical location of users. Data storage consumption in session replay primarily depends on aspects directly related to the user's interaction and the amount of data generated during that interaction.

Application HTML size influences data storage because larger HTML files mean more data needs to be tracked and stored during a session replay. User interaction level plays a critical role, as more interactions generally lead to more data being generated, requiring more storage for the session. Connection duration can also affect data storage, as longer sessions may generate more data over time due to prolonged interactions.

In contrast, the geographical location of users does not inherently contribute to the volume of data generated or stored during a session replay. While this aspect might affect latency or user experience in terms of access speed, it does not impact the amount of data collected from user interactions during the session. Thus, it stands apart from the other factors in terms of influencing data storage consumption for session replay.