DatabasesConnect to any database and analyse your data instantly·FilesUpload CSV or Excel files and explore them with AI·ChatAsk questions in plain language — chat with your data·DashboardsBuild interactive dashboards from your queries in seconds·AILet AI write the SQL so you don't have to·ChartsVisualise trends with auto-generated charts and graphs·No-codeZero SQL knowledge needed — just ask in plain English·ShareShare live dashboards with your team in one click·InsightsSurface hidden patterns and outliers in your data automatically·ExportsDownload results as CSV, Excel, or PNG charts instantly·DatabasesConnect to any database and analyse your data instantly·FilesUpload CSV or Excel files and explore them with AI·ChatAsk questions in plain language — chat with your data·DashboardsBuild interactive dashboards from your queries in seconds·AILet AI write the SQL so you don't have to·ChartsVisualise trends with auto-generated charts and graphs·No-codeZero SQL knowledge needed — just ask in plain English·ShareShare live dashboards with your team in one click·InsightsSurface hidden patterns and outliers in your data automatically·ExportsDownload results as CSV, Excel, or PNG charts instantly·
AnalityQa
FeaturesBy rolePricingFree toolsLearnBlog
Sign inGet started
Blog›Product / Growth

Why your funnel is leaking, with the receipts

Conversion went down. The funnel chart shows it. But the chart doesn't tell you which step, which segment, and why. AnalityQa runs a multi-step investigation that returns a written diagnosis with the supporting evidence.

Try AnalityQa free →See live examples
Magnifying glass on financial charts and graphs

The problem

  • →The standard funnel chart shows the drop, but the team has to spend half a day in BI tools digging into segments, browsers, plans, traffic sources before finding the cause.
  • →When the funnel is broken across steps, devices, and segments, it's hard to know which slice is actually broken vs which one looks broken because of a small sample.
  • →Most funnel tools surface aggregate conversion but don't connect to revenue data, so the team can't tell if the drop matters financially.
  • →By the time the analyst delivers the investigation, the engineering fix has already shipped — or the lost cohort has already churned.

Why the usual approach breaks down

A single funnel chart is not an investigation

Looking at the funnel and seeing a drop at step 3 is the easy part. The hard part is figuring out whether step 3 broke for everyone, or just for mobile users, or just for users from paid traffic, or just for one new plan tier. Each hypothesis requires its own filtered query, and most teams give up after two.

Segments multiply the work

A funnel sliced by 4 channels × 3 devices × 5 plans is 60 cells, each of which needs to be checked for anomalies. Doing this in Mixpanel or Amplitude requires creating 60 reports. Doing it in SQL means writing a parametrised query and a comparison loop. Most teams just look at the aggregate and miss the segment-level signal.

Funnel tools don't talk to your revenue system

Mixpanel knows the user dropped at the activation step. Stripe knows the user never converted. Joining the two — to compute the revenue impact of the funnel drop — requires a separate data model that few teams maintain.

Diagnosis without evidence is just opinion

Saying "I think the new pricing page broke conversion" isn't enough for the engineering team to act. They need to see the funnel split before/after, by traffic source, with the magnitude quantified. Producing that takes hours of manual work — and often the answer is "actually it's something else."

How AnalityQa solves it

Upload your data — or connect it live — and ask in plain English.

01

Define the funnel in one prompt

Describe the funnel in plain English: "Funnel: visited pricing page → started signup → completed signup → activated → paid invoice." AnalityQa builds the funnel against your connected sources — product events from your DB, signup data from your CRM, payment events from Stripe — and renders the conversion at each step.

02

Multi-segment slicing on demand

After the headline funnel, ask "Now slice by channel" or "By device + plan tier." Each slice runs against the same definition. AnalityQa flags slices where conversion deviates from the aggregate by more than a configurable threshold — so you don't have to read 60 cells, just the ones that matter.

03

Investigation mode for funnel drops

When weekly conversion dips, ask "Why did funnel conversion drop 12% this week?" AnalityQa runs a structured investigation: checks the segment mix, the per-step conversion rates, the time-of-day patterns, the recent product/marketing changes. Returns a written diagnosis ranked by contribution to the drop.

04

Revenue impact attached to the diagnosis

Each step of the funnel is joined to revenue automatically. A drop at the activation step is reported in dollars: "This drop cost an estimated $14K of MRR over the past 4 weeks." The engineering team gets to prioritise based on impact, not just rate change.

05

Live funnel dashboard

Pin the funnel — with segment slicing controls — to a dashboard. The dashboard refreshes on schedule. PMs and growth see the funnel as it changes day-to-day, not as a quarterly review.

You askedGenerated in 4.2s

"Build a funnel: pricing page view → signup start → signup complete → activated → paid. Show conversion at each step for the past 30 days."

MQLs

2,418+18.2%

CAC

€142−9.4%

ROAS

4.2×+0.6×

Funnel chart with conversion at each step

Last 12 mo

4-line funnel comparison

Investigation report with three driver panels and revenue impact

A dashboard built in AnalityQa — from question to chart, no SQL.

Real examples

Paste your data. Ask. Ship.

You

Build a funnel: pricing page view → signup start → signup complete → activated → paid. Show conversion at each step for the past 30 days.

