> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/knowledge-base/analytics.md). # Analytics See how your knowledge base is used, what customers search for, and how helpful articles are. Knowledge base insights live in the **Insights** section of the knowledge base sidebar. ## Analytics Open **Analytics** for a dashboard scoped to the current knowledge base. Data can be delayed by up to 15 minutes. * **Customer analytics**: total views, average views per published article, views over time, and a per-article breakdown. Views are split into **Human views** and **Non-human views**. * **Search insights**: searches with and without results, and the top queries in each group. Use **Top searches with no results** to find articles you still need to write. * **Internal metrics**: articles created and published, by creator and by status, over time. The main **Analytics** page also has a **Knowledge Base** tab, which includes **Helpfulness ratings & feedback** from article feedback. ### Human, bot, and AI crawler traffic Pylon classifies each article view as **Human**, **Known Bot** (such as search engine crawlers), **AI Crawler** (such as GPTBot, ClaudeBot, and PerplexityBot), or **Unknown**. **Non-human views** combine Known Bot and AI Crawler views. Article view charts can be filtered by traffic type, for example to see how much of your traffic comes from AI tools. ### Article activity Viewing analytics requires the analytics permission. Teammates without it see **Article activity** instead, which charts articles created and public articles updated. ## Performance The **Performance** page has two tabs: * **Feedback**: every feedback submission, with the article, score (from **Very unhelpful** to **Very helpful**), comment, and who submitted it. You can also open an article's feedback from its **⋯** menu. * **Search**: every search query on your knowledge base, with the number of results. Filter to **Zero results** to find gaps in your content. ### Feedback notifications To get notified when someone submits article feedback, click **Feedback Notifications** on the **Performance** page and turn on **Notify about knowledge base feedback submissions**. Choose any combination of: * **Slack channels to notify** * **Emails to notify** Notification settings apply to the current knowledge base. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.usepylon.com/pylon-docs/knowledge-base/analytics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.