-
Notifications
You must be signed in to change notification settings - Fork 14
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
Create a 'Signup' event on each platform #193
Comments
if we're unable send events before the user opts in, I would imagine setting an account created timestamp on the user properties (and matrix account data) and inferring account creation from that, may need some custom logic in posthog to translate that timestamp to an analytics day |
Can we simply send the event if the analytics opt in comes as part of the registration flow, and otherwise we don't send one? Seems like it would be the simplest approach. |
yep, updated the description |
@ouchadam , you can backdate events on PostHog according to their HTTP documentation. I found that the JS sdk does not allow to set that property, but I have created a new issue to extend the library's capabilities PostHog/posthog-js#390 That way we won't need to abuse the event properties in order to track an accurate registration time |
nice find! it looks like we have a similar issue with the android SDK where the ability to mutate the timestamp for historical purposes exists internally but isn't exposed to the main public api |
Related to element-hq/element-meta#193 Fixes element-hq/element-web#21925 The timestamp backdating will only work once PostHog/posthog-js#390 has landed and we have upgraded to a new posthog-js version
Has been completed on all platforms. closing. |
We'd like to be able to create cohorts according to how recently users have signed up. Adding a Signup event would allow us to create D1 / D7 / D30 cohorts in Posthog:
This wouldn't be present for older users, but given the purpose is mainly to analyse new users that will have raised this event, that's not a blocker.
As suggested by @pixlwave, simply send the event if the analytics opt in comes as part of the registration flow, and otherwise don't send one.
The text was updated successfully, but these errors were encountered: