From domain to full journeys in four steps.
The base setup takes about two minutes and asks for nothing beyond a script tag. Everything deeper is optional and unlocked one deliberate step at a time.
Enter your domain & create an account
Type your domain, verify your email with a one-time code, and you're in. Sign-in is handled by Clerk with email verification codes — there's no password for us to store, and nothing to install yet.
Email code only · no password · ~30 seconds
Paste one script tag
Copy a single async script tag into your site's <head>. That's the entire base setup — no server access, no SDK, no build step. Journeys start appearing in your console within minutes of the first visit.
One <script> tag · journeys appear in minutes
Optionally connect more
Each connection unlocks a layer, and each is your call. Add a read-only Stripe key to verify that paying customers actually received what they bought. Connect Google Search Console to see the keywords bringing people in. Or hand your dev AI an account API key: it can create sites, flip capture abilities, and read everything the console shows.
Read-only Stripe key · Search Console · account API
Drill in, verify, ask the AI
Click any metric to see the actual people behind it and their full timelines. Check the payment-verification view to confirm every purchase unlocked what it should. And when you want a second brain, ask Claude Opus 5 — Anthropic's frontier Opus model — to read your data and suggest concrete SEO, UX, and conversion moves.
People-level drilldown · payment verification · AI insights
Two ways data reaches your console
FlowGlance has two independent inputs. Most sites start with the first; teams building with AI often add the second.
What visitors do on your site
The script tag observes your site from the visitor's side: entry pages, referrers, scrolls, clicks, dwell time, signups, payments. It runs on your visitors' browsers and reports to us on your behalf — isolated to your site, used only for your console.
Your dev AI drives the whole thing
An account API creates sites and flips capture abilities; a read-only data API returns everything the console shows — journeys, index verdicts, verified revenue. Your dev AI can set a site up, tune what gets captured, and ground its decisions in real visitor data, without you clicking through anything.
Isolated per site. Deleted on request. Never resold.
Everything fw.js collects powers your console and nothing else — no cross-site profiles, no advertising use. Deleting a site erases its data at the storage layer, immediately.
Two minutes from now, you could be watching journeys.
The free plan covers one site with full journey timelines — no card required.