INVESTIGATE
Clues, journeys & comparisons
Follow an interaction, save a funnel and compare two periods with clear sample counts.
In this guide 4 sections
A clue is a lead, not proof of a broken button. Legitimate interactions can meet these conditions. The review status applies to this observation, not an entire website.
- Open Clues and choose an observation. Watch opens shortly before its recorded moment.
- Inspect what happened before and after. Three clicks within one second can create a repeated-click clue; an eligible button with no observed response for about 1.5 seconds can create a possible unresponsive-click clue.
- Mark the observation New, Reviewing, Resolved or Ignored. Note the evidence and the next thing you will check.
Journeys shows page paths within a retained recording. Save up to twenty funnels, each with two to eight ordered steps matching page paths, clues or form observations. A path prefix includes its child paths.
Use a recorded layout ID when structural field positions matter. Journeys do not identify a person across separate visits or devices.
Reports cover eligible retained recordings for the selected period using background aggregation. Check processing progress and coverage. Consent, sampling, retention and bounded observations affect coverage. Changes in rates do not establish that a website edit caused the difference. Older recordings do not receive invented new observations.
- Choose two separate UTC date ranges.
- Use matching page, device and layout filters where appropriate.
- Read the sample counts and denominators before interpreting rates.
- Inspect representative replays from both periods before drawing a conclusion.
Reports aggregate eligible retained recordings for the selected period in bounded background batches. Check progress and coverage while processing catches up. Deleting a recording removes its report contribution. Grouped Clues bring together similar observations, affected visits, trends and representative replay moments.
Owner-configured confirmed goals distinguish a supported success signal from a submit attempt. Journeys can include conversion windows, timing and branches. They need new recordings containing the configured signals; old replays cannot supply events that were never captured.