-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
View recordings relevant to an insight from the persons modal #7246
Comments
Important: Please also consider using timestamps with the recording - i.e. direct users to when something occurred if possible.
If I'm diagnosing a funnel dropoffs, I'd like to know why users dropped off. So show me the previous successful step and onwards. |
Ah, yeah that'd be super useful when showing the recording itself. I think to be certain about the position in a recording, we need @EDsCODE worth noting ^ if you're looking at the funnel stuff. |
I would prioritize this as soon as possible, critical for Diagnosing Causes, seeing recordings is the prime way to get qualitative insights (CC @mariusandra) |
The mockups here are a bit out of date - ideally we'd show only the applicable session recording for the funnel. There generally shouldn't be multiple recordings unless it's a really broad conversion window, right? |
I think in funnels it's generally true that multiple matching recordings would be rare, but in other insights, it will probably be more common that a user has multiple recordings of them performing a specific event. |
Closing this as it is definitely covered in the new PersonsModal |
Starting a new issue for (#5664) because the conversation there is outdated.
Summary: To allow customers to understand "why" a user did something (churned from a funnel, performed a specific event etc.), we should link to recordings from insights. Specifically, in the persons modal on an insight, we should link to the specific recording where the event happened.
For the UX, we have these mock-ups from @clarkus
https://www.figma.com/file/9yWtngNb1AIuf6KmXaEPJA/App-doodles?node-id=1085%3A137286
![image](https://user-images.githubusercontent.com/4813045/142686527-4557ac01-1ac8-4606-a31e-62c783cb5953.png)
Now that both
events
andsession_recording_events
are tagged with asession_id
, we can definitively say this event occurred in this recording, and that should make this work much simpler. It will only work for customers who have upgraded posthog-js, but I think that's OK.For most of the insights, it's pretty obvious which recordings should be shown in the modal. For example, on the trends page, when you open the modal, we should show the recordings when the event from the trend-line occurred. (Note: there could be multiple recordings that include that event)
Open questions
cc @EDsCODE @alexkim205 @paolodamico @macobo @neilkakkar
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: