Core features
Funnels
Define the path you expect, then watch where visitors leave it.
Building one
A funnel is an ordered list of steps. Each step matches either a page or an event, and they are evaluated in order — a visitor reaches step three only by having passed steps one and two.
| Step type | Matches on |
|---|---|
page | A path, such as /pricing. Wildcards are supported, so /blog/* covers every post. |
event | A custom event name you send with seentics.track(). |
custom | A condition you define, for cases the other two do not cover. |
checkout.js
// Makes 'signup_complete' usable as a funnel step.
seentics.track('signup_complete');What the report tells you
Two percentages per step, and the difference between them is the whole point of the page.
| Figure | Means |
|---|---|
| % of entries | Share of everyone who entered the funnel that reached this step. Falls away down the funnel. |
| % continued | Share of the previous step that carried on to this one. This is the one that finds a broken transition. |
| Left here | How many people reached the previous step and did not reach this one. |
Why “% continued” is the useful one
A late step can look fine against total entries simply because few people get that far, while losing most of the visitors who actually reach it. The funnel view calls out the biggest single drop-off for exactly this reason.
Then go and look
- Watch replays of sessions that reached the weak step and stopped.
- Check the heatmap for that page — often the next action is below where anyone scrolls.
- Then set up an automation that responds when someone is about to drop out.
Reporting window
The funnel detail page reports on the last 30 days. Historical figures are available over the REST API.