Concepts
Retention
How Rabolic retention cohorts work. Cohort start and return events, daily, weekly and monthly intervals in the project's time zone, and N-day, unbounded and rolling counts.
Retention groups people by when they first did something, then shows what share of each group came back.
What starts a cohort
| Option | Event |
|---|---|
| First visit | The first page view or screen of someone new in the period |
| First app open | $app_first_open, the first launch after install |
| Signed up | signup_completed, an event you send with track() |
| First purchase | A verified $purchase |
The options offered depend on the events your project has.
What counts as coming back
| Option | Event |
|---|---|
| Any session | Any page view or screen |
| A key event | One of your key events, such as workout_started |
| Purchase | Another verified purchase |
Intervals
| Interval | Cohorts | Columns |
|---|---|---|
| Daily | 14 days | Day 0, 1, 2, 3, 5, 7, 10, 14, 21 and 30 |
| Weekly | 10 weeks, starting Monday | Week 0 to week 8 |
| Monthly | 7 months | Month 0 to month 6 |
Days start at midnight in the project's time zone, weeks on Monday and months on the 1st.
Counting methods
- N-day: came back in exactly that period.
- Unbounded: came back in that period or any later one.
- Rolling: came back at any point from the first period up to and including that one.
Good to know
- People, not devices. Retention runs after identity resolution: someone who signs up on the web and comes back in your app counts once.
- Empty cells are the future. A cohort that started last week can't have a week-4 number yet, so the cell stays empty instead of showing 0%.
- Platforms and channels. Rabolic draws a retention curve per platform and shows retention by the first-touch channel of the event that started the cohort.
Journeys
How Rabolic builds journeys to a goal from each person's own events across web, iOS, Android and server, the milestone rules, look back, not-yet paths and sampling.
Revenue and attribution
Where Rabolic revenue comes from (Dodo Payments webhooks or your server with a secret key), the one-revenue-source rule, currency conversion, linking payments to people, and first- and last-touch attribution.