You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it's not straight forward to get business related session metrics like duration or bounce rates.
Faro's session manager currently doesn't send a session_end event.
This is because Faro can't know when a session conceptually ends.
Is it after a user logs out of a page or after a certain timespan etc.
It may be still useful for customers if Faro provides an easy to use set of functions to clear or end a session.
Furthermore it cab provide a session_end event which can be sent manually to have an option to track business metrics like session length or drop rates.
This is an easy option to get started.
In the long term this should be made easier
Proposed solution
Provide convenience function for ending a session and sending a respective event.
Additionally we can think about adding the session_start timestamp to the session meta so we always can derive the current session duration.
Alternatively we can only add the session duration to the respective session lifecylcle event. Whole duration e. g. can be calculated by lastSessionLifecycleEvent.duration + lastEvent.timestamp - lastSessionLifecycleEvent.timestamp. This would save a good chunk of redundant meta data
Context
The text was updated successfully, but these errors were encountered:
codecapitano
changed the title
Provide a convenince function to end a session and send a session_end event
Provide a convenience function to end a session and send a session_end event
Sep 10, 2024
codecapitano
changed the title
Provide a convenience function to end a session and send a session_end event
Better support session related business metrics
Sep 10, 2024
Description
Currently it's not straight forward to get business related session metrics like duration or bounce rates.
Faro's session manager currently doesn't send a
session_end
event.This is because Faro can't know when a session conceptually ends.
Is it after a user logs out of a page or after a certain timespan etc.
It may be still useful for customers if Faro provides an easy to use set of functions to clear or end a session.
Furthermore it cab provide a
session_end
event which can be sent manually to have an option to track business metrics like session length or drop rates.This is an easy option to get started.
In the long term this should be made easier
Proposed solution
Alternatively we can only add the session duration to the respective session lifecylcle event. Whole duration e. g. can be calculated by
lastSessionLifecycleEvent.duration + lastEvent.timestamp - lastSessionLifecycleEvent.timestamp
. This would save a good chunk of redundant meta dataContext
The text was updated successfully, but these errors were encountered: