Monitoring
Community Swarm’s monitoring system tracks activity across your connected Discord servers and Telegram groups, providing real-time insights into community health and engagement.
What the Monitoring Bot Tracks
The official Community Swarm bot passively observes your communities and collects the following data:
- Messages — Content, timestamps, authors, and channels for all messages in monitored channels
- Member activity — Who is active, message frequency, and participation patterns
- Channel activity — Which channels drive the most conversation
- Timestamps — When messages are sent, enabling peak hour and trend analysis
The monitoring bot is read-only. It does not send messages, react, or modify any server settings. It only observes and collects data.
Monitoring Methods
Community Swarm supports two monitoring approaches depending on the platform:
Bot API (Discord and Telegram)
The standard monitoring method uses the official Community Swarm bot. The bot joins your server or group and reads messages in configured channels. This is the simplest setup and works for most use cases.
User API (Telegram Only)
For Telegram groups, you can use one of your existing profiles (userbots) as the monitoring source instead of the official bot. This avoids adding an extra bot to your group and can be less visible to group members.
Select the monitoring method when adding a server. You can switch methods later from the server settings.
Bot Management
The Bot Management dialog (accessible from the Servers page) lets you view and manage monitoring bots across platforms.
For each platform, you can see:
- Current bots — Official and custom bots with their status
- Bot status — Active, Offline, Banned, or Maintenance
Custom Bots
You can add custom Telegram bots if you prefer to use your own bot for monitoring instead of the official one:
- Open Bot Management from the Servers page.
- Click Add Bot.
- Provide the bot token, display name, and optionally a proxy.
- Save the bot.
Custom bots appear in the monitoring bot selector when adding or editing servers.
Analytics Integration
Data collected by the monitoring bot feeds directly into the Analytics dashboard and Reports system. The monitoring bot collects raw data; analytics processing happens in the background.
Key analytics derived from monitoring data:
- Message volume — Daily, weekly, and monthly message counts
- Sentiment analysis — AI-analyzed sentiment scores for messages
- Peak hours — When your community is most active (hourly heatmap)
- Top topics — Most discussed subjects in your community
- Channel breakdown — Message distribution across channels
Profile Assignments
You can assign userbot profiles to engage in monitored servers. From the server card, click Manage Profiles to open the assignment dialog.
The dialog shows available profiles for the server’s platform with their assignment status:
| Status | Meaning |
|---|---|
| Pending | Assignment created, profile waiting to join |
| Joining | Profile actively attempting to join |
| Joined | Profile successfully joined the server |
| Failed | Join attempt failed (error details shown) |
| Already In | Profile was already a member of the server |
| Skipped | Join was skipped (reason provided) |
You can retry failed assignments or remove profiles that are no longer needed. If a Telegram profile fails to join, see the Join Troubleshooting guide for common errors and solutions.
Assigning too many profiles to a single server increases detection risk. Distribute profiles across servers and stagger their schedules for more natural behavior.
Server Verification
When you first add a server, it enters a Pending Setup state until the monitoring bot’s presence is verified. The dashboard polls for verification automatically.
If verification fails:
- Ensure the bot has been invited to the server with the correct permissions
- For Telegram, verify the bot has admin access
- Try clicking Verify again from the server card
Data Retention
- Message data and analytics are retained for the duration of your active subscription.
- Data can be exported through the Reports system.
- Analytics data begins populating after you connect the monitoring bot. Historical data from before the connection is not imported.