Why do Purchase Complete (구매완료) numbers update faster than my other conversions?
Purchase Complete (구매완료) is retrieved through a separate, faster fetch path than the other conversion events, then merged into the same report rows. As a result, its counts and value can refresh ahead of metrics like 구매 (Purchase), 가입 (Sign-up), and 장바구니 넣기 (Add to cart) for the most recent days. The gap is temporary. Once the other conversion events sync, the numbers line up again. For the full sync schedule, see the Naver Search Ads data reference.Why does reach look too high over longer date ranges?
Reach is a uniqueness metric, and Naver Search Ads report data is served from cached daily snapshots. Uniqueness is computed within each snapshot rather than de-duplicated across the whole range, so a person counted on more than one day is counted more than once when several days are combined. Over a multi-day range, reach can therefore be overstated. For a truer unique count, view reach one day at a time rather than summed across a long window. Impressions and clicks are additive and are not affected.Why do older dates take longer to load than recent ones?
Recent data (today and the most recent day) is available almost immediately, while older dates are assembled from a report that Adriel generates and downloads on request. Building that report for an older window takes longer, so a widget covering past dates can take a moment to populate on first load. Once built, the result is cached, and subsequent views of the same range are fast. Reliable history covers the most recent 1 year. Older data relies on the legacy cache and may be incomplete or unavailable.Why did my connection fail before any data loaded?
Naver Search Ads requires a valid Customer ID alongside the API credentials. If the Customer ID is missing or entered incorrectly, the connection is rejected up front, before any request reaches Naver, so no data loads. The fix is to re-enter the correct Customer ID from the Naver Search Ad account and reconnect. See How to connect Naver Search Ads to Adriel for where each credential comes from.Can I report in a currency other than KRW?
No. Naver Search Ads amounts are reported in Korean won (KRW) only, and the connector does not convert them to another currency. Currency-type metrics such as ad spend, CPC, CPM, and conversion value all appear in KRW. To compare Naver Search Ads spend against sources reported in a different currency on the same dashboard, apply conversion in a custom metric rather than expecting the connector to convert.Why doesn’t keyword data go back as far as campaign data?
The initial history imported when the data source is first connected differs by level. The ad account, campaign, ad set, and ad levels load a longer backfill than the keyword level, so keyword reporting reaches back a shorter distance in time. Because Adriel caches the data, the longer the data source stays connected, the more history accumulates. Separately, data for an element deleted on the Naver side is not retrievable after deletion, so a removed keyword, ad, or campaign stops returning rows. Exact per-level windows are listed in the Naver Search Ads data reference.Related
Naver Search Ads data reference
Metrics, breakdowns, refresh cadence, and limits for the connector.
How to connect Naver Search Ads
Credentials needed and the steps to connect the data source.
Naver GFA data reference
For display and feed ads across Naver’s GFA network.
Naver Smart Store data reference
For e-commerce orders and store performance on Naver.