The current Discord member count
Use /pulse-community to see the server’s current member count from Discord. This is a present count, not a reconstructed timeline of every person who joined.
Understand observed changes in your community. Pulse combines Discord’s current member count with aggregate joins and departures collected while you enable tracking.
For owners who want to understand whether new members stay, which community activities matter, and where to focus their effort.
Honest collection boundaries help you distinguish a current server count from observed change, rather than treating missing data as a real zero.
These are the features you can configure and use in the current release. Installation and the required Discord access are still needed.
Use /pulse-community to see the server’s current member count from Discord. This is a present count, not a reconstructed timeline of every person who joined.
Collect aggregate member events while Pulse is enabled and the required Discord member events are available. Counts reflect what the bot observed during that collection period.
Owners choose whether Pulse runs. The workspace explains missing member-event access, and Pulse does not fabricate analytics for periods before activation or while collection was unavailable.
Pulse reports member counts and observed join/departure aggregates for up to 30 days. Join/departure collection requires the bot operator to enable Discord Server Members Intent; while unavailable, the dashboard blocks collection and Status reports the app needs attention. It does not reconstruct historical or offline activity, read conversations or provide retention cohorts.
Here is how the current feature fits into a real community workflow.
Read the Pulse guideThey review member-event access and enable Pulse for their server.
Pulse begins recording aggregate joins and departures it observes from that point onward.
The owner uses /pulse-community to compare the present member count with the observed events.
Good tools should explain what they need, what they store, and what they leave under your control.
Member-event analytics depend on the Discord access and intent granted to Pulse. Missing approval is reported; it must not be bypassed or silently replaced with invented data.
Current Pulse keeps daily aggregates for 30 days and temporary deduplication hashes. It does not reconstruct earlier membership, copy message contents, or record voice conversations.
Each app has its own Discord installation consent and server-specific settings. Available features stay free. Installing an app does not authorize every module; enable only the features you want and save deliberately.
Explore trust & safetyInstall Pulse and choose its server workspace.
If required, ask the operator to verify Pulse’s Server Members Intent and member-event availability.
Enable and save collection deliberately, then check the current report and its observation boundaries.
The important details, without hidden assumptions about what is ready.
No. It starts from the events it observes while enabled. Earlier history is not reconstructed.
No. The member count is a present Discord count; observed joins and departures describe events collected during a specific period.
No. Pulse provides member counts and observed joins/departures. Growth charts and retention cohorts are unavailable.
Choose only the apps your community needs. Related apps have separate setup and permissions; an automatic connection between them is not enabled by installing both.
Choose the features your community needs, follow the setup guide and save your server’s settings.
