> ## Documentation Index
> Fetch the complete documentation index at: https://agencykey.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Metrics Reference
> Metrics in the Employee Analytics views
## Activity metrics
These metrics belong to the Employee Analytics report and follow its attribution and access rules.
| Metric | Description |
| ---------------- | --------------------------------------------------- |
| **Messages** | Total messages sent |
| **Fans Reached** | The number of different fans messaged in the period |
| **Scripts** | Unique scripts used |
| **Free Media** | Free media files sent |
## PPV metrics
| Metric | Description |
| ----------------- | --------------------------------------------------------- |
| **PPV Sent** | PPV messages sent |
| **PPV Sold** | PPV purchased |
| **PPV Open %** | Percentage purchased from sent (Sold / Sent) |
| **Avg. Sold PPV** | Average price of sold PPV |
| **PPV:Free** | PPV per free media. Higher = more aggressive sales |
| **PPV:Msg** | PPV per message. 0.10 = roughly every 10th message is PPV |
| **PPV \$** | Revenue from PPV in USD |
## Tips metrics
| Metric | Description |
| ----------- | ----------------------- |
| **Tips** | Number of tips received |
| **Tips \$** | Total tips in USD |
## Revenue metrics
| Metric | Description |
| --------------- | ----------------------------------------------------- |
| **Total Sales** | Total sales count (PPV + Tips) |
| **Total \$** | Total revenue in USD |
| **Rev/Msg** | Revenue per message (Total \$ / Messages) |
| **Rev/Fan** | Revenue per fan reached. Higher = better monetization |
| **% of Sales** | Share of total team/agency sales |
## After commission
Both reports — **By Employees** and **By Creators** — have an **After commission** switch next to **Trends**, above the table.
Turn it on and every money figure is shown net of the OnlyFans 20% cut, so the numbers match what actually lands in the payout:
* Totals and averages
* Per-fan and per-message revenue (**Rev/Fan**, **Rev/Msg**)
* The rows you see when you expand a model or an employee
* Anything you export
The switch flips instantly with no reload, keeps your expanded rows open, and is off by default — you see raw amounts until you turn it on.
Subscriptions are not included in the After commission view — it covers messaging sales only (PPV and tips).
Export while **After commission** is on and the money columns in your file come out net too, matching exactly what's on screen.
## Overlap between operators
On the **By Creators** report, when you expand a model into its per-operator rows, a small info hint sits by the **Fans Reached** cell. One fan can be messaged by several operators, so the per-operator rows can add up to more than the model's own total. This is expected — it is not double-counting in the model's figure.
## Response time
Available in the **By Employees** view. The **Response time** column shows how quickly each employee answers fans.
| Metric | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Response time** | Each employee's usual reply time — the middle of all their replies, so half are faster and half are slower. A faster value means fans wait less. |
The **Total** and **Average** rows show a dash for this column, because a usual reply time can't be added up across people. An employee with no replies in the selected period also shows a dash.
Click a **Response time** value to open a breakdown for that employee. Expand a row and click a single model to see only that model.
### Status at a glance
The breakdown opens with a colored word badge next to a plain sentence like "Usually Anna replies in 45s", so you read the verdict first.
| Status | Meaning |
| ------------- | --------------------------- |
| **Fast** | Replies very quickly |
| **OK** | Normal reply speed |
| **Slow** | Replies take a while |
| **Very slow** | Replies take over 5 minutes |
### Breakdown cards
| Card | What it shows |
| ----------------------- | ----------------------------------------- |
| **Usual reply** | The middle reply time — half are faster |
| **On average** | The average, including rare long ones |
| **9 out of 10 replies** | Most replies are faster than this |
| **Long replies** | Share of replies that took over 5 minutes |
| **Total replies** | How many replies the result is based on |
### Speed distribution
A single bar split by share of replies across five speed ranges:
| Range | |
| -------------- | --------------- |
| **under 30s** | Fastest replies |
| **30–60s** | |
| **1–2 min** | |
| **2–5 min** | |
| **over 5 min** | Slowest replies |
A line above the bar reads, for example, "80% of replies are faster than 2 minutes". A very small share shows as "\<1%" instead of a misleading "0%".
### Reply speed by hour
A 24-hour grid colored by how fast the employee answers at each hour. A strip below shows how many replies happened each hour, so you can see when they were busiest. A note calls out the fastest and slowest hours when there's a real difference.
Hours with fewer than 5 replies are marked as low data and don't affect the fastest/slowest note.
### By model
When an employee worked with more than one model, a table compares their usual reply time per model. A model where they're slow is flagged in coral. The table shows up to 50 models by messages sent.
Pick any date range up to 90 days in the table filters — the breakdown always follows the period and model filters you set on the table.
## Trend indicators
Arrows next to metrics show change compared to the previous period:
* ↑ Green — growth
* ↓ Red — decline
## Why employee and creator totals can differ
Employee metrics include only work and sales attributed to a CRM employee. Creator-originated, automated, system, or otherwise unattributed events are excluded from employee rows. A fan can also appear under more than one employee in an expanded breakdown, while the creator-level unique count remains deduplicated.
Sales attribution follows the active [Sales Settings](../sales-settings/index) version for the event time. Changing those rules can change which future sales appear under employees; it does not make Employee Analytics and Creator Analytics interchangeable.