> For the complete documentation index, see [llms.txt](https://guides.clickatell.com/release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.clickatell.com/release-notes/release-notes-archive/2023-release-notes/q2-2023/automated-messaging/new-analytics-settings.md).

# New Analytics Settings

Previously, tracking customer activity with a chatbot was not possible. Businesses had limited visibility into the way their customers engage with their brand, what their pain points are, or where they may be dropping off in the chatbot flow. This lack of information makes it difficult to optimize the chatbot experience for customers.&#x20;

We've added several enhancements to make this tracking easier for businesses. These enhancements are discussed in detail below.&#x20;

## Analytics Button

We've added an *Analytics* button to every node.&#x20;

<figure><img src="/files/wRAH5ebfDwgEU6WVSwSA" alt=""><figcaption></figcaption></figure>

This opens a dedicated space where you can attach a report label to the node and add the step to a collection of data markers.

<figure><img src="/files/hr3YxOKsuwrsXMeS8cU6" alt=""><figcaption></figcaption></figure>

You can also add a new collection from here, or navigate to the *Analytics Settings* page to manage your collections (see below).

<figure><img src="/files/MG4TTlKfU1CmSVgO1OUC" alt=""><figcaption></figcaption></figure>

## Analytics Settings

We've introduced a new page under *Configuration* where you can manage your data marker collections.&#x20;

You can add single or multiple data markers to any step (see above). This will be grouped into **data collections** that can then be tracked and included in your analytics report in the Clickatell Portal.

<figure><img src="/files/25jefOmyvQPDaJfn4rXW" alt=""><figcaption></figcaption></figure>

In the *Analytics Settings* section, you can:

1. Add new collections.
2. See a list of all the collections you've created.
3. Search and filter collections.
4. Remove, rename, and view usage of collections.
5. See if there are alerts and issues with your collections.

{% hint style="info" %}
For more information, see [this page](https://clickatell.gitbook.io/flow/reporting-and-analytics/analytics-settings).
{% endhint %}

<figure><img src="/files/N618pTXLPGRF6cnCx23o" alt=""><figcaption></figcaption></figure>

## Flow Feature Report

We've added a new [Flow Feature Report](https://clickatell.gitbook.io/flow/reporting-and-analytics/clickatell-portal-reports#flow-feature) to the Clickatell Portal.

<figure><img src="/files/Vo7P7WlQ4iBUe0IiqHyU" alt=""><figcaption></figcaption></figure>

The Flow Feature report provides an in-depth view of the flow features as set up in Chat Flow (Clickatell will help you set these up using your data collections). This report gives insight into your user journeys, which flows are most successful, and where the drop-off rate is big so that you can address the pain points with training or other interventions.

{% hint style="info" %}
Learn more about the [Flow Feature Report](https://clickatell.gitbook.io/flow/reporting-and-analytics/clickatell-portal-reports#flow-feature).
{% endhint %}

<figure><img src="/files/SA3Z59GnHkt8zDqtiTqx" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://guides.clickatell.com/release-notes/release-notes-archive/2023-release-notes/q2-2023/automated-messaging/new-analytics-settings.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.
