Pulse documentation
Read Discord’s current member count and aggregate joins and departures observed while enabled.
On this page
A ready workspace for Pulse.
Sign in as the server owner or with Manage Server permission. Open Pulse, choose the correct server inside the app, and check its connection. Each app needs its own Discord installation consent.
New to Guildryx? Follow Getting started first
Configure the required channels, roles, and access before enabling and saving. Saving applies to this app in the selected server.
Opt in to community counts
- Install Pulse and open its workspace. Select Collect aggregate join and departure counts.
- Enable Pulse and save. Collection is opt-in and specific to this server.
- A working member-event connection is required for join and departure counts. If the service reports unavailable member events, contact Guildryx support; a server manager does not need a bot token or Developer Portal access.
Read the community summary
- Use /pulse-community inside the server to see Discord’s current member count and the observed event summary.
- Join and departure numbers cover events Pulse actually observed while collection was enabled. They do not represent every historic member change.
- Daily aggregates are retained for up to 30 days. Current member count and observed changes can differ because older history and offline gaps are not reconstructed.
Understand collection boundaries
- Pulse does not collect message contents or record voice audio. Message and voice analytics, growth charts, cohorts and exports are unavailable.
- Pause Pulse and save when you want to stop future event collection.
- Use the service-status page to check a wider outage. Do not treat a reconnecting period as a zero-change day.
Commands & controls
Use these controls for the current release inside the relevant Discord server. Discord’s command picker supplies required options; app-specific permissions still apply.
/pulse-communitySee the current member count and observed member events.
What this app needs and keeps
Discord access
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.
Stored information
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.
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.
Troubleshooting
Join counts start later than my server history
Pulse only reports observed events after opt-in. It cannot reconstruct changes from before installation or during offline periods.
Member events are unavailable
Check the bot connection and service status, then contact Guildryx support. Only the bot operator controls the service’s privileged intent configuration.
Member count does not match the observed difference
Current count comes from Discord; the join/leave summary covers only the observed window. Older membership and unobserved changes are not included.
Still stuck? Check Service Status, then contact private support with the app, server ID, and the error. Never send a password, bot token, or backup code.