Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
SOLVED
Journey time
1 Accepted Solution
Correct answer by
There are a couple of approaches I can think of in workspace...
- Used the "average time on site" metric to get an average time for the process. This metric can be segmented at a hit level to get the average time for specific pages. So to get the average time for a process create a segment that segments all of the process steps together. e.g. for a three step process the segment would have 2 containers.
- Visit level container "step 1" AND "step 2" AND "step 3" (to ensure the user has seen all steps)
- Hit level container "step 1" OR "step 2" OR "step 3" (to restrict the metric to only those pages)
- Use sequential segmentation. Within sequential segmentation you apply time limits, so you can build up a view of how long it is taking to complete a process.
For example, to build up a view of how long it takes you could create multiple segments like this:
- "first page of process" then within 1 minute "last page of process"
- "first page of process" then within 2 minute "last page of process"
- "first page of process" then within 3 minute "last page of process"
- etc.
Another option would be to make changes to your implementation to actually time each process using JavaScript [EDIT: See @Jennifer_Dungan's reply for suggestions on how to do this using Adobe supplied plugins].
Hopefully some of the clever people on here might have some other ideas too - I'm really interested to see if there is a better way to do time based stuff
Correct answer by
There are a couple of approaches I can think of in workspace...
- Used the "average time on site" metric to get an average time for the process. This metric can be segmented at a hit level to get the average time for specific pages. So to get the average time for a process create a segment that segments all of the process steps together. e.g. for a three step process the segment would have 2 containers.
- Visit level container "step 1" AND "step 2" AND "step 3" (to ensure the user has seen all steps)
- Hit level container "step 1" OR "step 2" OR "step 3" (to restrict the metric to only those pages)
- Use sequential segmentation. Within sequential segmentation you apply time limits, so you can build up a view of how long it is taking to complete a process.
For example, to build up a view of how long it takes you could create multiple segments like this:
- "first page of process" then within 1 minute "last page of process"
- "first page of process" then within 2 minute "last page of process"
- "first page of process" then within 3 minute "last page of process"
- etc.
Another option would be to make changes to your implementation to actually time each process using JavaScript [EDIT: See @Jennifer_Dungan's reply for suggestions on how to do this using Adobe supplied plugins].
Hopefully some of the clever people on here might have some other ideas too - I'm really interested to see if there is a better way to do time based stuff
Related Conversations
