See how Funl turns activity into commercial evidence.
Illustrative sample data only. The screens below mirror capabilities already implemented in the protected Funl product.
Quote to booking
What deserves attention?
High-value acquisition source, but booking completion trails desktop.
The larger observed loss appears after submission, narrowing the next investigation.
Which sources create value?
Notice unusual movement before guessing why it happened.
Funl compares the latest complete UTC day with the same weekday across prior weeks. It uses robust seasonal evidence to decide whether a move deserves investigation—without turning deviation into a diagnosis.
Same-weekday median 9,880 · -36.8% movement · robust z 4.21
Same-weekday median 4,760 · +3.2% movement · robust z 0.62
Not enough comparable history to score responsibly.
Same-weekday median $12,060 · +3.5% movement · robust z 0.48
Measured drop outside the reviewed seasonal guardrails.
The latest complete day is materially below its comparable weekday baseline and clears the reviewed robust-deviation guardrails.
What Funl does not know from this signal alone: the root cause, whether the movement is causal, how much revenue is recoverable, or what action should be taken.
Last 14 complete days
Illustrative anomaly sample only. V1 scores complete UTC days against same-weekday history, requires enough comparable data, materialises zero-activity days, and favours silence when evidence is sparse.
Define the customer journey, then inspect every step.
Funl supports saved 2–8 step page/event funnels, bounded conversion windows and optional event-property filters. This sample shows the commercial result, not raw identities.
Event steps can also be narrowed using the visual property-filter editor with equals, not-equals, contains and does-not-contain matching.
See the paths customers actually take.
Visit-scoped journey analysis groups common page/event sequences without exposing raw pseudonymous session IDs.
Turn leakage into a ranked investigation queue.
Funl ranks observed funnel losses by dropped pseudonymous visitors and drop-off rate. It deliberately does not invent root cause or “recoverable revenue”.
Quote submitted → Booked
42% drop1,202 observed visitors lost between these steps
Observed evidence · investigate, do not assume causePaid Search mobile booking
31% below desktopHigh-value source with weaker completion after quote
Observed evidence · investigate, do not assume causeSocial lead quality
2.0% conversionTraffic is present but commercial completion remains weak
Observed evidence · investigate, do not assume causeSee who comes back without durable person tracking.
Daily first-seen cohorts use Funl's rotating pseudonymous analytics identity. Cross-month retention may therefore undercount returns by design.
| Cohort | D0 | D1 | D7 | D14 |
|---|---|---|---|---|
| 01 Oct | 100% | 38% | 24% | 17% |
| 02 Oct | 100% | 41% | 26% | 18% |
| 03 Oct | 100% | 35% | 23% | — |
| 04 Oct | 100% | 39% | — | — |
Find behaviours associated with conversion or drop-off.
Funl compares page/event-label prevalence between converted and drop-off sessions using bounded descriptive odds-ratio mechanics. Association is not causation or significance.
Measure what changed after a commercial intervention.
Funl compares an equal-duration baseline with the observed period after a change. It measures; it does not allocate traffic, claim causality or choose a winner.
Shorter mobile booking form
Quote → booking+11.8%Observed change versus an equal pre-intervention baseline.
New finance explainer
Lead submission+4.6%Observed change versus an equal pre-intervention baseline.
Social landing-page rewrite
Tracked revenue-2.1%Observed change versus an equal pre-intervention baseline.
See how real visitors experience the pages in your funnel.
Funl measures browser-observed LCP, INP, CLS, FCP and TTFB when performance collection is explicitly enabled. p75 is used as the primary comparison, and the evidence is never presented as proof that speed caused a conversion result.
Where experience deserves investigation
Performance is technical evidence to investigate alongside funnels and journeys. This sample does not claim the slower page caused the observed booking leakage.
See interaction density without recording the page itself.
Heatmaps are a separately controlled capability. Funl samples click coordinates and scroll-depth thresholds only—no DOM text, form values, selectors, screenshots or session-replay stream.
/booking
1,126 sampled clicks across 284 sampled visits on this path.
The product view is an abstract coordinate canvas. Funl does not fetch or store a screenshot for this heatmap.
How far sampled visits reach
Heatmaps remain separate from full session replay. The current product does not record DOM snapshots or playback sessions.
Connect browser behaviour to server-confirmed commercial outcomes.
Funl keeps trusted backend outcomes separate from ordinary browser analytics and preserves whether a server outcome was linked to an existing browser session.
Unlinked server outcomes remain commercially useful, but Funl does not fabricate a browser journey or acquisition source for them.
The public tour is illustrative. The protected product computes these views from tenant-scoped evidence.
Funl already implements the analytics capabilities shown here. Authentication and tenant admission remain separate from the analytics product itself.
All values, company names and outcomes on this page are illustrative sample data. They are not customer results, testimonials or independent validation.