Funnels
In Analytics → Funnels, add 2 to 10 steps, each a screen or an event, optionally filtered by a property (for example payment_method = mpesa), and a conversion window. Codeskop counts users who did the steps in order within the window, starting from their first step.
| Option | Type | Description |
|---|---|---|
| Users | n/a | How many users reached each step in order. |
| Conversion | n/a | From the first step, and from the previous step. |
| Dropped | n/a | Users who reached a step but not the next one. |
| Median time to convert | n/a | From the first step to the last, for users who completed the funnel. |
Why users dropped off
Under each drop-off, Codeskop shows how many of the users who stopped there crashed, hit errors or had failed API calls in the same period, and the top issues among them, each linking to the issue. It's the fastest way to tell a design problem from a bug.
Save funnels you check often
Owners and admins can save a funnel with a name; anyone on the team can open it.Retention
Pick a starting action (for example signed_up, or the Home screen) and a returning action. Users are grouped by the week (or day) they first did the starting action; each column shows the share who did the returning action in a later week (W1, W2…) or day.
Screens and paths
- Screens lists every screen and page with views, users, the median time on screen (until the next screen in the session) and the exit rate (how often it was the last screen).
- Paths shows, for a screen, where users went next (or where they came from) within a session. Select a destination to keep following the path.
Good to know
- Choose Production or Test and the period (7, 30 or 90 days) at the top of the Analytics page.
- Anonymous users count per install until you identify them; after identify, their events carry your user id.
- Results update within a minute or two of events arriving.