@dugganab
It will be great if journey properties exposed functions to get the previous nodes id's profile travelled through a level lookup approach.
getTravelledNodeId(level 1 or level2 or level3) - Level1 gives parentNodeId, Level2 gives grandparentnodeid, Level3 gives parent of grandparentnodeid.
In real world use cases, journey can have lots of further segments through conditional approach. Business may need this travel history at specific segment level and persist in their interaction data table. Relying on data-disteller query service for the history data from the massive step events dataset is a performance hit.
Where on the Adobe Experience Manager AEM, there are such OOTB API functions available to get the history of current page where one could build Breadcrumbs components on the brand sites.