Session summarization
Session summarization produces a written account of recorded activity. A summary can describe the apparent goal, actions and outcome, with references to relevant moments in the replay. rrweb Cloud calls this account a narration. Interpretations of intent or friction are inferences from the captured activity and may need checking against the replay.
How it works
A summarization system extracts actions and page context from recorded events, then uses that evidence to produce text. Named elements, such as a checkout button or search field, help make the account readable.
The result depends on what the session captured and what the system retained. Masked content, missing events or omitted context can limit the explanation.
Use a summary to find relevant moments
Read the summary to decide which parts of a session to inspect. Follow references back to the replay when investigating a possible problem. A repeated action can have several explanations, so a summary should distinguish the observed action from an inferred cause.