> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-exchange/reporting/dynamic-reporting.md).

# Dynamic Reporting

Digital Turbine handles over 15 billion events a day, producing some 3000 TB (approximately a trillion bytes) of data each month. Every event contains more than 80 attributes describing the advertisement request and response flow. Digital Turbine's Dynamic Reports module provides DT publishers with the ability to create and view reports revealing close to real-time data ingestion, flexible data exploration, and fast data aggregation.

<div data-with-frame="true"><figure><img src="https://1641760969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8KSLu5HNiyDWpvGRZh7B%2Fuploads%2Fgit-blob-9d651a44a57864ea7cc3506975f143bf81dde86e%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure></div>

## The Report

The [Auctions Report](/dt-console/reports/auctions.md) is a dynamic report that allows you to get a deeper look into the auction landscape and relies on specific data and dimensions.

***


---

# 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.digitalturbine.com/dt-exchange/reporting/dynamic-reporting.md?ask=<question>&goal=<user_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.