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

## Introduction

CrossTarget is a Korean programmatic advertising platform spanning display, video, and Connected TV (CTV) campaigns. The connector authenticates with a single API key, fetches daily CSV reports across all three campaign types, and stores them in a unified schema, with a report-type breakdown identifying the source report.

As a marketing connector, CrossTarget metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. The CrossTarget connector is currently in beta.

To connect this data source, see [How to connect CrossTarget to Adriel](/data-sources/a-f/crosstarget/how-to-connect).

## Data refresh strategy

CrossTarget is a daily-cache connector: a fixed number of recent days are re-fetched on every scheduled run and stored in Adriel's cache. It does not maintain a separate architecture pipeline; campaign group, campaign, and ad identifiers are surfaced as breakdowns rather than a separately refreshed hierarchy.

**Initial fetch.** On first connection, the last **90 days** of historical daily data are pulled.

**Refresh schedule.** The cache refreshes once per day at **22:00 UTC** (07:00 KST). On each run, the most recent **3 days** are re-fetched and updated in place. Days are fetched one at a time, and the current day is included in the refresh window.

Because only the most recent 3 days are re-fetched, adjustments CrossTarget makes to data older than 3 days are not reflected unless the data source is re-synced.

## Architecture levels

CrossTarget exposes ad-level performance. Campaign group, campaign, and ad identifiers are surfaced as breakdowns rather than separately refreshed hierarchy levels:

Campaign group → Campaign → Ad

## 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 `impression` is the literal CrossTarget CSV field. *Italic text* describes how a value is produced when it does not map cleanly to a single API field.
</Note>

### Performance

| Metric               | Description                                              | Data type | API Key             |
| -------------------- | -------------------------------------------------------- | --------- | ------------------- |
| Impressions          | Total ad impressions.                                    | Number    | `impression`        |
| Viewable impressions | Impressions that met CrossTarget's viewability criteria. | Number    | `impression_p_view` |
| Clicks               | Total clicks.                                            | Number    | `click`             |
| Ad spend             | Amount spent.                                            | Currency  | `amount`            |

### Video viewthrough

<Note>
  Viewable impressions and the video viewthrough metrics are populated only for video and CTV campaigns; display campaign rows leave these fields empty by design.
</Note>

| Metric               | Description                                   | Data type | API Key          |
| -------------------- | --------------------------------------------- | --------- | ---------------- |
| Start (viewthrough)  | Video view starts attributed via viewthrough. | Number    | `start_p_view`   |
| 25% video completion | Plays reaching the 25% mark.                  | Number    | `25_p_view`      |
| 50% video completion | Plays reaching the 50% mark.                  | Number    | `50_p_view`      |
| 75% video completion | Plays reaching the 75% mark.                  | Number    | `75_p_view`      |
| Completed views      | Plays reaching 100% completion.               | Number    | `completed_view` |

### Conversion performance

| Metric           | Description                                | Data type | API Key          |
| ---------------- | ------------------------------------------ | --------- | ---------------- |
| Installs         | App installs attributed to the ad.         | Number    | `install`        |
| App opens        | Subsequent app opens attributed to the ad. | Number    | `open`           |
| Purchases        | Purchase events attributed to the ad.      | Number    | `purchase`       |
| Purchase revenue | Monetary value of attributed purchases.    | Currency  | `purchase_price` |

### Custom events

<Note>
  The meaning of each custom event slot depends on the advertiser's CrossTarget setup. All 14 slots are available regardless of report type.
</Note>

| Metric            | Description                                       | Data type | API Key                                                                                 |
| ----------------- | ------------------------------------------------- | --------- | --------------------------------------------------------------------------------------- |
| Custom event 1–14 | Generic event counters configured in CrossTarget. | Number    | `e1`, `e2`, `e3`, `e4`, `e5`, `e6`, `e7`, `e8`, `e9`, `e10`, `e11`, `e12`, `e13`, `e14` |

## Breakdowns

Every field in the CrossTarget schema is available as a breakdown.

### Time

| Breakdown     | Description                                              | API Key |
| ------------- | -------------------------------------------------------- | ------- |
| Date          | Report date.                                             | `date`  |
| Day of week   | Day of the week, remapped from the CSV `day` column.     | `day`   |
| Month of year | Month of the year, remapped from the CSV `month` column. | `month` |

### Campaign structure

| Breakdown         | Description           | API Key               |
| ----------------- | --------------------- | --------------------- |
| Campaign group    | Campaign group name.  | `campaign_group_name` |
| Campaign group ID | Campaign group index. | `camp_g_idx`          |
| Campaign          | Campaign name.        | `campaign_name`       |
| Campaign ID       | Campaign index.       | `camp_idx`            |
| Ad                | Ad name.              | `ads_name`            |
| Ad ID             | Ad index.             | `ads_idx`             |

### Delivery

| Breakdown | Description                             | API Key     |
| --------- | --------------------------------------- | ----------- |
| Inventory | Inventory the impression was served on. | `inventory` |
| Ad size   | Creative ad size.                       | `ad_size`   |
| Channel   | Distribution channel.                   | `channel`   |
| Platform  | Platform the ad ran on.                 | `platform`  |

### Report type

<Note>
  Report type is set by Adriel during ingestion to identify which CrossTarget report each row came from — display, video, or CTV.
</Note>

| Breakdown   | Description                                                             |
| ----------- | ----------------------------------------------------------------------- |
| Report type | Source report: `DISPLAY_CAMPAIGN`, `VIDEO_CAMPAIGN`, or `CTV_CAMPAIGN`. |

## Limitations

* **Beta connector** — CrossTarget is in beta; its schema and behavior may change.
* **3-day refresh window** — only the most recent 3 days are re-fetched on each run, so changes to older data are not picked up without a re-sync.
* **90-day initial history** — first-time connection fetches at most the last 90 days; older data is never retrieved.
* **Video metrics on display rows** — viewable impressions and the video viewthrough funnel are empty for display campaigns.
* **One data source per API key** — the asset identifier is derived from a hash of the API key, so connecting the same key twice resolves to the same Adriel data source.

## See also

* [How to connect CrossTarget to Adriel](/data-sources/a-f/crosstarget/how-to-connect) (paired how-to)
* [Targeting Gates data reference](/data-sources/o-z/targeting-gates/data-reference)
* [Naver GFA data reference](/data-sources/g-n/naver-gfa/data-reference)