Journey reports are challenging when trying to dial in on the time it takes to complete the steps in a journey. Current Restrictions/Limitations Only one way to control the time range of the journey (sure we can do a static range or rolling time range), it is still only one time setting. Other analytics tools we use have additional levels of time parameters, the lack of this in Hubspot journeys limits the value we get out of the reports. Lacking stat of median time between steps; we only see the average time between steps Inability to refine time parameters on each step of the journey. Control that the action was done the 1st time since the previous step (and then stop recording the event on that report for that contact) ----- Further details We want to look at anyone who would enters the journey up to 30 days ago. THEN, we want to know, of those contacts, who completed the steps in the journey within 10 days of entering the journey. If a contact 'qualified' to be in the journey but dropped off before completing within 10 days, that's an interesting stat along with the 'success' rate of those that did complete within the 10 days. IF we limit the journey report date range to only include 10 days, we are NOT capturing the entire cohort of interest (like anyone who was sent the email in the last 30 days). IF we try to use the contact filter or apply a list to capture the cohort for the 30-day range, this doesn't work either. The reason being the date range on the report is set to 10 days because we want to know who completed the journey within 10 days, we will still only 'see' the contacts that did the first step in that 10-day range (even though we want to look at a cohort of contacts that did the first step in the last 30 days). ------ Median is good to see in addition to Average. OR at least allow us to decide which we prefer to see for each step. ----- We should be able to refine the parameters between each step as well and control how those actions are counted. (refinements) IF we are using a custom event or a page view, a person may do those events multiple times while in the time range of the journey. It appears that the most recent timestamp of firing those actions/event, overrides the first time after the prior journey step the contact may have done the event. This creates a challenge of knowing the time of completion between steps as the first time after the previous step is no longer recorded if the contact comes back and does the step again and again. Ex) Instead of opening an email, clicking a link, logging into our app showing seconds (confirming our engagement email is working); we are seeing opened an email, clicked a link and then the time to log into our app being hours or days later. When we dig into the contact record, we see this is due to the contact firing the event multiple times after having done the action in the previous step of the journey. We care to only see the time to complete as a reflection of the 'the first time after the previous step'.
...read more
