> ## 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.

# FAQs

> Common questions, expected behaviors, and troubleshooting for the CrossTarget data source.

## Why are my viewable-impression and video-completion numbers empty for display campaigns?

This is expected behavior. CrossTarget shares one field schema across all three report types, but the video funnel metrics — viewable impressions, view starts, the 25% / 50% / 75% completion counts, and completed views — are only populated for video and CTV campaigns.

Rows that come from a display campaign leave these fields empty because the source report does not return video engagement values for display inventory. Impressions, clicks, and ad spend are still populated for display rows.

To read the video funnel, filter or break down by report type and focus on the `VIDEO_CAMPAIGN` and `CTV_CAMPAIGN` rows.

## How do I separate display, video, and CTV performance?

CrossTarget stores display, video, and CTV rows in a single unified schema, and Adriel tags each row with a report type during ingestion. Adding the **Report type** breakdown to a widget splits the data into its three sources:

* `DISPLAY_CAMPAIGN`
* `VIDEO_CAMPAIGN`
* `CTV_CAMPAIGN`

This breakdown can be combined with campaign group, campaign, or ad breakdowns to compare the same structure across formats. For the full field list, see the data reference.

## What do my Custom event 1–14 columns mean?

CrossTarget exposes 14 generic custom event counters, surfaced as Custom event 1 through Custom event 14. The meaning of each slot depends entirely on how the advertiser configured events in CrossTarget — Adriel passes the counts through without assigning fixed labels.

All 14 slots are available regardless of report type. A slot that was never configured in CrossTarget will simply report no values. To interpret a specific column, check which event that slot number is mapped to inside the CrossTarget account.

## Why don't my recent edits to older data show up?

Each scheduled refresh re-fetches only the most recent few days of data and updates them in place. Adjustments CrossTarget makes to data outside that window are not picked up automatically, so a correction applied to a date from several weeks ago will not appear on the next regular refresh.

To pull those older changes into Adriel, re-sync the data source so the affected range is fetched again. For the exact size of the refresh window, see the [CrossTarget data reference](/data-sources/a-f/crosstarget/data-reference).

## How far back does CrossTarget history go when I first connect?

Adriel imports up to the last 90 days when the data source is first connected. Because Adriel caches the data, the longer the data source stays connected, the more historical data is stored — each refresh adds newly available days on top of what is already cached.

Dates older than the initial 90-day import are not retrieved retroactively, so connecting earlier means more history is captured over time.

## Why does connecting the same API key twice not create a second data source?

CrossTarget derives a data source's identity from a hash of its API key. Two different API keys produce two different data sources, but the same API key always resolves to the same one.

As a result, connecting a key that is already in use reconnects the existing data source rather than creating a duplicate. To create a genuinely separate data source, use a different CrossTarget API key. The display name chosen during setup is independent of this identity, so renaming a data source does not change which key it points to.

## Related

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