> For the complete documentation index, see [llms.txt](https://limechatai.gitbook.io/limechat-product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limechatai.gitbook.io/limechat-product-guide/helpdesk/analytics/sales-analytics/sales-overview.md).

# Sales Overview

***

## Introduction

The **Revenue Analytics Section** in the Analytics page provides insights into the financial impact of LimeChat’s bot and campaign interactions. It includes key revenue metrics, graphical representations, and detailed breakdowns to help businesses track and optimize their revenue generation efforts.

***

## Metrics

1. **Total Bot Revenue**
   * The total revenue generated directly through orders placed via the bot.
   * **Use Case**: Tracks the bot’s contribution to overall sales and evaluates its effectiveness in converting customer interactions into purchases.
2. **Total Outbound Revenue**
   * The total revenue generated directly through orders placed via outbound campaigns.
   * **Use Case**: Measures the financial impact of campaign-driven interactions.
3. **Total Influenced Revenue**
   * The revenue generated from orders placed by users within 7 days following an interaction with LimeChat. This excludes orders directly placed through the bot or campaigns.
   * **Use Case**: Highlights the broader impact of LimeChat interactions on customer purchasing behavior.

***

## Graph: Influenced Sales

* Displays a graphical representation of the number of sales influenced by LimeChat interactions over the selected timeframe.
* **Key Insights**:
  * Identifies trends in influenced sales.
  * Helps track the effectiveness of bot and campaign interactions in driving customer purchases.

<figure><img src="/files/cqlyQVZCpIhcQufnwXLy" alt="" width="563"><figcaption></figcaption></figure>

***

## Graph: Influenced Revenue Breakdown

* Shows a detailed breakdown of influenced revenue by categories such as product types, customer segments, or interaction channels.
* **Key Insights**:
  * Provides a granular view of the sources contributing to influenced revenue.
  * Enables businesses to optimize strategies for high-performing categories or segments.

<figure><img src="/files/bBbRnHqOpsTr11k9lIp6" alt="" width="563"><figcaption></figcaption></figure>

***

## Usage Tips

* Use **Total Bot Revenue** and **Total Outbound Revenue** to evaluate the direct impact of bot and campaign efforts on sales.
* Leverage **Total Influenced Revenue** to understand the extended financial benefits of LimeChat interactions.
* Monitor the **Influenced Sales** graph to identify trends and improve strategies for customer engagement.
* Analyze the **Influenced Revenue Breakdown** to uncover high-performing areas and optimize marketing efforts accordingly.

This **Revenue Analytics Section** provides actionable insights into how LimeChat interactions contribute to business revenue, empowering data-driven decision-making to maximize financial outcomes.

***

## FAQ'S

<details>

<summary>How is Total Bot Revenue calculated?</summary>

Total Bot Revenue includes all orders placed directly through LimeChat’s bot. If a user completes a purchase within the bot interface, the order value is added to this metric.

</details>

<details>

<summary>What qualifies as Total Outbound Revenue?</summary>

Total Outbound Revenue consists of orders placed as a direct result of outbound campaigns, such as WhatsApp or SMS marketing. If a user clicks on a campaign message and completes a purchase, the order is counted.

</details>

<details>

<summary>How does the Influenced Revenue Breakdown help in optimization?</summary>

This breakdown categorizes influenced revenue by product types, customer segments, or interaction channels, allowing businesses to identify top-performing areas and refine their sales strategies accordingly

</details>

<details>

<summary>What factors could cause a drop in Total Bot Revenue?</summary>

Possible reasons include reduced customer engagement with the bot, ineffective bot responses, pricing changes, or external factors like seasonal demand fluctuations. Reviewing bot flows and analyzing user drop-off points can help identify the issue.

</details>

<details>

<summary>Can I compare bot performance across different customer segments?</summary>

Yes, the Influenced Revenue Breakdown allows segmentation analysis, helping businesses understand which customer groups respond best to bot and campaign interactions.

</details>

<details>

<summary>How do I use this data to improve marketing strategies?</summary>

By analyzing influenced revenue trends and high-performing product categories, businesses can adjust messaging, refine bot scripts, and allocate marketing budgets to the most effective channels.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://limechatai.gitbook.io/limechat-product-guide/helpdesk/analytics/sales-analytics/sales-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.