In this demo bank, users who stalled at document upload opened support chat or booked a branch visit. That doesn’t look like lost interest. It looks like a step that needs help.
Funnels
The funnels that matter most
touch your most sensitive data.
Part of analytics
A drop-off is a lead,
not a verdict
A conversion rate tells you something moved. It doesn’t tell you where, who was affected or what happened next. Funnels take you through each of those from one page, with no query to write.
- Where are we losing people?
43%
of entrants lost between cart and payment, about 1,200 users a month
Every funnel opens with the numbers that decide where to look: how many users entered, how many finished, how long it took, and the one transition losing the largest share of the people who reached it. “Onboarding feels leaky” becomes something you can take into a planning meeting.
- Who is affected?
30% → 12%
Android 12’s share of users, from checkout start to payment
Break any step down by platform, app version, country or any event property, then do the same on the step before it. A value whose share shrinks is losing people faster than the others. You can also compare any cohort against everyone else, step by step, with the difference stated for you.
- What did they do instead?
Card Declined
The top event after the payment step
Countly ranks the events people did rather than continuing, so a support view or an error shows up beside the step it followed. Click any count to open the profiles behind it and read their timelines. Often that tells you which team owns the fix.
- Did the change work?
12.1% → 14.0%
Checkout conversion after the release
Trends plot conversion by entry day, so a release that helps shows up as a step up after its ship date. Compare up to four funnels side by side, with entries and completions next to the rates, so a “better converting” funnel that barely gets traffic can’t pass as a win.
Built to fit
Define conversion the way
your product works
A funnel is only useful if everyone agrees what it counts. The builder previews the result as you edit, so you know it works before you save it.
- 01Events · Filters
Steps
Any recorded event can be a step, with filters on its properties, such as a purchase above a certain amount.
- 02Sequential · Exact
Order
Let anything happen between steps and only check the order, or stop the chain at the first event that doesn’t match.
- 03Cross · Same session
Sessions
Follow each profile across sessions, or require the whole journey to happen inside one session.
- 04Optional
Completion window
Bound how long the journey may take, so a purchase three months later doesn’t count as a conversion.
- 05Optional
Exclusions
Drop anyone who triggers an event you name. They count as neither entered nor completed.
- 06Profile · Any property
Who converts
Each profile counts once, however many times it retries. Or count by any property, such as a team or an account, once its members finish the steps together.
Works with
Funnels, with the
rest of Countly
Every feature reads the same live data, so an answer in Funnels doesn’t stop there. These are the handoffs built in.
All featuresData ownership
Keep sensitive journeys
in your environment
Identity checks, payments and claims are often the flows most worth measuring, and reading them means looking at individual behavior. That makes it matter where the data lives.
Data privacyAspectFlexEnterprise
EnvironmentDedicated single-tenant instanceYour cloud, your data center or air-gapped
Data residencyThe Google Cloud region you chooseWherever you deploy, including air-gapped networks
Vendor accessOperated by Countly; access limited, granted by you and loggedNo default access
ISO 27001Certified
ISO 27017Certified
ISO 27018Certified
SOC 2Type II examined
TISAX®Participant*
*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at enx.com/tisax