posthog icon indicating copy to clipboard operation
posthog copied to clipboard

Cohort criteria - match by specific date range

Open dansimau opened this issue 3 years ago • 1 comments

Is your feature request related to a problem?

I want to create cohorts based on when people signed up.

Describe the solution you'd like

On the "Matching criteria" section of a cohort filter, be able to match an "Completed event" between a date range. Currently, it is only in the last <n> <unit>.

Screenshot 2022-08-08 at 12 03 55

Describe alternatives you've considered

I guess I'll have to manually export all the user IDs from my database into a CSV and upload them into PostHog.

Additional context

Trying to move over from Mixpanel and this is one of many hoops to jump through (as Mixpanel has this feature).

Screenshot 2022-08-08 at 12 08 49

dansimau avatar Aug 08 '22 10:08 dansimau

This is also something that we are eager to do with PostHog, but for now, it seems like there isn't a clear way to achieve this.

For our use case, we want to define a cohort and use that as how we measure an active user.

For example, if we define an active user as someone who completes 3 events in any given month, we can't currently accurately measure that in PostHog on a daily, weekly, or monthly basis as far as I understand. This is unfortunate because an active user for most businesses is more than just someone who completes one action.

Amplitude does a good job of this.

Hope this can be updated or implemented soon!

tuckerschreiber avatar Aug 09 '22 13:08 tuckerschreiber

  • on this feature request.

We want to compare user behavior based on cohorts and compare for example the September cohort to the August cohort. The criteria for users to be added to a cohort is the sign up date. It would be really beneficial, if we could create a cohort based on the sign up date. For example: I would like to create a cohort based on this filter: First seen between 01.08.22 and 31.08.22 OR as an alternative: First seen on or after 01.08.22 and before 31.08.22

MagiErber avatar Sep 02 '22 10:09 MagiErber

+1

This could also be solved for me by assigning an a property or cohort to the user for the week when they first "Identified"

davidfurlong avatar Jan 17 '23 13:01 davidfurlong

+1

scormier avatar Oct 16 '23 16:10 scormier