Pathing
Web pathing
With consent on, each action in this browser is a first-party event to /api/collect. The timeline is this tab. The flow counts hops from every consented session and keeps only the counts.
Pathing is collected in this browser. A page view fires on each route change. A click records the element’s tag, visible text, one data attribute, and the link path. Scroll depth is recorded at 25, 50, 75, and 100 percent. A form records its field names when it starts and when it is submitted, never the values. Consent changes, sign-in, sign-out, and outbound links are their own events.
Each event carries a session id, a sequence number, a timestamp, the path, and the previous path in this tab. Those fields live in the existing collect record. Personalization can use the path — which notes were opened, and whether the visit came through the lab — when it chooses what to show next. The rule still runs here, and it can name that signal.
Turn consent on to see a beacon. While consent is off, this browser does not send a path and nothing is stored.
Session key site.path.v1 · this tab only
Recommended next
Why these picksReading path transitions…