Analytics and customer support for an app built in Bolt

You built it fast. Now people you have never met are using it, and you can see neither where they came from nor what they are stuck on. Deacon is one script tag that fixes both, and Bolt already documents how to add one.

Last reviewed September 2026

What the build gave you, and what it did not

Bolt gave you

  • An app, from an idea, in an afternoon
  • Hosting and a public URL, both handled before you asked for them
  • Code you can open and change whenever you want to

Nobody set up

  • The preview showed you the app. It never showed you a stranger using it
  • Your bolt.host address is public and nothing there is counting
  • Strangers who get stuck have to go looking for a way to reach you
  • Whatever you shipped this morning, nobody wrote down what it broke

Try Deacon for free

Install Deacon

Seven things that change once the tag is on

A question at eleven at night

Deacon
Answered there and then from your help pages, with the page it came from linked underneath.
Without it
It waits in your inbox until morning, by which time they have made other plans.

Where the traffic came from

Deacon
Recorded as it arrives. Sources, pages, countries and devices, on the same tag.
Without it
A separate analytics product, installed separately, read separately.

The question you keep answering

Deacon
Grouped with every other wording of it, so you can see it is the top one.
Without it
A feeling that you have typed this before.

Questions nothing covers

Deacon
Listed for you. Write the answer once and it joins your knowledge base.
Without it
Answered by hand each time, or answered wrongly by a bot that guessed.

Consent banners

Deacon
Not needed for the counting. No cookie is set and no visitor address is stored.
Without it
One more banner between a visitor and your product.

Getting started

Deacon
50 answers a month on one seat, free, and no card to start.
Without it
Two products to sign up for before either of them tells you anything.

Deciding what to build next

Deacon
The questions nothing answered, ranked by how often people asked them.
Without it
Whichever complaint you happened to read most recently.

Three things worth knowing

Bolt already documents this

Adding a third-party script is a supported thing to do, not a workaround. Bolt’s own hosting documentation covers third-party analytics and tells you to paste the code in Code view or ask Bolt in the chat to place it for you. Deacon’s snippet is the same kind of code.

A prototype and a product need different things

Bolt is very good at getting something real in front of people quickly. The moment those people are strangers rather than friends, you need to know how they found you and what they could not work out, and none of that was part of building it.

The chatbox route is the fast one

You do not have to find the file. Paste the snippet into the same chatbox you built the app in, ask Bolt to add it, and it goes where it needs to go. That is Bolt’s own documented answer for third-party scripts, not a trick.

Putting it in

Open Code view and paste the snippet before the closing body tag, or paste it into the chat and ask Bolt to place it. Bolt’s own hosting documentation names both routes for third-party scripts, so neither is a workaround.

Before that, add your address in Deacon. The widget runs only on the domains you have listed and stays quiet everywhere else, which is the usual reason a first install looks like it did nothing. If you are on a generated bolt.host subdomain, that is the address to list.

Check it on the published site rather than in the preview. The install guide covers adding your help pages and the rest of the dashboard.

Deacon on a Bolt app, answered

Two ways, and Bolt documents both routes for third-party scripts. You can switch to Code view and paste the snippet in yourself, before the closing body tag, or you can paste it into the chatbox and ask Bolt to place it, which is usually quicker. Bolt leaves the exact location to whoever wrote the script, and ours wants the end of the body. Nothing else needs configuring.

Yes, as long as you list that address in Deacon. The widget only runs on domains you have added, so a project on a generated subdomain needs that subdomain listed. A custom domain is a paid feature on Bolt, so a free project is published on the generated one. Add the address you are actually publishing to and it will work.

Judge it on your published site rather than in the in-browser preview. The preview relies on a browser feature that only Chromium has, so what loads there is not a reliable guide to what your visitors get.

No. The same script tag that runs the widget counts page views, and both show up in the same dashboard. There is nothing extra to install and nothing extra to pay for.

The free plan gives you 50 answers a month on one seat. No card, and it does not run out after a fortnight. Counting page views costs nothing on any plan.

Try Deacon for free

The next person who cannot find something gets an answer instead of a contact form. That is the whole change, and it is one line.

See what Deacon does, or read the plans and prices.

READ NEXT