> For the complete documentation index, see [llms.txt](https://docs.notyfire.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notyfire.io/administration/analytics.md). # Analytics The Analytics view shows how Notyfire is used across your organization. It helps you track content activity and adoption in one place. It is available only to administrators and has two tabs: **Overview** and **Adoption**. ### Overview The Overview tab shows a simple summary of published content. It includes the number of items created in each module, such as **Announcements** and **Development**. This helps you see which areas are actively used. Use this tab to: * Check overall activity in Notyfire. * See how many items are published per module. * Compare Announcements vs Development usage. * Spot areas with low activity. * Track changes during rollout. #### Announcements Shows internal communication activity, such as information updates, planned changes, and incidents. #### Development Shows development-related communication and helps track delivery activity across teams. ### Adoption The Adoption tab shows how well Notyfire is being used in practice. It focuses on three key metrics: * Active users * Active subscriptions * Notifications sent Together, they show whether users are logging in, following content, and receiving updates. #### Active users Shows how many users have recently used Notyfire. This helps you check if people are actually adopting the tool after onboarding. Low usage may indicate missing training, awareness, or relevant content. #### Active subscriptions Shows how many has active subscriptions. Subscriptions indicate that users are selecting what they want to follow. Higher numbers usually mean better engagement and understanding of the tool. #### Notifications sent Shows how many users received notifications. This helps you understand communication volume. It should always be reviewed together with user and subscription data to understand real adoption. #### Using Adoption data Use this dashboard during rollout to track progress over time. Review it after: * Onboarding new teams * Enabling modules * Training sessions * Communication campaigns * Changes in subscription setup Healthy adoption usually shows steady growth in all three metrics. If adoption is low, check: * User access and onboarding * Content activity * Subscription setup and filters * Internal communication about Notyfire *** ### Recommended approach Check Analytics regularly, not just once. Combine metrics with user feedback to understand both **what is happening** and **why**. This helps you: * Improve onboarding * Increase adoption * Support teams that need help * Plan rollout steps * Make Notyfire a standard communication tool --- # 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.notyfire.io/administration/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.