Find where a conversion path breaks
Build an ordered funnel from two to five page or event steps. See how many daily anonymous visitors reach each step and where the path loses momentum.
How to install ↗Use pageviews and product events together
A signup funnel can start at /pricing, continue through signup_started, and finish at signup_completed. Page steps match a path; event steps match a named custom event.
Read the denominator
The current funnel groups by the daily server-derived identifier and tests ordered steps within its window. It measures observed daily visitor progression. A return after UTC midnight has another anonymous ID and cannot complete the earlier anonymous funnel.
Investigate a drop-off
Select a date range and segment by campaign, page, device, country, browser, or operating system. Use the activity feed or replay to inspect possible reasons, then compare a change against the same measurement rules.
Know the current boundary
Advanced exclusion steps and persistent cross-day anonymous funnels are not implemented. A separate thirteen-week retention report supports explicit users and unambiguous consented identities in Attribution mode. The funnel endpoint still groups by daily ID.
Frequently asked questions
How many steps can a funnel have?
The API validates two to five ordered page or named-event steps.
Can a funnel cross midnight?
The anonymous identifier changes at UTC midnight, so the current daily-ID funnel cannot connect those visits.
Does identify make the funnel cross-day?
No. The current funnel endpoint groups by the daily identifier; identified cohort funnels require a separate reporting implementation.
Start with a clear measurement model.
Install the SDK, then explore traffic and product activity with the same definitions.