Help Center Analytics

​

What you get

The Analytics tab (/dashboard/help-center/analytics) gives you visibility into how your help center is being used:

​

Time periods

Filter analytics by:

• 7 days
• 30 days (default)
• 90 days

​

Breakdowns

The analytics API supports two breakdowns: The dashboard surfaces these as different tabs / panels in the Analytics view.

​

Zero-result queries

Probably the most valuable metric for your AI/help center strategy. When customers search for something and nothing comes up, that’s a content gap. Halo shows zero-result queries in a dedicated panel. Workflow:

1. Review zero-result queries weekly
2. For high-frequency ones, write an article
3. The new article auto-feeds your AI’s knowledge base too — so the next time someone asks the same question in chat, the AI can answer

This loop tightens your support over time.

​

Public telemetry

Public help center pages send pageviews to /api/help-center/analytics/pageview:

• CORS-enabled
• Rate-limited per IP
• Records pageviews and links to help_center_id, article, collection
• Used as the source of truth for the analytics dashboards

You don’t need to wire anything up — it works automatically once your help center is live.

​

Limitations

A few things to know:

• No identity-resolved analytics — pageviews are anonymous unless the visitor is authenticated via your help center auth
• No funnel/journey tracking — pageviews are individual events, not stitched into journeys
• No exports — analytics data is read-only in the dashboard today

For more advanced analytics, you can plug Google Analytics or GTM into your help center via Settings > GA Measurement ID / GTM ID. That gives you the full GA toolkit on top of the help center.

​

Reactions

Articles can have thumbs up / thumbs down reactions enabled (see Design). The Analytics tab aggregates reactions per article so you can see which articles are landing well and which need work.

​

Where to go next