Analytics shows no data yet

What it is

An all-zero dashboard means one of a small number of things, and almost none of them are a fault. The page tells you as much when it happens: No data for this period, "Activity will appear here once your chatbots start chatting."

This article is the checklist, ordered by how often each cause turns out to be the real one.

When you would use it

Right after a launch, when you expected to see something. When a dashboard that had numbers yesterday has none today. Or before you report a bug — every item below takes under a minute to rule out.

Where to find it

Dashboard. You will also want Dashboard → Accounts, Dashboard → Chatbots, and Dashboard → Settings → Appearance while you work through the list.

Steps

Work down in order. Stop when one of them explains it.

1. Are you in the right workspace? Open the account switcher. A member looking at their own personal workspace sees their own empty analytics, not the team's. This is the single most common cause and it takes five seconds to check — see Switch accounts.
2. Do you have a chatbot at all? Open Dashboard → Chatbots. With no chatbots, the dashboard shows setup guidance instead of charts, and there is no date-range picker.
3. Has anyone actually sent a message? Not opened the widget — sent a message. A session with no messages is not counted as a conversation, deliberately, so that curiosity clicks do not inflate your chart.
4. Is the range wide enough? The default is 7 days. If your traffic was ten days ago, switch to 30 days.
5. Is your timezone right? A range boundary sits at midnight in your timezone. Evening traffic can fall outside a window you thought it was inside — see Why your dashboard days start when they do.
6. Is a chatbot filter still applied? Filtering to a quiet chatbot looks identical to having no data.
7. Is the chatbot actually reachable? A paused chatbot's hosted page returns a not-found and its widget is refused, so visitors cannot generate anything to measure. See Activate or pause a chatbot.
8. Are you out of message credits? With the meter empty, visitors get an unavailable message rather than an answer. Check Settings → Billing as the owner — see We are out of credits.
9. Is the widget being blocked? A widget refused on your domain never gets as far as a conversation. See The widget is blocked.
10. Have you waited a minute? Figures are cached briefly. A message sent seconds ago may not have surfaced yet.

The distinction that catches most people

Traffic is not conversations, and conversations are not messages.

• Someone loading a page with your widget on it: nothing is recorded.
• Someone clicking the bubble and reading the greeting: still nothing. An empty session is deliberately excluded so the chart is not full of phantom bumps.
• Someone typing a question and getting an answer: now it counts — one conversation and at least one message.

So a dashboard reading zero after a busy launch day usually means people saw the chatbot and did not talk to it. That is a real finding worth acting on, not a reporting bug. Move the bubble somewhere more visible, or set a greeting that invites a question — see Chatbot messages and language.

Testing it yourself, properly

To prove the pipeline works end to end:

1. Open your chatbot's hosted page, or your live website, in a private window. Arrive as a stranger, not as the signed-in owner.
2. Send a real question and wait for the answer.
3. Wait about a minute.
4. Refresh the dashboard on the 7-day range.
5. You should see one conversation and at least two messages.

If that appears, everything is working and the earlier zeros were genuinely an absence of visitors.

One thing to know before you test: messages you send from the owner's test chat drawer do count towards your analytics. They are not filtered out. That is fine for proving the pipeline works, but it means a launch week where you tested heavily will report numbers that are partly your own. Note how much testing you did before you present the first week's figures to anybody.

Limits and plan notes

Analytics is not a paid feature. Every plan has the same dashboard. Upgrading will not make numbers appear; visitors will.

Deleting a chatbot does not reset your charts, and deleting one to "clean up the numbers" is a bad trade — you lose the chatbot, its knowledge, its public link, and its conversations. See Delete a chatbot.

A member scoped to selected chatbots sees analytics for those chatbots only. Their zero and the owner's non-zero can both be correct.

Only the last 90 days is reachable from this page.

Common problems

I chatted as the owner and still see zeros.

Confirm the range includes the time you chatted in your timezone, and that no chatbot filter is applied. Then hard-refresh. Owner test messages do count, so they should appear.

I have customer records but analytics is empty.

Possible and consistent. A lead form can create a contact before any answered message exists — a visitor who completed the form and then left produces a customer and no conversation. See Where leads come from.

Everything was fine yesterday and is zero today.

Either the range rolled over midnight and today is genuinely quiet so far, or something stopped visitors reaching the chatbot. Check credits, the chatbot's status, and the widget in that order.

My teammate sees numbers and I do not.

Different workspace, different chatbot scope, or a different range. Check all three.

Zero conversations but the response-time chart has a line on it.

Refresh. Different figures settle at slightly different moments, and a stale cached fragment can briefly disagree with a fresh one.