AI

Funnel built. Visit→signup-start: 14%. Signup-start→signup-complete: 71%. Signup-complete→activated: 38%. Activated→paid: 47%. Overall: 1.8% from pricing visit to paid. The biggest drop is signup-complete→activated.

Funnel chart with conversion at each step
You

Same funnel, but split by traffic source.

AI

Organic: 2.4% overall conversion. Paid Google: 0.9%. Direct: 2.1%. Partner referral: 4.8%. Paid Google's drop is concentrated at the signup-complete→activated step (22% vs 38% for organic). Worth a look.

4-line funnel comparison
You

Why did funnel conversion drop 12% this week?

AI

Weekly conversion fell from 1.9% to 1.67%. Driver 1 (61%): activation rate dropped from 38% to 28% on mobile devices specifically — likely tied to the OAuth update shipped Tuesday. Driver 2 (24%): traffic mix shifted toward paid Google (which converts at 0.9%). Driver 3 (15%): unexplained noise. Estimated revenue impact: −$8.4K MRR if the trend continues 30 days.

Investigation report with three driver panels and revenue impact
You

Compare last week's funnel to this week's, segment-by-segment, and highlight the segments where the drop is statistically significant.

AI

23 segment cells flagged. The 4 statistically significant drops (p<0.05): Mobile + Paid (−18pts at activation), iOS Safari + any source (−14pts at signup-complete), Pro plan signups (−9pts at activation), Brazil traffic (−21pts but small sample, n=42).

Heatmap: segment × week, with significance flags
You

What's the revenue impact of the activation-step drop on mobile?

AI

The 10pt activation drop on mobile, applied to ~340 weekly mobile signups, costs ~34 activated users per week. Historical activated→paid is 47%, average MRR per paying customer $89. Estimated impact: 34 × 0.47 × $89 = $1,420/week, or $73K/year if not fixed.

Revenue impact summary

Note from Alex

The first time a PM asked me why their funnel had dropped, I watched them spend three hours pulling Mixpanel reports and never find the answer. The data was all there — it just lived in three different tools with no way to connect them. That's the problem I built this for: not a better chart, but an actual investigation that returns a written diagnosis with the evidence attached.

— Alex, Co-founder, AnalityQa

What teams get out of it

✓Funnel drops get diagnosed in under a minute — drilled down to step, segment, and dollar impact.
✓Diagnosis includes which segment, which step, and the dollar impact — not just "conversion is down."
✓Engineering and growth prioritise based on revenue impact, not on whichever metric was most recently shouted about.
✓Live funnel dashboard catches regressions the same day they ship instead of the same week they're noticed.

Frequently asked questions

Do we need to instrument new events for this to work?+

Only if the funnel step you want to track isn't already in your data. AnalityQa works with whatever events you currently log. Most teams find their existing event coverage is enough for 80% of useful funnel questions. For the missing 20%, you instrument once and the funnel updates automatically.

How does AnalityQa handle deduplication when one user fires the same event twice?+

Default behaviour is one event per user per step (first occurrence). You can override: "Treat repeated signup events as separate funnels" if you have a flow where a user genuinely re-enters the funnel. The dedup rule is shown in the chat so you can verify it matches your model.

Can the funnel investigation account for cohort effects — like a marketing campaign that brought in a different audience?+

Yes. The investigation explicitly checks for segment-mix shifts and isolates them from per-segment conversion changes. The diagnosis usually says "X% of the drop is mix shift, Y% is per-segment regression" so you don't blame engineering for a marketing-mix change.

How does the revenue impact get computed?+

AnalityQa joins the funnel users to your billing data, computes the typical conversion-to-payment rate and average MRR per paying customer for that segment, and projects the impact of the funnel change. The math is shown so you can audit it.

Can we set up an alert when the funnel drops by more than X%?+

Yes. Pin the funnel dashboard with a refresh cadence and configure an alert (Slack or email) that fires when total conversion or any segment-level conversion drops below a threshold. Most teams set it to fire on a 7-day rolling window to avoid daily noise.

Will the investigation always find a clear cause?+

Not always. Sometimes the drop is noise (small sample) or genuinely unexplained by the available data. AnalityQa is honest about this: when it can't find a driver above the significance threshold, it says so and reports the unexplained portion explicitly. You then decide whether to instrument more or wait for more data.

Does this work for B2B funnels with longer sales cycles?+

Yes. Define the funnel steps over the longer time window: "Demo request → discovery call → proposal → contract signed." The investigation logic is the same. Segment slices by ICP fit, AE owner, deal size become the relevant axes.

Related guides

SaaS / Customer Success

Find Where Onboarding Breaks and Fix It With Data

SaaS / Product

Find the activation moment that converts trials

Product

Know If Your Feature Launch Is Actually Working

Run this analysis on your own data.

Upload a file or connect your database — 100 credits free, no credit card. Your first dashboard ships in under 5 minutes.

Try AnalityQa free →

No credit card required

AnalityQa

Your AI data analyst — for anyone with data and questions.

Product

  • Features
  • Pricing
  • Blog
  • Free Tools

Company

  • About
  • Contact

Legal

  • Privacy
  • Terms

© 2026 AnalityQa AI. All rights reserved.

All systems operational