> For the complete documentation index, see [llms.txt](https://tapminds.gitbook.io/tapmind-mediation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tapminds.gitbook.io/tapmind-mediation/reporting-analytics.md).

# Reporting & Analytics

## Section Overview

This section explains how TapMind captures events, processes data, and delivers reporting. It covers the event lifecycle, reporting architecture, and the role of key data infrastructure.

Use this section when you need to understand how performance and revenue data flows through the platform.

## Who Should Read This Section

* **Product Managers** evaluating reporting capabilities for clients
* **Project Managers** tracking reporting-related milestones
* **Client Stakeholders** who rely on revenue and performance data
* **Support Teams** investigating reporting delays or data discrepancies
* **Developers** working on event pipelines or data integrations

## Pages In This Section

| Page                                                                                       | What you will learn                                     |
| ------------------------------------------------------------------------------------------ | ------------------------------------------------------- |
| [Event Lifecycle](/tapmind-mediation/reporting-analytics/event-lifecycle.md)               | How events are generated, transmitted, and stored       |
| [Reporting Architecture](/tapmind-mediation/reporting-analytics/reporting-architecture.md) | How the reporting pipeline is structured end to end     |
| [Why RabbitMQ](/tapmind-mediation/reporting-analytics/why-rabbitmq.md)                     | Why TapMind uses a message queue for event processing   |
| [Why MongoDB](/tapmind-mediation/reporting-analytics/why-mongodb.md)                       | Why TapMind uses document storage for event data        |
| [Why PostgreSQL](/tapmind-mediation/reporting-analytics/why-postgresql.md)                 | Why TapMind uses relational storage for structured data |

## Suggested Reading Path

**New user**

[How Mobile Ads Work](/tapmind-mediation/getting-started/how-mobile-ads-work.md) → [Event Lifecycle](/tapmind-mediation/reporting-analytics/event-lifecycle.md) → [Reporting Architecture](/tapmind-mediation/reporting-analytics/reporting-architecture.md)

**Developer**

[Event Lifecycle](/tapmind-mediation/reporting-analytics/event-lifecycle.md) → [Reporting Architecture](/tapmind-mediation/reporting-analytics/reporting-architecture.md) → [Why RabbitMQ](/tapmind-mediation/reporting-analytics/why-rabbitmq.md)

**Operations**

[Reporting Architecture](/tapmind-mediation/reporting-analytics/reporting-architecture.md) → [Monitoring & Troubleshooting](/tapmind-mediation/operations/monitoring-troubleshooting.md) → [FAQ](/tapmind-mediation/reference/faq.md)