> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/analytics/overview.md).

# Overview

Batch allows you to track the performance of your orchestrations across different channels with two comprehensive views:

* **Performance Analytics:** An analytics tab offering a macro-level view to monitor the evolution of key metrics over time.
* **Orchestration Analytics:** A detailed, orchestration-specific view providing additional insights, accessible within each orchestration.

Analytics data is updated in real time and assigned to the date the message was originally sent. For instance, if a message is sent on January 1st and recipients interact with it (e.g., open or click) on January 2nd or 3rd, all such interactions are recorded under January 1st.

For Trigger and Recurring Automations, Profiles can receive messages repeatedly if they re-enter a Trigger Automation or are targeted again by a Recurring Automation. Analytics will reflect these multiple message sendings by displaying cumulative metrics, including the total number of sent messages, opens, clicks, and other engagement data.

{% hint style="warning" %}
Deleting an orchestration, a step in a trigger automation, or removing a language version of a campaign does not erase related analytics. Metrics for messages sent in these cases remain available.
{% endhint %}

{% hint style="info" %}
Note that you can access raw analytics data (e.g., when a profile opened an email) via the Export Profile Events API.
{% endhint %}


---

# 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://doc.batch.com/getting-started/features/customer-engagement-platform/analytics/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.