Docs
Mark checkpoints
Add to Chrome

How to mark an action and find the events that happened after it

Add a named checkpoint before an action, or anchor one after an event you already found.

Use Mark here when you are about to do something worth checking: submit a form, open a calculator result, finish checkout, or change a consent choice. A checkpoint gives that action a visible place in the timeline.

Mark before an action

  1. Choose the website under History for.
  2. Click Mark here, or press M outside an input.
  3. Enter a label such as “Before submitting sample form.”
  4. Choose Add marker, then perform the website action.

Markers are local annotations. They do not fire an analytics event, change the page, or tell a provider to record anything. Check Record On separately before testing.

Subsequent entries show their elapsed time after the marker. Open an event to see its marker context alongside the preceding page change. Marker timing helps you navigate a test; it does not prove that a particular action caused every nearby event.

Mark a place you have already found

Open an event and choose Mark after this event. Pixel Trail anchors the checkpoint after that entry, so you can add a reference point without pretending it was recorded before the action happened.

The marker’s label is editable while you add it; use a short action description that you will recognize later. A blank label receives a numbered checkpoint name.

Show only what followed

Set Filters → Starting point → Last marker, choose a specific marker from the starting-point choices, or open the marker and choose Show events since here. Earlier activity stays saved.

Markers survive page reloads with your retained history. They can disappear when older history is trimmed, its retention period is cleaned up, or you confirm Delete all history.

Use a checkpoint to keep context. Use Clear view when the visible list itself has become too crowded.

Search documentation