Funnels
Define a conversion path from the events you already collect, and see where people drop out.
A funnel is an ordered list of steps. Annot8 counts how many visitors reached each one, and shows you where the drop-off is.
Funnels live under Project → Analytics → Funnels and require Analytics to be enabled and consented.
Defining one
Give the funnel a name, an optional description, and two or more steps. Each step matches one kind of event:
| Step type | Matches on |
|---|---|
pageview | A URL pattern, wildcards supported |
click | A CSS selector |
custom | An event name you send via track |
conversion | A conversion name you send via trackConversion |
A worked example
Signup flow:
| # | Step | Type | Match |
|---|---|---|---|
| 1 | Landing page | pageview | / |
| 2 | Pricing viewed | pageview | /pricing |
| 3 | Signup clicked | click | [data-cta="signup"] |
| 4 | Account created | conversion | signup_completed |
Steps 1–3 need no code — they match on things the widget already collects. Only step 4 needs a line in your app:
window.Annot8("trackConversion", "signup_completed");Reading the result
Each step shows how many visitors reached it and the drop-off from the step before. The steps are ordered, so a visitor has to have hit step 2 to count at step 3.
Funnels can be viewed over 7, 30, or 90 days.
Getting useful answers out of it
- Start coarse. Three steps that you understand beat eight you have to squint at. Add detail once you know which gap is the big one.
- Instrument the end, match the middle. Conversions are worth an explicit
trackConversioncall because they're the number you'll quote. Intermediate steps are usually fine as pageview or click matches. - Pair it with feedback. When a step drops off hard, filter the inbox to that page. The funnel tells you where people leave; the feedback tells you why.