Bolt has an Analytics page of its own, under the project name, then All project settings. It shows unique visitors, page views, top pages, traffic sources, locations and the pages that returned a 404. It's there only for apps on Bolt Hosting with a paid plan, and only for the last 30 days.
Bolt's help center is honest about two more limits. The numbers include crawlers and bots, with no way to filter them out. And there are no events, funnels or people, so you can see that 400 visitors arrived without knowing whether any of them signed up.
For that, Bolt's own docs suggest pasting a third-party tracking script into the project. This guide does it with Spreelytics, which is free up to 1 million events a month and runs on our servers. There are seven steps:
- Get your snippet
- Ask Bolt to add it to index.html
- Allow your app's domains
- Publish and check it works
- Tag the clicks that matter
- Identify people when they sign in
- Build your first funnel
We checked the Bolt parts against support.bolt.new on 16 November 2026.
1. Get your snippet
Sign up for Spreelytics and create an audience for your app. Open Settings → Tracking script and copy the snippet, two script tags with your client key in the second:
<script src="https://cdn.spreelytics.com/cdn/sdk/spreelytics-loader.js"></script>
<script>
Spreelytics.init({ client_key: "YOUR_CLIENT_KEY" });
</script>
The key is public on purpose. It can only send data to its own audience, which makes it safe to leave in page source and in a GitHub repo.
2. Ask Bolt to add it to index.html
Unless you asked for something else, Bolt builds web apps with React and Vite, which keep a single
index.html at the project root, and the snippet goes in its <head>. Paste this into the Bolt
chat with your snippet after it:
Add these two script tags inside the
<head>ofindex.html, in this order, before any other scripts. Don't change anything else.
Editing by hand costs no tokens. Open Code view, find index.html and paste the snippet into the
<head> yourself (Code view is read-only in Safari and on a phone, so use another browser for this).
The app changes screens without reloading. That's fine. Spreelytics counts a page view every time the address changes through the browser's history, which is how React's routers work.
This guide covers web apps. If you started Bolt with "mobile app", it built an Expo app, and a script tag doesn't run there.
3. Allow your app's domains
Spreelytics only accepts data from hostnames on the audience's Allowed domains list, in Settings → Details, so add each address your app answers on:
- the
bolt.hostaddress from your first publish (renamed, if you changed it with the pencil icon in the Publish menu) - your custom domain, if you connected one, with and without
wwwif you use both - your Netlify address, if you moved hosting to Netlify
Bolt's preview runs inside your browser on a different hostname. Leave it off. Your own testing then never shows up in the numbers.
4. Publish and check it works
Edits in Bolt don't reach the live site on their own. Click Publish, then Update.
Now open the published address in a normal browser window and click around. In Spreelytics, Settings → Tracking script should switch to Tracking is live, and you'll appear on the Realtime page within a few seconds.
Nothing there? Check Allowed domains first. Then turn off your ad blocker, which also breaks Bolt's own preview, so you may have done that already.
5. Tag the clicks that matter
A page view says someone opened your pricing page. Whether they clicked anything there is a different
question, and you can answer it without writing tracking code: any element with a data-spree-track
attribute sends an event, named after the attribute's value, each time it's clicked.
Ask Bolt:
Add
data-spree-track="signup_clicked"to the sign-up button anddata-spree-track="upgrade_clicked"to the upgrade button.
Those clicks show up on the Events page.
6. Identify people when they sign in
If your app has sign-in, through Bolt Database or Supabase, tell Spreelytics who signed in, and the visits they made while anonymous join their profile, followed by everything after.
When a user signs in or signs up, call
window.Spreelytics?.identify(user.email). When they sign out, callwindow.Spreelytics?.reset().
Each person then has a timeline, from the channel that first brought them to every page and click since. Identify users lists the other details you can attach.
7. Build your first funnel
A funnel shows how many people reach each step, and where the rest give up. Spreelytics builds funnels
out of goals. Create those first on the Goals page, each one a page path such as /pricing or an
event from step 5, then chain them on the Funnels page:
- visited
/ signup_clickedupgrade_clicked
Funnels read the events you already have, so a funnel made today fills in last week as well. Aim your next prompt to Bolt at the biggest drop.
Final thoughts
Adding analytics to a Bolt.new app takes seven steps:
- Get your snippet
- Ask Bolt to add it to index.html
- Allow your app's domains
- Publish and check it works
- Tag the clicks that matter
- Identify people when they sign in
- Build your first funnel
Bolt's Stripe integration writes Supabase edge functions that create the checkout session. Connect Stripe in Settings → Revenue, ask Bolt to put the visitor id into that session's metadata, and each payment is credited to the channel that brought the buyer. How to see which marketing channel earned each Stripe payment shows which fields to set.
Built your app somewhere else? How to add analytics to a vibe-coded app covers Lovable, Replit, v0 and Base44 too.