> For the complete documentation index, see [llms.txt](https://metacrm.gitbook.io/metacrm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metacrm.gitbook.io/metacrm/products/community/community-analysis.md).

# Community Analysis

The **Community Analysis** feature provides a unified dashboard for tracking, analyzing, and comparing your Telegram and Discord communities. Designed specifically for community managers, it offers insights into member growth, engagement, retention, and trending topics, all within a single, easy-to-navigate interface.

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

#### Key Features

1. **Core Metrics Integration**\
   Track essential metrics across both Telegram and Discord to monitor and compare community health:

   * **Member Growth**: View the total number of members and their growth rate over time.
   * **New Member Count**: See how many new members joined during a specific time period.
   * **Retention Rate**: Measure the percentage of new members who remain active after joining.
   * **Engagement Activity**: Analyze participation levels with metrics like:
     * **Active Members**: Members contributing through messages or reactions.
     * **Average Interaction Rate**: Interactions per member, including comments, messages, and reactions.

   Metrics can be filtered by time intervals (daily, weekly, monthly) for a unified comparison of Telegram and Discord data.
2. **Community Hot Keyword Tracking**\
   Understand trending topics within your communities:
   * **Keyword Analysis**: Identify frequently mentioned keywords in user messages on Telegram and Discord.
   * **Hot Topic Cloud Visualization**: Visualize trending keywords in a cloud format, with keyword size reflecting frequency.
     * Clickable keywords reveal detailed insights, such as example messages containing the keyword.
   * **Time-Based Insights**: Filter by time period (daily, weekly, monthly) to track changes in community interests over time.
3. **Unified Data Presentation**\
   A single dashboard consolidates key metrics across both platforms:
   * **Member Growth Trend**: Line chart showing membership growth over time.
   * **Engagement Trend**: Comparison chart illustrating engagement levels across Telegram and Discord.
   * **Retention Analysis**: Visualize member retention trends for both platforms side-by-side.
   * **Hot Keywords Panel**: Highlight the top 10 trending keywords for easy access.
4. **Interactive Charts and Graphs**\
   Visualize metrics with clear, interactive charts:
   * **Member Growth Comparison**: Line graphs comparing growth rates between Telegram and Discord.
   * **Engagement Metrics**: Bar charts showing active members and interaction rates for each platform.
   * **Keyword Trends**: Line graphs or bar charts tracking specific keyword trends over time.
5. **Cross-Platform Comparison**\
   A side-by-side summary view simplifies platform comparison:
   * **Growth Rates**: Compare member growth for Telegram and Discord.
   * **Engagement Levels**: Assess average interactions per user across platforms.
   * **Retention Rates**: Understand retention patterns over specified periods.


---

# 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 dynamically by asking a question.

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

```
GET https://metacrm.gitbook.io/metacrm/products/community/community-analysis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.