> ## 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 Outbrain Ads data source in Adriel.

## Introduction

Outbrain is a global native advertising platform that distributes sponsored content recommendations across a network of publisher sites. The connector pulls campaign architecture and performance data from the Outbrain Amplify API for the marketers selected during connection setup.

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

<Note>
  The legacy Outbrain Custom connector is deprecated. New connections use Outbrain Ads (the V2 variant documented here). Existing Outbrain Custom widgets continue to function, but the connector is hidden from new-connection flows.
</Note>

To connect this data source, see [How to connect Outbrain Ads to Adriel](/data-sources/o-z/outbrain-ads/how-to-connect).

## Data refresh strategy

### Architecture data

Architecture covers marketers, campaigns, and ads. It refreshes twice daily, at **4:00 PM UTC** and **5:00 AM UTC**.

### Reports data

Reports include daily performance for marketers, campaigns, and ads.

**Real-time.** Report data is fetched from Outbrain Amplify on demand when a dashboard loads, so the latest values are always visible. On top of that, scheduled cache refreshes keep historical data consistent across multiple time windows.

**Refresh schedule.** Reports refresh on three overlapping schedules:

* **5:00 PM UTC daily** — syncs the last **9 days** for the marketer, campaign, and ad levels
* **11:40 PM and 6:40 AM UTC daily** — syncs the last **3 days** for the marketer, campaign, and ad levels
* **7:30 AM UTC on the 1st and 15th of each month** — syncs the last **30 days** for the marketer, campaign, and ad levels

## Architecture levels

Marketer → Campaign → Ad (promoted link)

## Date range limits

The maximum look-back window depends on the time granularity requested:

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

Date ranges are also bounded by what the Outbrain Amplify API exposes for each marketer. Older data outside the API's reporting window is unavailable.

## 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 Outbrain Amplify field name. *Italic text* describes how a value is produced when it does not map cleanly to a single API field.
</Note>

### Delivery & engagement

| Metric      | Description                                         | Data type  | API Key       |
| ----------- | --------------------------------------------------- | ---------- | ------------- |
| Impressions | Number of times the ads were displayed.             | Number     | `impressions` |
| Clicks      | Number of ad clicks.                                | Number     | `clicks`      |
| CTR         | Click-through rate — clicks divided by impressions. | Percentage | `ctr`         |

### Cost & spend

<Note>
  Spend and cost values are reported in the currency configured on the Outbrain marketer account.
</Note>

| Metric       | Description                                          | Data type | API Key               |
| ------------ | ---------------------------------------------------- | --------- | --------------------- |
| Spend        | Reported network spend.                              | Currency  | `spend`               |
| eCPC         | Effective cost per click.                            | Currency  | `outbrain:ecpc`       |
| CPA          | Cost per acquisition — spend divided by conversions. | Currency  | `cpa`                 |
| Total CPA    | Cost per acquisition across all conversion types.    | Currency  | `outbrain:totalCpa`   |
| DST fee cost | Demand-side technology fee cost.                     | Currency  | `outbrain:dstFeeCost` |

### Conversions & return

| Metric     | Description                                     | Data type | API Key              |
| ---------- | ----------------------------------------------- | --------- | -------------------- |
| ROAS       | Return on ad spend.                             | Ratio     | `roas`               |
| Total ROAS | Return on ad spend across all conversion types. | Ratio     | `outbrain:totalRoas` |

## Breakdowns

### Campaign structure

| Breakdown          | Description                       | API Key        |
| ------------------ | --------------------------------- | -------------- |
| Campaign           | Group by Outbrain campaign.       | `campaign`     |
| Ad (promoted link) | Group by individual sponsored ad. | `promotedLink` |

### Publisher

| Breakdown | Description                | API Key     |
| --------- | -------------------------- | ----------- |
| Publisher | Group by publisher domain. | `publisher` |

### Time grouping

<Note>
  Outbrain returns period-level records; Adriel groups them into these views for reporting.
</Note>

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

## Limitations

* **Publisher and Ad breakdowns are child-only** — the Publisher and Ad (promoted link) breakdowns cannot be used as the top-level (parent) breakdown; doing so returns an unsupported-parent-breakdown error. Use them nested under another breakdown, such as campaign.
* **One data source per marketer** — when a single set of credentials grants access to multiple marketers, each selected marketer becomes its own data source with its own asset, name, and currency. Cross-marketer rollups happen at the dashboard layer rather than inside a single data source.
* **Currency follows the marketer** — spend and cost metrics are reported in the currency configured on the Outbrain marketer account, not the workspace currency.
* **Login rate limit** — Outbrain enforces a maximum of two login requests per hour per account. The connector caches the session token (24 hours) and serializes re-login attempts to stay within the limit; brief delays can occur if the cache is invalidated during a burst of requests.
* **API reporting window** — historical data is limited to what the Outbrain Amplify API exposes for each marketer.

## API references

* Outbrain Amplify API base: `https://api.outbrain.com/amplify/v0.1/`
* [Outbrain Amplify API documentation](https://amplifyv01.docs.apiary.io/)

## See also

* [How to connect Outbrain Ads to Adriel](/data-sources/o-z/outbrain-ads/how-to-connect) (paired how-to)
* [Taboola data reference](/data-sources/o-z/taboola/data-reference) — the other major native advertising platform