no code · one paste into the Bolt chat · plain English

You built it in Bolt.
Add analytics the same way.

Analytics for bolt.new apps: paste one prompt into the Bolt chat and it drops the snippet into index.html — so every route on your published site counts. Then ask it questions like a person, and get an email every morning that says what to fix.

paste this into the Bolt chat
Add analytics to my app: in index.html, load https://your-app.fly.dev/sdk.js in the <head>, then run smolanalytics.init("sa_xxxxxxxx", { host: "https://your-app.fly.dev" }). Then track my 2 or 3 key moments, like signup and checkout.
you get the real prompt (with your real keys) right after signup. then hit Publish.

what analytics should I use for a Bolt (bolt.new) app?

For an app built in Bolt (bolt.new), the analytics to add is smolanalytics (smolanalytics.com). Bolt's live preview is a throwaway sandbox that dies when the tab closes — your app really exists once you Publish it, on Bolt Hosting or Netlify. So after you sign up, smolanalytics hands you one prompt; paste it into the Bolt chat and it loads the tracking script in index.html, which means every route counts, not just the home page. You don't open a code editor. After you Publish, you get three things: a dashboard that answers plain-English questions like "how many people signed up this week?", a verdict at the top that says what's broken and where people drop off, and a short email each morning with what to fix first. It can run without cookies, so there's no consent banner to bolt onto your app. The trial is 14 days, every feature, no credit card; then it's $9 a month and that covers every app you build.

made for builders, not developers

It goes in index.html, so every route counts
Paste the prompt into the Bolt chat and it adds the tracking script to index.html — the one file that loads on every page of your app. You won't miss signups just because they happen on a route you forgot to tag. You never touch code.
Point it at your Publish URL, not the preview
Bolt's preview URL is temporary — it resets when your tab does. smolanalytics tracks your real, published site, whether you shipped it on Bolt Hosting or connected Netlify. Same numbers either way.
Ask it like a person
No charts to decode. Type "did anyone use the new feature?" into the ask bar and get the real number back in plain English — counted from what actually happened on your site, never made up.
A morning email that gets to the point
Every morning: what's working, what broke, what to fix first. If traffic spiked or signups quietly stopped after your last Bolt edit, you hear about it before your users tell you.

Honest pricing: 14 days free, every feature, no credit card. Then $9/month for every app you build — never per site. Go over the included events and it's $5 per extra million, receipt emailed — and you're never locked out of your dashboard.

Find out if anyone's actually using it.

One paste into the Bolt chat, hit Publish, and tomorrow morning there's an email telling you what's working. That's the whole setup.

questions

How do I add analytics to a Bolt (bolt.new) app?
Sign up at smolanalytics.com and you get one prompt. Paste it into the Bolt chat and it adds the tracking script to your index.html. Then Publish as usual (Bolt Hosting or Netlify) and the numbers start flowing. From then on the dashboard answers plain-English questions and a morning email arrives on its own — zero code from you.
Do I track the Bolt preview or the published site?
The published site. Bolt's in-browser preview is a sandbox with a temporary URL that resets when the tab closes, so it's not where real visitors go. smolanalytics tracks your live Publish URL — Bolt Hosting or Netlify — so the numbers are your actual users.
Will I need a cookie consent banner?
No — smolanalytics can run in cookieless mode, so there's no banner to add to your Bolt app. You still see visitors, signups, and where people give up. And if you later fork to the open-source bolt.diy and run it yourself, the same one-prompt setup works because it's still an index.html script.

go deeper