> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/reports-and-analytics/reports.md). # Reports Use prebuilt Netmera reports to monitor messaging performance, user growth, app health, event volume and KPIs without building a custom analysis. Reports are prebuilt dashboards for monitoring messaging performance, user growth, platform health, and operational activity. Use this section when you want a ready-made answer quickly, without building a custom analysis from scratch. In general, **Reports** gives you structured dashboards with stable metrics. **Analytics** is better when you want ad-hoc exploration, custom breakdowns, or more investigative work. {% hint style="info" %} Most reports follow the same workflow. Start with the date range, add filters if needed, review the main trend or table, and export when you need deeper analysis. {% endhint %}

Illustration of a report dashboard with line charts and the Netmera mascot

### How to work with reports {% stepper %} {% step %} #### Pick the report that matches the question Start from the sections below. Each report is designed to answer a different type of operational or performance question. {% endstep %} {% step %} #### Set the time range first Use a shorter range when you are debugging a recent issue. Use a longer range when you want to understand trends or compare periods. {% endstep %} {% step %} #### Filter out noise Use labels, channels, audience filters, or report-specific options where available. This helps the report answer one focused question instead of several broad ones at once. {% endstep %} {% step %} #### Export when you need to go further Exports are useful when you want to share the result, compare it outside the panel, or join it with another source. {% endstep %} {% endstepper %} ### Messaging performance Use these reports when the question is about campaign delivery, engagement, conversion, or revenue across one or more channels.

What you can review	Open
Cross-channel campaign overview, including volume, open rate, conversion, and revenue	Campaign reports
Push-specific delivery, clicks, conversions, and revenue	Push reports
Email delivery, opens, clicks, bounces, unsubscribes, and bounce reasons	Email reports
SMS dispatch, provider-confirmed delivery, and failure detail	SMS reports
WhatsApp send, delivery, and read performance	WhatsApp reports
Automated, transactional, and geofence campaign performance	Automated, transactional & geofence reports

### Users, growth, and app health Use these reports when you need a broader platform view, such as user growth, installs, version adoption, or reachability.

What you can review	Open
Total users, devices, sessions, opt-ins, and revenue over time	Total users report
Installs, reinstalls, and uninstalls	Installs report
Which app versions are active across users and devices	Application version
Who can be contacted on each messaging channel	Channel reachability
Which Android apps coexist with yours on user devices	App tracking

### Event volume and operational checks Use these reports when you need fast event counts rather than a full behavioral analysis.

What you can review	Open
Daily and hourly event volume	Event reports
Deeper event investigation with dimensions and breakdowns	Event insight

### KPIs and governance Use these reports when the goal is broader management, monthly tracking, exports, or auditability.

What you can manage	Open
Monthly KPI monitoring	KPIs monthly
User actions and configuration changes in the panel	Audit logs
Scheduled and manual data exports	Scheduled data export
Metric definitions used across the report set	Broken link

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://user.netmera.com/netmera-user-guide/reports-and-analytics/reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.