> 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-growth/reporting-api/reporting-api-metrics-and-dimensions.md).

# Reporting API Metrics and Dimensions

**Metrics** define what type of data you want to include in your report. 

**Dimensions** allow you to filter the data set based on specific values. 

{% hint style="info" %}
Names of metrics and dimensions are case-sensitive.
{% endhint %}

## Metrics

Metrics are the data types that you want to include in your report. You must include at least one of the following metrics in your report request.

| METRIC NAME   | DESCRIPTION                                                                               | VALUE TYPE | EXAMPLE VALUE |
| ------------- | ----------------------------------------------------------------------------------------- | ---------- | ------------- |
| `Clicks`      | Count of clicks served as reported by DT                                                  | Integer    | `4200`        |
| `Installs`    | Count of installs as reported by the MMP                                                  | Integer    | `373`         |
| `Impressions` | Count of impressions served as reported by DT                                             | Integer    | `219147`      |
| `Spend`       | Gross Advertiser spend with DT in USD                                                     | Double     | `274.26`      |
| `Preloads`    | Count of preloads successfully loaded (opened and unopened) on a device as reported by DT | Integer    | `250`         |

## Dimensions

You can specify filter data based on any of the following supported dimensions. The generated report only contains data defined by the filter value(s) you specify in your report request. For example, if you request the `Country` dimension and specify `US` and `CA`, the generated report includes the specified metrics related only to the United States and Canada.

The following table describes the supported dimensions and how to specify values for each dimension in your JSON report request:

| DIMENSION NAME           | DESCRIPTION                                                      | VALUE TYPE | EXAMPLE VALUE                          |
| ------------------------ | ---------------------------------------------------------------- | ---------- | -------------------------------------- |
| `Ad Set`                 | The name of the campaign as labeled in the channel.              | string     | `My Fun Campaign` / `Programmatic`     |
| `Ad Set ID`              | Unique identifier for the campaign within the channel.           | string     | `12345` / `Programmatic`               |
| `App Name`               | The advertised app name.                                         | string     | `MyFunGame`                            |
| `Campaign ID`            | A standardized identifier used across systems for this campaign. | string     | `12345`                                |
| `Campaign Name`          | The standardized name of the campaign used across systems.       | string     | `My Fun Campaign`                      |
| `Country`                | Country code                                                     | string     | `US` / `CA`                            |
| `Country Name`           | Country full name                                                | string     | `United States of America` / `Canada`  |
| `Date`                   | A specific date in `YYYY-MM-DD` format (ISO 8601 format).        | string     | `2023-09-07`                           |
| `OS`                     | The device operating system.                                     | string     | `Android` / `iOS`                      |
| `Placement Type`         | The type of placement for the ad.                                | string     | `Banner` / `Interstitial` / `Rewarded` |
| `Store ID`               | The advertised app bundle.                                       | string     | `my.fun.game`                          |
| `Supply Account Name`    | The publisher app developer.                                     | string     | `Fun Game Studio`                      |
| `Supply Source Category` | The publisher app category.                                      | string     | `puzzle` / `casual`                    |
| `Supply Source ID`       | The publisher app bundle or site.                                | string     | `another.fun.game`                     |
| `Supply Source Name`     | The publisher app or site name.                                  | string     | `Another Fun Game`                     |


---

# 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://docs.digitalturbine.com/dt-growth/reporting-api/reporting-api-metrics-and-dimensions.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.