> ## Documentation Index
> Fetch the complete documentation index at: https://docs.headlesslabs.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Server Analytics

> Server Analytics presents aggregated metrics Headless observed for the server. It requires Manage Server and cannot reconstruct activity from before collection began.

## Observed metrics

`.analytics` (aliases `.serveranalytics` and `.sa`) and `/analytics` show an image covering the last seven days. Runtime aggregates messages, joins/leaves, voice events, moderation, message deletions, and recorded security, counting, and giveaway events. Counters begin when Headless observes events; earlier activity cannot be reconstructed.

### `.analytics`

```headless-command Syntax theme={null}
.analytics
```

```headless-command Example theme={null}
.analytics
```

Also works: `.serveranalytics` · `.sa`

### `/analytics`

```headless-command Syntax theme={null}
/analytics
```

```headless-command Example theme={null}
/analytics
```

The image and controls generated by Headless are in English; server and channel names retain their Discord-configured text.

## Retention and refresh

Collection retains up to 45 days of daily buckets and 96 hours of hourly buckets; the command view summarizes seven days. The Refresh button regenerates the image from stored counters. The command requires Manage Server, and the slash response is ephemeral.

> [!NOTE]
>
> Missing records from before collection began do not mean there was no activity. The command summarizes seven days even though buckets are retained longer; retention does not provide arbitrary date ranges or metrics Headless did not record.

## Per-server data

Counters are queried and stored per server. Analytics is not a message archive and does not reveal the contents of deleted messages; it reports counts of observed events.

## Steps

**1. Check authorization**

You need Manage Server to run the command.

**2. Open the panel**

Use the prefix command or slash command and review the server card.

**3. Interpret the time window**

Distinguish the seven-day summary from maximum bucket retention; do not attribute unobserved data to the bot.

## Metrics and privacy

> **Server Analytics**
>
> A visual panel of server activity observed by the bot. The command provides a seven-day summary and can refresh the image from persisted counters.
>
> <ul>
>   <li>Messages, growth (joins/leaves), and voice activity</li>
>   <li>Moderation and message deletions</li>
>   <li>Recorded Honeyspot, Vanity, Counting, and Giveaway events</li>
> </ul>

> **[Privacy](/docs/en/permissions.md)**
>
> The public view is limited to aggregate telemetry; user timelines and sensitive details remain behind authentication and per-server authorization.
>
> <ul>
>   <li>Seven-day public summary, without individual timelines</li>
>   <li>Dashboard session and module policy gate private data</li>
>   <li>Analytics requires Manage Server in Discord</li>
> </ul>

## Related pages

* [User History](/docs/en/community/user-history.md)
* [Logging](/docs/en/server/logging.md)
* [Permissions](/docs/en/permissions.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.