Journeys
A journey starts from a goal and shows the paths people actually took to reach it. You don't define steps. Use a funnel to measure a flow you know, and a journey to find the flows you didn't know about.
Goals and milestones
- Goals are your conversions, your key events and app installs (
$app_first_open). Conversions come first; the primary one is the default. - Milestones are the same set of events. Page views, screens and identify calls aren't milestones, so paths stay readable. Every event still shows on a person's own journey.
Mark an event as key in Events to make it a goal and a milestone. See Key events and conversions.
The rules
- One timeline. A person's events from the web, iOS, Android and your server are one timeline. For someone who reached the goal, it ends at their first goal event and starts the look back before it: 7, 30 or 90 days.
- Touchpoints aren't milestones. The source of the first session is the journey's first touch, shown on its first milestone.
- Visits fold together. Consecutive sessions on one platform are one visit milestone with a count, such as "3 web visits".
- Each milestone counts once, the first time, per platform. A sign-up on the web and a sign-up in the iOS app are different milestones, so web → iOS and web → Android are different paths.
- An install owns its session. The session an app install opened belongs to the install milestone.
- Same milestones, same path. People with the same milestones in the same order share a path.
Reached and not yet
- Reached: people whose first goal event is in the date range.
- Not yet: people first seen in the date range who haven't reached the goal. Their paths show where people wait: after a sign-up, after an install, after the first visit.
Devices join through identify()
A website visit and an app install are one journey when both called identify() with the same user id, or your server sent the user id. Nothing is guessed from IP addresses or fingerprints. A device that never identified stays its own person. See Identity.
Large projects
Above 20,000 people on either side, paths, medians and shares come from a fixed sample of people. The number of people who reached the goal is always exact.
Funnels
How Rabolic counts funnels per person across web, apps and server, with 2 to 10 ordered steps, a 1 to 90 day window, step filters, breakdowns and median timing.
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.