Journeys

Open Journeys to see agents and people using your product. Each journey shows the actor, where it entered, the sources it touched, its event counts and when an event was last received.

​

Find a journey

Search by agent, journey ID or entry page. Filter narrows results by Who, Identity, Touched, Linkage and receive date. Dates use UTC: Received from includes that date; Received before excludes it. Search and filters cover your workspace, including journeys that have not been loaded yet. The count shows how many matching journeys are loaded. Use Load more journeys for the next page or Refresh to start from the newest results. You can share a filtered list by copying its address. Select an actor’s name to open its journey. The arrow at the end of the row opens a short preview.

​

Read the tracker

The Journey tracker places recorded events in source lanes such as Edge, Browser, MCP, Auth and API. These identify the source of an event. A host or path in the event details identifies the page or service it reached. Nearby events are grouped to keep busy journeys readable. Select a group to browse its events, then select an event to open Event details. Search and source or placement filters, and HTTP errors, narrow the event list while keeping the full journey visible in the graph. Compress gaps shortens long stretches with no observed events. A gap does not establish that the agent was waiting or that nothing happened elsewhere. Bars show recorded duration and dots show point events for individual events. Select an event within a group to see its interval. Group labels identify ambiguous membership. On journeys with many gaps, only the longest gaps are marked; all gaps are still included in compressed time. Exact times and the gap before an event are available in the event details.

​

Understand the evidence

An actor’s identity and an event’s placement answer different questions:

• Identity describes how the actor was identified. A verified identity does not prove that two events belong to the same journey. A verified signature count applies only to the events on which one was recorded.
• Proven placement connects an event to the journey’s anchor through proof links.
• Inferred placement needs at least one inferred connection to the anchor.
• Ambiguous placement has competing possibilities.
• Anchor identifies the reference event. It can still be ambiguous.

The inspector explains the selected event’s membership path, individual connections and their conditions. A connection can be downgraded without being a proof. Arrows indicate recorded causal direction; other connections show evidence without establishing which event caused the other. Model percentages are estimates, not a guarantee of accuracy. When a browser event records who drove it, its Driver is shown separately from the actor’s identity and the event’s placement. When a change of control was recorded, Driver changed shows who previously drove that tab and who drives it now.

​

Inspect recorded details

Select an event to inspect its action, source, service, request and response status, duration, client or user agent, and timing. Missing information is shown as unrecorded. MCP calls can have generic labels when their action names were not captured. Source time is the time the source reported. Corrected time reflects any recorded clock adjustment. Received time is when the event arrived. Clock details show the basis for an adjustment or that none was recorded. Milestones such as Agent registered, Claim completed, Registration expired and Registration revoked appear only when recorded. A duration from registration to claim requires both events in the same registration. An Auth event alone does not establish a completed sign-up or activation. The address includes your selected event, so you can share the same inspection with another member of the workspace. Back to journeys preserves the list filters you came from.

​

Replay and refresh

Replay reveals the current reconstruction in accelerated playback. Events in the same order group appear together because no order between them has been established. Use the slider or previous/next controls to move manually. Reduced-motion preferences keep playback manual. Replay is not a browser recording or a history of earlier predictions. It pauses when the page is hidden. Check for updates reads the latest journey. If new evidence changes it, Apply update replaces the view and resets replay. Your selected event stays selected if it still belongs to the journey; otherwise a notice lets you clear it and choose another.

​

Set up sources

An Admin can use Set up on the Journeys page to add a browser script or an edge source. Follow the instructions shown for the chosen source. Manage existing sources in Settings · Journeys. If you are a Member, ask an Admin to set them up for your workspace.