Explain cohort retention and write a pseudo-query for May signups
Tests cohort retention vs aggregate DAU and SQL self-joins for Week 1, 2, and 4 retention from May signups. Strong answers define cohorts by signup date, use datediff, and left-join activity. Red flag: using calendar week instead of relative signup date.
Tests whether you can distinguish cohort retention from aggregate vanity metrics and model relative-period retention in SQL. A strong answer defines May signups as the denominator, self-joins an activity table on user_id, computes days-since-signup with datediff, and buckets distinct returners into Week 1 (days 1-7), Week 2 (days 8-14), and Week 4 (days 22-28). Red flag: using calendar week or month boundaries rather than each user's personal signup date, which destroys the cohort comparison.
Read the original → amplitude.com
- #analytics
- #sql
- #retention
- #cohort-analysis
- #metrics
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.