Skip to main content
MaxenceGA
Level 1
September 25, 2026
New

Next or Previous panel – option to include repeat instances and visit entries

 

Hi everyone,

We use the Next or Previous panel to analyse navigation, and we compared it with paths rebuilt from our raw data (page events ordered by timestamp within each visit). The results are very close, which makes this panel really valuable. But I think two options are missing to reflect real user behaviour:

  1. Include repeat instances. The panel uses the "Non-repeating instance" model, so consecutive views of the same page (e.g. a search results page reloaded after each date change) disappear. Flow already offers "Include repeat instances". Having the same setting here would make both views consistent.
  2. Show visit entries. When the page is the first of the visit, there is no previous page, and these occurrences are excluded. A "No previous page / Entry" row would let the previous pages add up to 100% of the page's occurrences.

Today we work around this with a manually edited segment, but it has to be rebuilt for every page and panel, which doesn't scale.

Would others find this useful too?

    3 replies

    Jennifer_Dungan
    Adobe Champion and Community Advisor
    Jennifer_DunganAdobe Champion and Community Advisor
    Adobe Champion and Community Advisor
    September 25, 2026

    I upvoted this… I agree some more options would be nice… however you should be able to edit the segment after its been created to make some adjustments to do what you want (it’s just a little more effort)..

     

    Also, that said, have you tried the new Journey Canvas? On a node, you can right click and “Show top nodes” (before or after) and then choose “immediately” or “eventually”, and you can display it in the Journey Canvas, or in a Freeform Table….

     

    This provides some more options for digging into next/previous that you might find helpful.

    Translate
    MaxenceGAAuthor
    Level 1
    September 28, 2026

    Thanks for the suggestion on Journey Canvas, I’ll definitely give it a try.

    On the Previous & Next Page panel, building hundreds or thousands of segments isn't scalable for our 100+ Product Owners monitoring their features self-serve.

    Having those two native additions would be a real game changer for server-to-server implementations, as we operate completely without client-side SDKs or s.code.
     

    Translate
      Jennifer_Dungan
      Adobe Champion and Community Advisor
      Jennifer_DunganAdobe Champion and Community Advisor
      Adobe Champion and Community Advisor
      September 28, 2026

      I agree, depending on what you are doing, segments can be fine for ad hoc, or some specific use cases.. but not hundreds or thousands…  

       

      If you are dealing with a lot of pathing and journey analysis… while it’s a big project, have you considered exporting Raw Data feeds to a data lake? While this does take some finessing to get the data processed to match up to Adobe (since you are dealing with raw...), it can sometimes be easier to use SQL for large scale variations over the built-in Adobe tools.

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...