Where to find it
Open Lapse from the property's Tools. The left menu has Dashboard and Journeys. Both pages cover the selected property only.
Dashboard tiles
All numbers cover the last 7 days. A tile shows a dash, not a zero, until something has been counted.
| Tile | What it counts |
|---|---|
| Sessions Entered | Journeys opened by an entry event |
| Signals Emitted | Journeys that lapsed and sent their signal |
| Completed | Journeys closed by an exit event, so no signal was sent ("did the thing instead") |
| Lapse Rate | Signals Emitted divided by (Signals Emitted plus Completed), as a percentage |
Lapse Rate only counts journeys that reached a conclusion. Journeys still waiting out their window are neither lapsed nor completed, so they are left out rather than dragging the rate down.
Two more figures appear below the tiles once they are above zero:
| Figure | What it counts |
|---|---|
| Resolved Early | Signals sent straight away because the visitor started a new session, instead of waiting out the timer |
| Suppressed For Consent | Journeys that lapsed but sent no signal, because the visitor had not granted the consent the journey requires |
The How Lapse Works panel restates the journey shape, and the Journeys panel lists every journey with its status, what it watches (entry → exit events), what it emits and its window. Click Manage to open the Journeys list.
Journeys list
The list shows one row per journey, with the journey written out as a sentence, its status and its own 7-day numbers:
| Column | What it shows |
|---|---|
| Journey | Title and the sentence, for example "When add_to_cart happens, but purchase does not happen within 35 minutes of inactivity, emit cart_abandoned." |
| Status | draft, active or paused |
| Entered (7d) | Sessions that opened this journey |
| Signals (7d) | Signals this journey emitted |
| Lapse Rate | Same definition as the dashboard, with the number completed underneath |
| Actions | Edit, Clone and Delete |
A row also carries a flag when no Echo destination is listening for its emitted event. Deleting a journey asks you to confirm first; any signal it emits stops.
Warnings
These appear at the top of the dashboard, the Journeys list and the editor. Each one is a reason a journey will silently never fire or never be delivered.
| Warning | Cause | Fix |
|---|---|---|
| Echo is not sending events to Lapse | The property has no enabled Echo destination of type Lapse | Add one in Echo > Destinations |
| Your Lapse destination is not forwarding every event these journeys need | The Lapse destination's event filter leaves out an entry, exit or refresh event of an active journey, or session_start | Add the listed events to the filter, or clear the filter to forward everything |
| N active journeys emit events that nothing is listening for | No other enabled destination's event filter includes the emitted event name | Add the name to a destination's event filter, or use a destination that forwards everything |
| This window measures inactivity, but Echo is only forwarding a few events to Lapse | Editor only: the Lapse destination does not forward page_view | Forward page_view, or clear the filter |
Troubleshooting
| Symptom | Likely cause |
|---|---|
| Tiles show a dash | Nothing counted in the last 7 days. Check the journey is Active, the warnings above are clear, and your site actually sends the entry event |
| A journey is saved but nothing happens | Its status is Draft or Paused. Only Active journeys run |
| Signals Emitted rises but nothing arrives downstream | No destination is listening for the emitted event name, or the receiving destination is failing. Check the destination in Echo |
| Signals fire while visitors are still shopping | The window is shorter than the session timeout, or the Lapse destination is not forwarding browsing events such as page_view |
| Resolved Early never appears | session_start is not forwarded to Lapse, or your site does not send it |
| Numbers fall back to a dash after a quiet week | The figures are a rolling 7-day window |
| "Journey saved, but publishing it failed" | The journey is stored but not live. Save it again |