Every team builds their own tracking. We built the managed version.
The event script, the database, the dashboard nobody quite trusts — you've built some version of this before. Flowgrid is the same idea, run by someone else: a typed SDK and real infrastructure, without the quarter it took to build or the one it takes to keep alive.
- page
- /pricing
- referrer
- google.com
- campaign
- spring_launch
- device
- Mac · Chrome
- country
- United Kingdom
- session
- 4m 12s · 7 pages
You named the event. Everything under it arrived on its own — no schema, no properties to remember at the call site.
- One tag
- Every eventPageviews, clicks, forms and Core Web Vitals the moment the tag loads — no plan required.
- npm · typed
- Not a snippetA real package with autocomplete, server-side tracking and a lint-clean API surface.
- Ask · plain English
- Answers, not dashboardsAsk what changed and get the funnel, the replay and the fix to ship.
The in-house version
8 parts
1 part
Every one of them is something a team writes, deploys, pays for and gets paged about — before anybody has read a single number.
What stays in your repo
<script src="https://core.flow-grid.xyz/flowgrid.js" defer></script>You still get all 8.
You only run one.
Ingest, queue, store, identity, dashboards and the pager do not disappear — they stop being yours to keep alive. The only part left in your repository is the tag.
One subscription in place of the stack you're running today
Don't take the page's word for it.
Two ways to look at a real workspace before you put a tag on anything. Neither of them needs a card.