Collect
Route changes are not page loads
A client-side route change can leave the tag on the first view. A history listener sends the next one.
Two routers
A single-page app changes the screen without a new document. A tag that only listens for a load never sees the next view. The fix is to send page_view when history.pushState or popstate runs. This demo uses its own stack so it does not change the address of this lab. This site’s App Router calls its page view when the pathname changes, which is the same idea.
/
Home
Log
- Opened / with no page_view yet.
Recommended next
Why these picksReading path transitions…