Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Can I recommend that we update the following section section? ### Cohorts and Time
Cohorts and Time - update to:
A common question that customers want to answer is how certain user behaviour impact downstream behaviour. Should you use cohorts or funnels to answer the question of how many users watch a comedy video and then subscribe? Cohorts and filters will give you different answers.
For example, consider this report: https://mixpanel.com/s/4AuMRi
For the cohort on Jan 1, I'm looking at the users who watched a comedy video in the last 30 days before Dec 25 and who then subscribed over the same period of time. However, for the funnel on Dec 25, I'm looking at the users who watched a comedy video on Dec 25, and who have then also subscribed anytime within the next 30 day period from Dec 25. This means that if a user subsequently subscribes on Jan 3, the funnel chart can change to take that conversion into account. In this case, if you care about the conversion window, i.e. the amount of time that a user has in order to count as a conversion, using funnels would give you a more accurate answer.