-
Notifications
You must be signed in to change notification settings - Fork 129
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
feat: report reason for recording start #1452
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Size Change: +5.23 kB (+0.19%) Total Size: 2.83 MB
ℹ️ View Unchanged
|
Co-authored-by: Manoel Aranda Neto <[email protected]>
i'm going to make this draft... turns out to be really tricky to only trigger once on "normal" start since we might need to wait for decide or not also makes me think it'd be useful in a recording/session to be able to distinguish between client and browser navigation generally |
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the |
in this private slack thread https://posthog.slack.com/archives/C06R7TKD508/p1727988694238459
A user has
adding this as an event has cost implication for users (if small)
and it is tricky to pick up a definitive start reasons for some flows as start is idempotent and we call it more than once
so, let's add a session super property so folk can look for that