> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data reference

> Metrics, breakdowns, refresh cadence, and limits for the Moloco data source in Adriel.

## Introduction

Moloco is a mobile and CTV (Connected TV) programmatic advertising platform for app growth and performance marketing. The connector retrieves campaign performance across four hierarchy levels from the Moloco Cloud CM API v1, authenticated through a short-lived Bearer token exchanged from four user-supplied credentials.

As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration.

To connect this data source, see [How to connect Moloco to Adriel](/data-sources/g-n/moloco/how-to-connect).

## Data refresh strategy

### Architecture data

Architecture covers the ad account and its campaigns, ad sets, and ads. It refreshes twice daily, at **4:00 PM UTC** and **5:00 AM UTC**.

### Reports data

Reports include daily performance for the ad account, campaigns, ad sets, and ads.

**Cache-only.** Report data comes from cached daily performance snapshots rather than live calls to Moloco. Dashboard values are composed from the last snapshot, so the most recent few hours of activity are not yet reflected, and metrics based on uniqueness (such as reach) can be overvalued across date ranges longer than one day.

**Initial fill.** On data source creation, the cache fills with the last **730 days** of daily data at the ad account, campaign, ad set, and ad levels.

**Refresh schedule.** The cache refreshes **every hour (UTC)**, syncing the **last 60 days** across the ad account, campaign, ad set, and ad levels.

Data is considered reliable within the cache sync window. Older data may be incomplete or inaccurate due to legacy caching behavior.

## Architecture levels

Ad account → Campaign → Ad set → Ad

The ad set level maps to the Moloco API's `AD_GROUP_ID`, and the ad level maps to `CREATIVE_ID`.

## Date range limits

| Breakdown | Max range |
| --------- | --------- |
| Daily     | 93 days   |
| Weekly    | 1 year    |
| Monthly   | 2 years   |

## Metrics

<Note>
  **How to read the columns**
  **Data type** uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.
  **API Key** in code style like `impressions` is the literal Moloco API field or Adriel cell key. *Italic text* describes how a value is produced when it doesn't map cleanly to a single API field.
</Note>

### Performance

| Metric        | Description                                               | Data type | API Key        |
| ------------- | --------------------------------------------------------- | --------- | -------------- |
| Impressions   | Number of ad displays.                                    | Number    | `impressions`  |
| Clicks        | Number of ad clicks.                                      | Number    | `clicks`       |
| Clicks (all)  | Mirror of clicks, retained for aggregation compatibility. | Number    | `clicksAll`    |
| Spend         | Reported spend in the account currency.                   | Currency  | `spend`        |
| Pixel revenue | Attributed revenue reported by Moloco.                    | Currency  | `pixelRevenue` |

### Video engagement

| Metric              | Description                        | Data type | API Key     |
| ------------------- | ---------------------------------- | --------- | ----------- |
| Video plays at 25%  | Plays reaching the first quartile. | Number    | `videoP25`  |
| Video plays at 50%  | Plays reaching the midpoint.       | Number    | `videoP50`  |
| Video plays at 75%  | Plays reaching the third quartile. | Number    | `videoP75`  |
| Video plays at 100% | Plays reaching completion.         | Number    | `videoP100` |

### Conversions

<Note>
  Installs and conversions are exposed under Moloco's `conversions:moloco_reports:*` namespace, which keeps them distinct from the generic conversion metrics on other connectors.
</Note>

| Metric      | Description                                               | Data type | API Key                                  |
| ----------- | --------------------------------------------------------- | --------- | ---------------------------------------- |
| Installs    | App installs attributed by Moloco.                        | Number    | `conversions:moloco_reports:installs`    |
| Conversions | Post-install and custom conversions attributed by Moloco. | Number    | `conversions:moloco_reports:conversions` |

## Breakdowns

### Standard hierarchy

| Breakdown  | Description                                    | API Key     |
| ---------- | ---------------------------------------------- | ----------- |
| Ad account | Group by Moloco ad account.                    | `adAccount` |
| Campaign   | Group by campaign.                             | `campaign`  |
| Ad set     | Group by ad group (mapped from `AD_GROUP_ID`). | `adSet`     |
| Ad         | Group by creative (mapped from `CREATIVE_ID`). | `ad`        |

### Time grouping

<Note>
  Moloco returns daily records; Adriel groups them into these views for reporting. Each grouping has its own maximum date range (see Date range limits).
</Note>

| Breakdown | Description                      |
| --------- | -------------------------------- |
| Daily     | Split reports by day.            |
| Weekly    | Split reports by week.           |
| Monthly   | Split reports by calendar month. |

## Limitations

* **No platform breakdowns** — Moloco reports support only the account, campaign, ad-set, and ad hierarchy plus date groupings. Audience, device, geographic, and placement breakdowns are not available.
* **Cache-only delivery** — reports are served from scheduled snapshots, not on-demand pulls, so the most recent few hours of activity are not yet reflected. Reach across long date ranges can be overvalued, as with any cache-only connector.
* **Slower wide ad-level queries** — ad-level (per-creative) reports are fetched in smaller date chunks than higher levels because the Moloco API enforces a tighter range limit for them, so wide ad-level date ranges can take longer to load.

## API references

* [Moloco developer documentation](https://developer.moloco.cloud/)

## See also

* [How to connect Moloco to Adriel](/data-sources/g-n/moloco/how-to-connect) (paired how-to)
* [Amazon DSP data reference](/data-sources/a-f/amazon-dsp/data-reference)