Skip to content
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

Closed
2 of 3 tasks
novocaine opened this issue Mar 4, 2022 · 7 comments
Closed
2 of 3 tasks

Create a 'Signup' event on each platform #193

novocaine opened this issue Mar 4, 2022 · 7 comments
Assignees
Labels
A-Telemetry Telemetry / analytics to understand usage T-Enhancement Z-FTUE

Comments

@novocaine
Copy link

novocaine commented Mar 4, 2022

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:

Screenshot 2022-03-04 at 09 57 36

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.

@daniellekirkwood
Copy link
Contributor

👀 @ouchadam & @pixlwave

@ouchadam
Copy link

ouchadam commented Mar 4, 2022

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

@pixlwave
Copy link
Member

pixlwave commented Mar 7, 2022

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.

@daniellekirkwood daniellekirkwood added T-Enhancement A-Telemetry Telemetry / analytics to understand usage Z-FTUE labels Mar 7, 2022
@daniellekirkwood daniellekirkwood self-assigned this Mar 7, 2022
@novocaine
Copy link
Author

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

@germain-gg
Copy link

@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

@ouchadam
Copy link

ouchadam commented Apr 26, 2022

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

https://github.com/PostHog/posthog-android/blob/master/posthog/src/main/java/com/posthog/android/payloads/BasePayload.java#L181

germain-gg pushed a commit to matrix-org/matrix-react-sdk that referenced this issue Apr 26, 2022
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
@daniellekirkwood daniellekirkwood removed their assignment Apr 29, 2022
@pixlwave pixlwave removed their assignment Sep 13, 2023
@germain-gg
Copy link

Has been completed on all platforms. closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Telemetry Telemetry / analytics to understand usage T-Enhancement Z-FTUE
Projects
None yet
Development

No branches or pull requests

7 participants