648
visitors identified
3 companies read pricing 4x this week → top of the list this morning
- Sources
- 31
- Returning
- 22
- Matched
- 14
Your web, product, customer, and behavioral data into one system. Ask questions in plain English, investigate the evidence, and turn insights into action with AI.
Demo form · 14:02
Company
Left without submitting. Passwords and card fields are never read.
Pricing · 3rd visit
/pricing · 6m 12s
Same visitor, same week — not a new anonymous session.
CRM · Matching…
Checking your contacts…
Note ready for the contact record. Nothing writes without your approval.
Most analytics tools tell you what happened. Flowgrid helps you understand why — bringing the evidence together so you can go from a question to an answer to an action without stitching together five different tools.
A chart dips. Nobody can say why yet.
Analytics, replays, the CRM, last week's report.
Which events, which pages, which date range.
Or wait for whoever knows how to.
New or returning, mobile or desktop, free or paid.
One recording at a time, hoping to spot the pattern.
Stitch the clues together by hand.
By then the change has been live for a week.
Ask
"What caused checkout conversion to drop?"
Investigate
The segments, events, sessions, journeys and product data behind the question.
Understand
The evidence behind the change, instead of a guess from a dashboard.
Act
An experiment, a report or a pull request. Nothing changes without your approval.
One question. Here is everything Flowgrid put on the table to answer it, and every piece opens to the data underneath.
Anomaly
Checkout conversion −14%
Break flagged on Sep 14
Affected segment
12,481 visitors on iOS Safari
Relevant events
The drop is at payment
Last week vs this week, share of checkout starts
Session evidence
Error sessions 30 → 96 a day
Visitor 8f2c
iPhone · Safari 18 · 4m 12s
maya@northwind.co
iPhone · Safari 18 · 2m 48s
Visitor 31ad
iPad · Safari 18 · 6m 03s
Rage clicks on “Pay now” in 431 sessions
Timeline
Started Sep 14, 14:20
First failing session 14:20
Likely cause · next action
Payment step, iOS Safari only
components/checkout/PaymentForm.tsx
Error text matches the card-expiry validation in your connected repo
Visits, identity, replays, funnels and your CRM — one system, so working out who a visitor is and what they were after never needs an export in between. Open any of them directly, too.
Put a name and a company to traffic that never filled anything in, then match it against the contacts already in your CRM.
Which accounts read your pricing page, how often they came back, and the channel that brought them — not another sessions count.
Watch the demo form being abandoned. You know the field they stopped on before you pick up the phone.
Events, retention and segments behind each account, so whoever takes the call knows what the buyer has actually used.
See which accounts adopt what. Stalled usage is a save call; heavy usage is an expansion one.
Define what counts as pipeline here — demo starts, pricing revisits, qualified accounts — and watch it move live.
Ingest doesn't keep office hours. The visits, the form starts and the identities behind them land while you're gone, and your KPIs recompute overnight on a schedule nobody has to remember. You come back to a list that is already current.
648
visitors identified
3 companies read pricing 4x this week → top of the list this morning
37
demo forms abandoned
Most stopped on "company size" → the field, not the offer
1,284
events behind open deals
Two trials stalled before import → surfaced on the account

Ask it in your own words. The answer comes back off your own visitors — who they were, what they read and the session behind it. No SQL, no ticket, no waiting on whoever owns the list.
"Who started the demo form and left?"
Nine people yesterday. Six are already contacts in your CRM, with the field they stopped on attached.
"Which accounts are warming up?"
Repeat pricing visits over the last fortnight, ranked, each with the matching contact and the sessions behind it.
Variant B reached significance
You didn't ask for this one: it recomputes every half hour, so the verdict is current whenever you look.
See how experiments workFlowgrid records what your visitors do, never what they type, and your team decides who sees it. The agent proposes; a person approves.

Every other tool hands you a chart and wishes you luck. This one drafts the note on the contact and opens the pull request with the evidence attached — then stops. It can write the draft; only you can send it.
Full breakdown on the pricing page
Everything you need to see whether the numbers move. No card.
For early SaaS and e-commerce teams adding deeper analysis.
For growing teams replacing separate analytics tools.
For teams that need higher volume, more seats, and full control.
For organizations that need a custom plan and priority support.