> ## Documentation Index
> Fetch the complete documentation index at: https://docs.growthxai.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How Each Number Is Counted
> The exact definition behind every figure in Reports, on the Dashboard, in the client portal, in Claude and in the API.
Every metric below is defined once, in the database. The Dashboard, the [Reports page](/reports/reports-overview), the [client portal](/agencies-and-clients/clients-and-client-portal), the [Claude connector](/integrations-api/mcp-connect-claude) and the [public API](/integrations-api/public-api) all read that one definition, so they cannot disagree.
In the app these definitions appear as tooltips on each figure. The API returns them from `GET /v1/metrics/definitions`.
## Time
| Term | Definition |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Day** | A calendar day in the **workspace timezone** ([Settings → Workspace](/getting-started/platform-overview/workspace-settings)). Ranges include both end dates. |
| **Previous period** | The same number of days immediately before the selected range. |
## Volume
| Metric | Definition |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Invites** | Connection requests LinkedIn accepted for delivery in the period. |
| **Accepted** | Invitations accepted in the period, whenever they were sent. Attributed to the step and variant that sent the invitation. |
| **Acceptance rate** | Accepted ÷ invites sent, both within the period. |
| **Touches** | Messages + InMails + emails + invitations that carried a note. This is the denominator of every reply rate. |
Because **accepted** counts acceptances in the period and **invites** counts sends in the period, acceptance rate can go above 100% in a short range — for example a quiet week in which invitations sent the week before were accepted. Widen the range for a stable figure.
## Replies
| Metric | Definition |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Replies** | Threads in which the lead answered an **automated step** for the first time in the period. One lead answering three times is one reply. |
| **Reply rate** | Replies ÷ touches. |
| **Interested** | Replies whose thread is currently classified *interested* — by the AI, or by your override. |
| **Positive reply rate** | Interested replies ÷ replies, leaving out-of-office auto-replies out of the denominator. |
| **Negative reply rate** | Not-interested replies ÷ replies, on the same denominator. |
A reply to a teammate's **manual** message from the Inbox is conversation, not a campaign reply. It is not counted in **replies** and does not affect reply rate. Only answers to automated steps count, which is what makes the number comparable between sequences.
Because interest is read live, correcting an intent in the Inbox changes the report for past days too. That is deliberate: the report should match what you believe about the thread.
## Outcomes
| Metric | Definition |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Meetings** | Leads that reached a **Meeting** stage, or booked through the [booking link](/sequences/creating-managing-sequences/booking-and-call-tasks), in the period. Counted once per lead. |
| **Won** | Leads that reached a **Won** stage in the period. Counted once per lead. |
| **Funnel** | Follows the leads **enrolled in the period** through every later stage, whenever that stage happened. |
Meeting and Won depend on your pipeline stages carrying the right meaning. Set that under **Leads → Manage → Stages**: each stage can be marked as new, contacted, connected, replied, interested, meeting, won or lost. New workspaces come with all eight already mapped.
## Cost
| Metric | Definition |
| ------------------ | -------------------------------------------------------------------------------------------- |
| **Sender cost** | Monthly cost × days in period ÷ 30, for every sender that was connected in the period. |
| **Cost per reply** | Sender cost ÷ replies. The same shape is used for cost per interested reply and per meeting. |
Set **Monthly cost** on each sender. Leave it empty and that sender contributes nothing to the cost figures.
## Sender metrics
| Metric | Definition |
| ----------------------- | ------------------------------------------------------------------------------- |
| **Headroom** | The share of the invitation cap a sender did **not** use over the last 30 days. |
| **LinkedIn limit hits** | Times LinkedIn itself refused further invitations. |
| **Network growth** | The increase in the sender's connection count. |
## Where a rate is empty
A rate with a denominator of zero is returned as **n/a**, never as 0%. "No invitations sent" and "no invitations accepted" are different facts, and the report keeps them apart.
## Related articles
* [The Reports Page](/reports/reports-overview)
* [Dashboard Overview](/getting-started/platform-overview/dashboard-overview)
* [Sender Insights](/senders/sender-insights)