> ## 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 Targeting Gates data source. ## Why don't my CTR, ROAS, and conversion-rate columns total correctly? Targeting Gates reports several ratio fields — CTR, conversion rate, ROAS, post-view ROAS, and indirect conversion ROAS — as pre-computed values for each day, and Adriel stores them as text. Because they are text rather than numbers, they are not summed or averaged across rows, so a widget that tries to roll them up will not produce a meaningful combined figure. To get an aggregated ratio, define a custom metric over the underlying counts, spend, and revenue instead of using the reported ratio column. For example, a rolled-up CTR is clicks divided by impressions. The available metrics and their data types are listed in the [Targeting Gates data reference](/data-sources/o-z/targeting-gates/data-reference). ## Why did my data source disconnect right after I connected it? Targeting Gates requires two settings on the platform side before data can flow: Adriel's IP addresses must be whitelisted in the Targeting Gates account, and API access must be enabled for the account. If either is missing when the connection is first made, the connector reports an error and the data source is disconnected automatically. The fix is to correct the setting in the Targeting Gates account and then reconnect the data source. Steps for both prerequisites are covered in [How to connect Targeting Gates to Adriel](/data-sources/o-z/targeting-gates/how-to-connect). ## Why is some data missing on a very high-volume day? Targeting Gates data is read from a per-day CSV export. A single day with an unusually large number of rows can exceed the export's size limit, and rows beyond that limit are truncated at the source before they reach Adriel. When this happens, aggregated totals for that day can read slightly low. This affects only the largest days and is a limit of the CSV export itself, so narrowing a widget's breakdowns or date range does not recover the truncated rows. ## Why is Targeting Gates data taking a while to appear after I connect? On first connection, history is retrieved one day at a time, so a long historical range fills in gradually rather than all at once. The most recent days appear first, and older days continue to populate on the following scheduled refreshes. For the refresh schedule itself, see the [Targeting Gates data reference](/data-sources/o-z/targeting-gates/data-reference). Newly made campaign changes on the platform are not immediate either; they appear on the next sync. ## How far back can I see Targeting Gates data? Adriel imports up to the last 180 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. For an overview of how caching and retention work across sources, see [Data history and retention](/data-sources/how-data-works/data-history-and-retention). The Targeting Gates CSV export makes data available for up to 2 years from the current date. Days requested beyond that window return empty rather than raising an error, so very old ranges may show no data. ## Why do I see Korean column names in the field picker? Targeting Gates can export its CSV columns with either Korean or English headers, depending on the account's settings. Adriel recognizes both sets and maps them to the same standardized fields, so widgets work regardless of which locale the export uses. The column names shown in the field picker reflect whichever headers the source export returns. ## Related Metrics, breakdowns, refresh cadence, and limits for the connector. Whitelist IPs, enable API access, and add the CSV URL. Recent changes to the Targeting Gates data source. How Adriel refreshes cached connector data over time.