> ## 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 Naver GFA data source.

## Why is my reach higher than expected over a multi-day date range?

Reach counts unique users, and Naver GFA report data is served from cached daily snapshots. Uniqueness is computed per snapshot rather than deduplicated across the full range, so a user who saw the ad on more than one day can be counted more than once. Over a range longer than a single day, reach and other uniqueness-based metrics can be overvalued.

For an accurate figure, view reach one day at a time, or treat multi-day reach as an upper bound rather than an exact unique count. Impressions, clicks, and spend aggregate normally across days and are not affected.

## Why can't I see data for a deleted campaign or ad?

Naver GFA does not provide deleted elements. Once a campaign, ad set, or ad is deleted on the platform, its data is no longer available to the connector and it stops appearing on the dashboard, including for dates when it was still active.

To keep a record before removing something in Naver GFA, export or screenshot the relevant widget while the element still exists. Pausing an element instead of deleting it keeps its historical data available.

## Why does my agency-managed account need a Manager Account ID?

Naver GFA routes access to agency-managed ad accounts through a manager account. When an ad account sits under an agency, the connector needs the Manager Account ID that has access to it. Without it, requests to the account fail with permission errors.

If a Naver GFA connection reports permission errors for an agency-managed account, confirm the Manager Account ID is set on the connection. See [How to connect Naver GFA to Adriel](/data-sources/g-n/naver-gfa/how-to-connect) for where this is configured.

## What currency are my Naver GFA amounts reported in?

All Naver GFA monetary metrics, such as ad spend, CPC, CPM, and conversion value, are reported in Korean won (KRW). This is fixed for the data source and cannot be changed on the connection.

For dashboards that combine Naver GFA with sources reporting in other currencies, apply a currency conversion at the widget or dashboard level so totals aggregate consistently.

## Why is some data missing or truncated for a very large query?

Naver GFA applies limits on how much data can be returned at once, and very large queries can be truncated. Report data is also considered reliable only within the cached sync period; requests reaching well outside that period may return incomplete or missing values.

To reduce the chance of truncation, narrow the date range, reduce the number of breakdowns on the widget, or split a broad query into smaller dashboards. Date-range caps also vary by time granularity, which is covered in the [Naver GFA data reference](/data-sources/g-n/naver-gfa/data-reference).

## Related

<CardGroup cols={2}>
  <Card title="Naver GFA data reference" href="/data-sources/g-n/naver-gfa/data-reference">
    Metrics, breakdowns, refresh cadence, and limits for Naver GFA.
  </Card>

  <Card title="How to connect Naver GFA to Adriel" href="/data-sources/g-n/naver-gfa/how-to-connect">
    Connect a Naver GFA ad account, including agency-managed setups.
  </Card>

  <Card title="Naver Search Ads data reference" href="/data-sources/g-n/naver-search-ads/data-reference">
    The sibling Naver connector for search ads, which uses a different authentication model.
  </Card>

  <Card title="Refresh strategies" href="/data-sources/how-data-works/refresh-strategies">
    How Adriel caches and refreshes data across connectors.
  </Card>
</CardGroup>