# How to understand the Broadcast UI Metrics

OverviewCommentShare feedback on the editorThis document explains the different metrics in the **Broadcast UI** and how they are calculated.CommentShare feedback on the editor​CommentShare feedback on the editorThis table outlines the different metrics in the Broadcast UI and how they are calculated.CommentShare feedback on the editor

| **Metric**                  | **Description**                                                                                                                              |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Total**                   | Sum of **Sent** and **Failed** messages.                                                                                                     |
| **Sent**                    | Messages triggered from LimeChat’s system.                                                                                                   |
| **Failed**                  | Messages that failed to send due to issues like an incorrect or non-existent number.                                                         |
| **Delivered**               | Messages successfully received by the user’s device. This may be lower than **Sent** due to factors like frequency capping or BSP errors.    |
| **Read**                    | Number of messages that were opened by users.                                                                                                |
| **Read Rate**               | Percentage of **Delivered** messages that were opened. Formula: `Read ÷ Delivered × 100`                                                     |
| **Reply Rate**              | Percentage of **Read** messages where users responded. Formula: `Replies ÷ Read × 100`                                                       |
| **Conversion Rate**         | Measures engagement, typically based on user replies or interactions.                                                                        |
| **Click-to-Response (CTR)** | Number of times users clicked a link within the message. Does not indicate if an order was placed or further interactions occurred.          |
| **Revenue**                 | Revenue generated from users clicking a link and placing an order. Only counted if the purchase occurs after interacting with the broadcast. |

CommentShare feedback on the editor​CommentShare feedback on the editor[<br>](https://app.gitbook.com/o/4Lfr62NemLcosNZYG4H3/s/bX4xjPD7aB6o9V5WDDF9/campaign/common-faqs/understanding-flow-reports-and-analytics-key-differences-and-troubleshooting)

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbX4xjPD7aB6o9V5WDDF9%2Fuploads%2F2JAxhAA9OAUPHh100Hk9%2FScreenshot%202025-02-25%20at%205.06.34%20PM.png?alt=media&#x26;token=cde9e0a5-a061-478c-a58f-a8f426941a2f" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://limechatai.gitbook.io/limechat-product-guide/client-shareable-docs/how-to-understand-the-broadcast-ui-metrics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.