Analytics
Funnel analysis you can act on
Pick the events, set a window, see exactly where people drop, then fix the leaky step with an automation instead of just staring at the chart.
How it works
From events to a funnel.
Three steps, no SQL, no dashboard export.
01
Pick 2 to 5 events and a window
Choose any events you already track, sign up, added to cart, sent first email, in the order you expect people to complete them. Set a conversion window from an hour up to 30 days.
02
See step-by-step drop-off
Each step shows the count that reached it and the percentage that fell off before the next one, so you're reading a real breakdown instead of guessing which step is the problem.
03
Spot the leaky step
One step almost always loses more people than the rest combined. That's the step worth fixing first, and the one you can point an automation at directly.
The difference
The part other funnel tools skip.
Every funnel tool on the market can show you the leak. Google Analytics, Amplitude, Mixpanel, PostHog, they all draw the same shrinking bar chart and tell you 40% of people dropped between step two and step three. That part is solved, and it has been for years.
What happens after you see the leak is where most of them stop. You export a segment, hand it to marketing, and wait for someone to build a campaign in a different tool with a different definition of who actually dropped off.
GetFluxly skips the handoff. Attach a lifecycle automation directly to the leaky step in the funnel builder, and anyone who reaches that step without moving forward gets the triggered email automatically. The funnel doesn't just report the drop, it drives the fix. See how this fits the rest of analytics.
Under the hood
Built on real behavior.
No separate funnel pixel, no unlimited step chains, no cookie banner to measure conversion.
Real events, not page tags
Funnels run on the events you already send through the SDK, page views, custom events, server events, not a separate pixel with its own tagging rules to maintain.
2 to 5 steps with a conversion window
Every funnel is 2 to 5 ordered steps and one conversion window, from an hour to 30 days. No unlimited step chains that turn into a report nobody reads.
Cookieless by default
Funnels run on the same gfh_ server-hash ids as the rest of analytics. No fingerprinting, no storage before a visitor identifies themselves, no banner just to measure conversion.
Segment the funnel by trait or channel
Filter any step by a trait like plan or a channel like referrer, then save it as a full segment when you want to reuse the same audience elsewhere. It sees your schema, not your customers.
FAQ
Questions, answered.
What is a funnel?
A funnel is an ordered sequence of events you expect people to complete, like Viewed pricing, Started signup, Sent first email. GetFluxly counts how many people reached each step and shows the percentage that dropped off before the next one.
How many steps can a funnel have?
Between 2 and 5 steps, on any events you're already tracking. Keeping the range tight keeps a funnel readable instead of turning into a step chain nobody checks.
Can I filter a funnel by segment?
Yes. Filter any step by a trait like plan or a channel like referrer to see whether the drop-off is concentrated in one segment or spread across all of them.
How do I fix a drop-off once I find it?
Attach a lifecycle automation to the leaky step. Anyone who reaches that step without completing the next one gets the triggered email automatically, no export, no separate campaign tool.
Do funnels need cookies or a consent banner?
Most teams running analytics-only tracking don't, but check your own obligations. Funnels run on the same cookieless gfh_ server-hash ids as the rest of GetFluxly analytics, computed server-side with zero storage before a visitor identifies themselves.