Unveiling Insights with Customer Journey Reports
Customer journey reports show the path contacts take between defined stages and where they stall. The exam tests stage design, time-to-convert, and honest interpretation of drop-off.
What a journey is
A journey is an ordered set of stages, each defined by an event or property: first session, form submission, MQL, deal created, closed won. Every stage needs a date source, otherwise HubSpot cannot calculate time between stages. A contact is counted at a stage once they complete it, and stage order defines the path.
What the report shows
- Contacts who reached each stage.
- Conversion rate from the previous stage.
- Average time to convert between stages.
- Drop-off, meaning contacts who stopped.
Segmenting
Break journeys down by source, lifecycle, company size, or campaign to see whether a bottleneck is universal or confined to one segment. A 20-day average might be 3 days for one source and 40 for another.
Worked example
Stages: first session, demo request, deal created, closed won. Counts: 4,000, 400 (10%), 120 (30%), 48 (40%). Average time from demo request to deal created is 21 days; deal to close is 14 days. Reasoning: conversion is healthiest at the end, but the 21-day gap between a requested demo and a created deal is the largest delay and the clearest operational fix.
Traps
- Defining stages from properties that get overwritten, so history disappears.
- Missing date properties, leaving time-to-convert blank.
- Comparing journeys built over different windows.
- Confusing contact journeys with deal journeys: one company can have several contacts.
- Reading an average time without checking the distribution.