> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/email-api-smtp/analytics.md). # Analytics & Reports Learn what statistics Mailtrap provides: Stats dashboard, Email logs, Email categories, Mailbox providers.


Stats Dashboard	Check the analytics for all the emails you send.	Stats Dashboard
Email Logs	Include the status of each message, its preview, events history, HTML source, and statistics.	Email Logs
Email Categories	Performance of various types of emails, such as welcome emails, billing emails, confirmation emails, etc.	Email Categories
Mailbox Providers	Check the deliverability stats using filters such as Domains, Mailbox Providers, and Categories.	Mailbox Providers
Statuses and Events	The latest delivery status of an email, each status bears a distinct color, and an email can only have one status at a time.	Statuses and Events

--- # 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://docs.mailtrap.io/email-api-smtp/analytics.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.