Journeys & page views

A journey is the sequence of pages a visitor viewed — the route they took through your site, in order. NudgeVisor follows every step of that journey across pages and sessions, so you can see the paths that convert and the ones that leak. This guide explains how page views are captured and how to read a visitor's journey.

How page views are captured

Page views are recorded automatically by the widget — there is nothing extra to wire up once it is installed. Each time a visitor loads a page, the widget logs the URL and adds it to their journey.

Single-page apps work too. The widget patches the browser's history API (pushState and related navigation), so client-side route changes are recorded without a full page reload. That means a visitor moving between views in a React, Vue or Livewire app builds the same clean journey as one browsing a traditional multi-page site. If you have not added the widget yet, follow Installing the widget first.

Reading a visitor journey

A visitor's journey is shown as an ordered list of the pages they viewed, most recent step first. You can see where they entered, the route they took through your site, and where they are now. The journey sits alongside their session replay, so you can jump from "they visited these pages" to actually watching what they did on each one.

Journeys across sessions and identity

A journey is not limited to a single visit. NudgeVisor links the pages a visitor views across multiple sessions, so a return visitor's full history stays connected rather than fragmenting into separate anonymous sessions.

Identity ties this together. When you identify a visitor, their earlier anonymous activity is stitched to their known profile — so the journey you read reflects everything that person has done, before and after they signed in.

Spotting drop-off

Journeys make it obvious where people get stuck. Look for the points where visitors consistently stop — a checkout step they never get past, a pricing page they leave from, a form they open but never complete. These are the leaks in your funnel, and the journey view is where you find them.

From journeys to nudges

Once you know where visitors stall, you can act on it. Feed those patterns into a proactive nudge — for example, trigger a message when someone lingers on a page they usually drop off from, and offer help before they leave.

Next steps

• Session replay — watch exactly what happened on each page of the journey.
• Identifying visitors — connect anonymous and known activity into one journey.
• Proactive nudges — turn drop-off points into timely messages.