648
visitors identified
3 companies read pricing 4x this week → top of the list this morning
- Sources
- 31
- Returning
- 22
- Matched
- 14
Flowgrid captures the name, email and company as they are typed — no submit required — matches them to the contact in your CRM, and shows your team what they were reading.
Works with the CRM you already use · One click with Google · No credit card
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.
The visits are all there, in sessions, sources, form reports and whoever owns the spreadsheet. Turning one into a person, an account and a reason to call is still a job someone does by hand — usually the rep who should be on the phone instead.
Sessions are up again. None of them have names.
Only the people who finished. The rest left no trace.
Wait for whoever owns the spreadsheet.
Paste addresses in one by one to see who is already a contact.
Third pricing visit or an idle tab? The report cannot tell you.
By feel, because nothing in front of you is ranked.
Retype what you found onto the contact record.
By then they have booked a call with someone else.
Question
No query to write and no list to export first.
Investigation
Walks the visits, the form starts, the repeat sessions and your CRM.
Evidence
The visits, the fields captured and the matching contact sit beside the answer.
Answer
Who it was, what they read and when they went quiet.
Action
A note on the contact, a report or a pull request. Nothing writes 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.
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.
One package and one init call, or one script tag on any platform.
Pages, sessions and campaigns with no tracking plan first — and the name and company off your own forms, captured as they are typed.
As soon as traffic lands, there is a list to work rather than a chart to read.
The install is small enough that an agent can do it from the README.
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.