Docs
Page changes
Add to Chrome

How to follow events across page reloads and single-page navigation

Keep earlier events and use automatic page boundaries to understand what happened after navigation.

Pixel Trail keeps a local timeline across page loads. Reloading the website does not clear its saved events, so you can inspect an action that navigated away from the page where it started.

Read the page boundaries

While the tab is recording, Pixel Trail adds navigation entries such as New page, Page reloaded, and Route changed. These separate browser navigation from the analytics events around it.

Route changed covers supported single-page navigation observed through browser history updates or the page observer. A route marker is evidence of navigation, not evidence that your analytics code sent a page-view event.

For example, after a route changes, look for an outgoing GA4 page_view request if that is what your implementation should send. A route boundary by itself does not establish that request happened.

Focus on the current page

Open Filters and set Starting point → Latest page. Earlier saved events stay in history, while the timeline starts at the most recent navigation boundary in the selected history scope.

You can also open a page boundary and choose Show events since here to use that particular boundary as your starting point. Select an event to see its elapsed time since the preceding page change and marker, when available.

Find activity from another tab

Use History for to select an open website, All tabs, or a saved earlier tab. Saved entries remain subject to your retention setting and storage limits.

The history selector changes what you see; it does not automatically enable recording for every website. Check the Record button for the intended open tab before repeating a test. Events that occurred before recording began cannot be reconstructed.

For a clean screen between actions, use Clear view instead of deleting the evidence you may need later.

Search documentation