FAQs

​

Why does my Kakao Keyword Ads dashboard only show KRW?

Kakao reports spend in Korean won (KRW) only, and the connector fixes every Kakao Keyword Ads ad account to KRW. No other reporting currency is available from Kakao’s API. When the ad account’s currency differs from the workspace currency, costs are converted automatically using the current day’s exchange rate, so widgets can still roll up alongside other data sources.

​

Why can I only go back 62 days when I add the hourly breakdown?

The hourly breakdown (Hour of day) is capped at a 62-day lookback. When the requested start date is older than 62 days, the query is rejected before any data loads, so the widget returns nothing rather than a partial result. To look further back, remove the hourly breakdown and use a daily, weekly, or monthly grouping instead. Those grouping options have their own longer date-range limits, listed in the Kakao Keyword Ads data reference.

​

Why is data older than 12 months incomplete?

Access to the most recent 12 months of data is guaranteed. Anything older is served from a legacy cache and may be incomplete or unavailable, so widgets that reach back beyond a year can show gaps or missing rows for the earliest dates. For the clearest reporting, keep long-range comparisons within the most recent 12 months where possible.

​

Why do my conversion numbers differ between the 1-day and 7-day windows?

Kakao tracks each conversion event through the Kakao Pixel and SDK on two attribution windows: a 1-day window and a 7-day window. The 1-day window credits only conversions that happen within a day of the interaction, while the 7-day window credits conversions up to seven days later, so the 7-day figure is usually the higher of the two. Imported events carry a window suffix so the same event can appear as two separate metrics (for example purchase_1D and purchase_7D). The standard Conversions, Conversion value, and Revenue metrics use Kakao’s 7-day purchase value by default. The data reference lists the full set of conversion metrics.

​

Why does ad-account-level data look aggregated from campaigns?

Kakao’s API does not accept a single query spanning all campaigns at once. Because of this, requests are split per campaign and merged, and an ad-account-level request is served as a campaign-level aggregation rolled up to the account. The totals are equivalent, but the account row is built from its underlying campaigns rather than fetched directly. To inspect the components, drill into the campaign breakdown.

​

Do I need to reconnect after Kakao’s OAuth migration?

In most cases, no. Access tokens are refreshed automatically in the background, and the connector supports both Kakao’s current and legacy sign-in flows, so existing connections keep syncing without manual steps. A reconnect is only needed if a dashboard starts showing an authorization error for the data source. To restore access in that case, see How to connect Kakao Keyword Ads to Adriel. If the error persists after reconnecting, email support@adriel.com with the ad account ID and the affected dashboard URL.

​

Related