Adobe Experience Cloud
Why CJA Journey Canvas and Next/Previous Item disagree on the next page
Different path populations can produce different next-page counts even when dates and primary metrics match. Reconcile the query before choosing a winner.
October 20, 2026
An ecommerce analyst selects a product detail page in Customer Journey Analytics Journey Canvas, asks for the top three immediately following nodes, and gets counts that differ from the Next/Previous Item panel. The date range, container and primary metric look identical. In an October 2026 Experience League question, a community advisor points to an important possibility: a Canvas node can inherit the path leading into it, while the panel may start from a broader population.
Write down the actual question
“What did shoppers do after a PDP?” is ambiguous. Does it mean after any PDP visit in the session, after a PDP reached from a category page, or after the first PDP only? Does a repeated PDP count again? The answer changes the denominator and possibly the ordering of next pages. Align the business question before comparing two tools.
Rebuild a minimal path
Use one data view, a narrow date range and a single PDP value. Remove earlier Canvas nodes and any later constraints, then compare the next node to a Next/Previous Item panel with the same event, session settings, filters and metric. Add one constraint back at a time. If the counts diverge only after an earlier node returns, the two views are evaluating different populations.
Adobe's Journey Canvas documentation and Next/Previous Item guidance should be the reference for each visualization's path behavior. Keep the comparison at the same granularity: people, sessions and events are not interchangeable counts.
Make the reconciliation reviewable
Save both workspace configurations and a small path cohort. List the filters, entry condition, node sequence, repeat handling and time window beside the resulting counts. If the same exact query still differs, open an Adobe support case with the reproducible workspace and example IDs, rather than labelling one chart a bug from aggregate numbers alone.
Adovo’s view
Two charts disagree when they answer two different questions more often than when arithmetic has failed. The valuable work is to expose the population behind each number. A measurement system earns trust when an analyst can tell a merchant what the denominator means without defending a screenshot.