# Analytics

> **Click** [**here**](https://discord.com/oauth2/authorize?client_id=1069423090225918082\&permissions=275146722545\&integration_type=0\&scope=applications.commands+bot\&redirect_uri=https%3A%2F%2Fcommunityone.io%2Fdashboard%2Fbot-auth-complete%2F%3Fsource%3Dgitbook\&response_type=code) **to introduce our bot to your server.**

Our analytics dashboard provides you with more than 100+ KPIs, helping you track moderators' performance and the overall health of the community, including how effective your marketing strategy is. If you are a community manager working in a large team, you may also find our weekly automatic report helpful. Our report gives a high-level summary of what is happening on the servers. 

## Get started on [Dashboard](https://communityone.io/dashboard)

Click on **Analytics** to start setting up your Dashboard

<figure><img src="/files/RO6JVtMZ9aCpJ5s9WVJt" alt=""><figcaption></figcaption></figure>

## Track channels

Give us a list of channels that you'd like us to keep track of. We will use your approved channels to:

* Measure analytics for your data insights
* Feed into our [AI CM](/communityone/use-ai-to-supercharge-your-community/introduction/ai-community-guru.md) for additional qualitative insights

{% hint style="info" %}
Kindly exclude internal team channels!
{% endhint %}

## Track moderators

You can add a list of moderators to track by giving us the role. You can add multiple roles, including admin. Note that we will only show up to 25 moderators' stats at once.&#x20;

{% hint style="info" %}
If you'd like to update the list of members for the specific roles, remove and add back the role for our internal system to trigger an update.
{% endhint %}

If you want our bot to track how moderators handle tickets, go to your ticket tool and add communityone as one of the roles/members that will get tagged whenever a ticket is opened.&#x20;

Here's a list of ticket bots that we support:

* Tickets
* Ticket King
* Ticket Tool
* Helper.gg
* Server Support
* Ticket Tools

If you want us to track another ticket bot, drop by our [discord](https://discord.gg/communityone) and leave a message.

For ticket-related analytics, ensure no external bots, such as WICK, can overwrite our permissions to see tickets. Unlike most of our analytics, we can not retroactively see past tickets simply because they are no longer on the server. As a result, you will only see data when new tickets have been generated. For testing, you can create a ticket and see if the "Ticket" category in the Moderation Workload chart is showing up. After your moderators answer any tickets created after our bots start tracking, you can track them on the Ticket Attended chart.

<figure><img src="/files/qyKtpfB1jttEuFMsrmWk" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/DWLZ6TWDBZVcSeYEeeXB" alt=""><figcaption></figcaption></figure>

## Track Topics

You can track the number of messages and communicators by topic. All you have to do is give us the issues and the associated keywords. We will count the number of messages that contain these keywords. You can add up to 10 keywords per topic.&#x20;

You can add 1 topic in our free plan, 2 topics if you are in freeplus, and an unlimited amount of topics for all of our premium tiers.&#x20;

<figure><img src="/files/XUICclEOVAxY3LQ7co0g" alt=""><figcaption></figcaption></figure>

You can find your data on the engagement tab of your analytics.&#x20;

<figure><img src="/files/hD531W1oWTxR6z7mioZ1" alt=""><figcaption></figcaption></figure>

## Track bot/spam accounts

Specify the role that a **human** would get after he/she is verified via your verification system. Everyone on Discord would get a base role of @everyone. After a user is verified (via whatever bot system that you use), you can specify a role (such as @verified) to differentiate the users from a bot.

This configuration allows us to discern between genuine human and bot accounts. Remember, you can designate multiple roles as indicators of verified humans, which is especially useful when utilizing Discord's welcome screen.

<figure><img src="/files/7jbr1z8Aiyqv7XW6JIFN" alt=""><figcaption><p>Our analytics on bot detection</p></figcaption></figure>

## Track engagement by roles

You can specify the roles that you want our analytics to track in a more detailed manner.  Currently, this is a premium feature.

<figure><img src="/files/ZgNxFjvtGzdi5HNslgIo" alt=""><figcaption></figcaption></figure>

Here's the list of analytics that we are providing by roles:

* Messages
* Members
* Words per Message
* Message per Member
* Heatmap on activities by days and hours

<figure><img src="/files/urKDFCGlZgR18UZaF76U" alt=""><figcaption></figcaption></figure>

## Email Notification

<figure><img src="/files/feHNNRyPnf35MwvLduqE" alt=""><figcaption></figcaption></figure>

We send out a daily and weekly report summarizing your discord data. If you and any of your team mate would like to receive a daily upate, just enter their emails here.&#x20;

## On-demand Update:

<figure><img src="/files/zRf2HLtLuMnQu2RL8aes" alt=""><figcaption></figcaption></figure>

This is a pro feature allowing you to:

* Get historical data of your Discord
* On-demand update: If you are actively doing marketing and would love to see your stats more frequent than once a day, you can use this to trigger an update.

## API Integration:

You can find detailed documentation for API here: <https://api.communityone.io/v1/documentation#tag/Analytics>

Please note that some analytics that depend on context may change depending on our reference window. For example, the number of new users who have ever chatted can change depending on the window we use.&#x20;

{% hint style="info" %}
Join [Discord](https://discord.gg/nVqt3z78Mw) for questions, comments, and a little gift <img src="https://fonts.gstatic.com/s/e/notoemoji/latest/1f381/512.gif" alt="🎁" data-size="line"> or back to [CommunityOne Home](https://communityone.io/)
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://communityone.gitbook.io/communityone/feature-deepdive/analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.