Get data flowing. Then just ask.
Set up in one step, then ask your numbers in plain English. The dashboard ask bar answers about your data and shows your real events and pages so you never guess what to type. Your coding agent answers code-aware questions over MCP. Same reports underneath, so the numbers always agree.
Pick the row that sounds like you
One of these gets events into your instance. After that, everyone asks the same way.
I have a website or web app
- 1Sign up and create a projectYou get an isolated instance and a write key, in about a minute. No card.
- 2Drop one script tagPaste the snippet into your site's <head>. It autocaptures pageviews and clicks right away. Add track() for the key moments (signup, checkout) when you want funnels.
- 3Ask, or read the morning emailThe dashboard opens with the verdict. Ask 'where do people drop off?' in the ask bar, or just read the brief that lands each morning.
<script src="https://YOUR-INSTANCE/sdk.js"></script>
<script>smolanalytics.init("YOUR_KEY", { host: "https://YOUR-INSTANCE" });</script>I built my app with AI (Lovable, Bolt, v0, Replit)
- 1Sign upYou never open a code editor or a terminal. Signup hands you one prompt with your key already in it.
- 2Paste the prompt into your builder's chatYour builder's AI drops the tracking in the right place for that platform. We have a page for each one with the exact prompt and where it goes.
- 3Come back to the dashboardIt fills in live, answers your questions in plain English, and the morning email starts the next day. Zero code from you.
I code in Cursor or Claude Code
- 1Connect onceOn the cloud, paste your organization's MCP token (from Settings) into your editor: one connection operates every project, you pass a project name to reach any of them and the read key stays server-side. Self-hosting, run smolanalytics connect to wire every assistant to your local instance. Restart the editor.
- 2Ask in the same window you write code"what's the mau for the PQR page?" works because your agent knows PQR is the /pqr route from your code, then queries smolanalytics for it. Your own model answers, so the ai part is free. No api keys.
- 3Trust the numberYour AI assistant admits it can hallucinate your numbers. This one can't. The answer comes from the same deterministic reports the dashboard renders.
smolanalytics connect # wires up cursor, claude code, and the restthe editor-native guide →
Two ways to ask, for two kinds of question
One asks about your data. The other asks about your code. Knowing which is which is the whole trick, so here they are, side by side.
Type a plain-English question and get an exact number back, computed deterministically, no model needed. It answers about your DATA: 'how many checkout this week?', 'where do people drop off?', 'visitors to /pricing'. It does not read your code, and it does not have to: the dashboard shows your real event names and top pages as clickable chips, so you pick what to ask instead of guessing what things are called.
Connect once (on the cloud, one org token operates every project; self-hosting, run connect) and your editor's own model gets smolanalytics plus your codebase plus the tracking plan (smolanalytics.plan.json). This is where codebase-aware questions work. Ask 'what's the MAU for the PQR page' and your agent knows PQR is the /pqr route from your code, then pulls the number. It can also instrument new flows and verify they fire. Same reports underneath, so it never disagrees with the dashboard.
Pin the metrics you check daily
Build a funnel, trend, breakdown, or retention view once and pin it, or have your agent call save_report. It shows on your board, pinned to your dashboard, every visit, so the numbers you watch every morning are one glance, not a re-typed question.
Answers cover all your history by default
That's the default. Scope any question with today, yesterday, this week, last week, this month, last month, or last N days, and the answer tells you the exact range it used, so a number is never silently measured over the wrong window.
Incumbent-level depth, behind a plain-English question
Under the ask bar is a full product-analytics engine, the same reports Mixpanel and Amplitude give you, computed exactly. You reach any of it three ways: ask in plain English, ask your editor over MCP, or open the full dashboard. Every answer is the same deterministic report, so it can't drift.
Any sequence of events, with per-step drop-off, overall conversion, and the median time to convert. Break the whole funnel down by any property (source, plan, country) to see who converts and who stalls.
Daily, weekly, or monthly cohorts, a rolling/unbounded mode, and an anchor on the returning action that matters (“retention on activate”), with honest denominators: only cohorts old enough to observe a period are counted.
The real screen-to-screen and page-to-page routes people actually take, and exactly where they fall out.
Reusable definitions, did-any / did-all of an event set plus property filters, applied across every report, so “pro users from HN” is one saved thing.
New, returning, resurrected, and dormant users over time, plus DAU/WAU/MAU stickiness: is your product a habit or a one-time visit?
Up to 8 events on one chart at hour/day/week/month with the prior window ghosted behind, and any metric broken down by country, browser, device, UTM, or any property you send.
Total, average, median, and p90 over any numeric property, revenue per day, average order value, p90 latency, not only event counts.
A real filter builder on everything: is / is not / contains / regex / greater-than / less-than / set / not-set, AND or OR, with value typeahead from your own data so you pick, never guess.
Click any visitor and see everything they did, in order, with their traits and first/last seen, the clean per-user timeline GA4 never gave you.
Roll events up by account or organization, not just by user, so you read usage the way a B2B product actually sells.
Record a deploy (git sha + message, one line in CI, or auto-synced from GitHub) and smolanalytics ties every metric change to the ship behind it: a before/after per deploy. Ask "did my last deploy move signups?" and get the number. No other analytics tool can. They have your data but not your deploys. Correlation, not proof, and the copy always says so.
The dashboard opens with what to FIX, biggest drop-off, spikes, retention breaks, not a wall of charts of what happened. A morning brief email covers every product you run. You start at the answer, not the exploration.
Who is this for?
Built for agent-native indie developers and small builders. Not for a data team that wants a distributed event warehouse. That's a different tool. smolanalytics is for people who want a straight answer without the ops.