> For the complete documentation index, see [llms.txt](https://help.1msg.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.1msg.io/docs/api-1msg/template-analytics.md).

# Template Analytics

Template analytics help you understand how your message templates are performing. You can use them to answer questions like:

* How many times was a template **sent**, **delivered**, or **read**?
* If your template includes URL buttons or Quick Reply buttons, how many times were they **clicked**?

For businesses using the Marketing Messages API, you can also track off-site conversion metrics (e.g., app activations, checkouts, purchases) tied to templates.

These insights let you evaluate template effectiveness (open-rate, click-rate), compare templates, optimize your content, calls to action, and more accurately tie WhatsApp template usage to business outcomes.

## Core Capabilities

Using the 1MSG Analytics API, you can automate monitoring of the following metrics:

* **Sent / Delivered / Read:** Standard message funnel.
* **Clicked:** Array of button‐click metrics (only available for templates in category MARKETING or UTILITY), including total and unique clicks.
* **Cost:** Cost metrics, e.g., total amount spent, cost per delivered, cost per URL button click (for campaigns/tracked templates).

## Important Limits and Nuances

Before implementing or using analytics, pay attention to these technical details:

1. Geographic restrictions: Click analytics (click tracking) is not supported for WABAs registered in the EU, UK, and Japan due to data protection laws (GDPR, etc.).
2. Specifics in Russia and China: In regions with restricted access to Meta services, users need a VPN for click analytics to work correctly. If a recipient clicks a button without VPN, the link may not open.
   * Recommendation: If your audience is in Russia, disable link tracking in the template settings (`cta_url_link_tracking_opted_out: true`).
3. API technical limits:
   * Granularity: Only daily stats are available (`DAILY`). No hourly analytics.
   * Request limit: A single API request can return data for a maximum of 10 template IDs.
   * Time zones: UTC is used by default. You can switch to the account time zone with `use_waba_timezone`.
4. Enabling template analytics: To activate analytics, call `/settings/templateAnalytics` with `enable = true`.\
   After that, permission to retrieve analytics data is requested and applied at the Meta (WABA) level. Once enabled, it cannot be disabled at the WABA level. In 1msg, “disabling” is implemented as an API-level restriction: data stops being displayed and used in the product.

## Example Use Cases

* A/B content testing: Compare two offer versions by Read Rate and Clicked; keep the one with more clicks.
* Database quality control: If the gap between Sent and Delivered is more than 15%, your database has many inactive numbers. This is a signal to clean the list to avoid harming your Meta number reputation.

## Documentation and Resources

* [1MSG.io Documentation — Template Analytics](https://docs.1msg.io/#tag/Template-Analytics): Endpoints for getting statistics and managing settings.

> Note: Analytics data is updated with a delay ranging from a few minutes to several hours (depending on delays on Meta’s side).


---

# 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://help.1msg.io/docs/api-1msg/template-analytics.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.