You no longer need to "enable pathing"....
That was part of the old Prop config for the old Reporting Interface.
In Workspace, you can use Flow diagrams to see how people are moving through your site, and you can even mix dimensions... you could start with "flows containing page a" (based on Page) then this will build a flow showing the pages coming into page a, and the pages following page a... but you can drag another dimension or even metrics onto a column in the diagram and replace just that column of data.
You no longer need to "enable pathing"....
That was part of the old Prop config for the old Reporting Interface.
In Workspace, you can use Flow diagrams to see how people are moving through your site, and you can even mix dimensions... you could start with "flows containing page a" (based on Page) then this will build a flow showing the pages coming into page a, and the pages following page a... but you can drag another dimension or even metrics onto a column in the diagram and replace just that column of data.
Does that means there is no use of enabling PROPs anymore?
Only existing evars such as Page Name or Page URLs are enough for a flow diagram?
Views
Replies
Total Likes
No, those settings were for the old Reports.. they are basically meaningless now... I expect those settings to be removed sometime this year...
Reports is still live for some customers (despite the "Dec 31st sunset date")... that checkbox really just told the interface which props to show under Paths in the Reports interface:
@Jennifer_Dungan is right, flow diagram will show you the journey.
If you want entry and exit versions for props (such as entry page title & exit page title), you can enable these in Admin > Report Suites > Select your Report Suite(s) > Edit Settings > Traffic > Traffic Variables. At the far right, you can enable Path Reports on a prop by prop basis.
Here's an Adobe video and documentation.
Views
Replies
Total Likes
Thanks for the steps, After this how do you capture the previous page URL and Next page URL in these PROPS.
Views
Replies
Total Likes
In the old obsolete way, you would have had to create a "URL" prop that would capture the url on each page (and action if you needed it there) and enable pathing....
While you still will need a dimension to capture the URL (I recommend a hit expiry eVar since it will hold up to 255 characters), you don't have to enable pathing, you can just use it in the Flow visualization.
There is also a special panel called "Next or previous item" that will auto create a report about the last or the next "whatever" you are reporting on... including URLs (if you have a dimension for that)
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies