Connecting Naver Search Ads on Clarisights
Naver is the dominant search engine in South Korea. Naver Search Ads is the paid-search platform that runs alongside Naver search results and across Naver's owned properties. Connecting Naver Search Ads to Clarisights brings campaign, ad group, ad, and keyword performance — including PC vs Mobile splits and direct / indirect conversion metrics — into your reporting alongside other paid channels.
At a glance
| Authentication | Naver Search Ads API license (X-API-KEY), secret key (used for HMAC X-Signature), and customer ID (X-Customer) |
| Permissions needed | API access enabled in the Naver Search Advertiser Tools → API Manager. Account ID is fixed at credential issue time and cannot be changed later. |
| Account discovery | Manual — one Naver ad account per credential set; Account ID is provided on the connect form |
| Data freshness | Daily, with the last 2 days re-pulled on every refresh |
| Lookback window | Last 2 days on every refresh |
| Backfill on connect | Last 2 days (longer historical backfills available via Clarisights support) |
| Timezone | Asia/Seoul (KST) |
| Currency | KRW (Korean Won) — converted to your reporting currency by Clarisights on ingest |
| Levels supported | Account · Campaign · Ad Group · Ad · Keyword |
| Limited rollout | No |
Prerequisites
An active Naver Search Advertiser account
API access enabled: in the Naver Search Advertiser Center, go to Tools → API Manager and issue an API license. This generates an API License Key and a Secret Key.
Your Naver Customer ID — visible in the Naver Search Advertiser Center header
Your Naver Account ID for the advertiser you want to connect
Steps to Connect
Step 1 — Issue an API license in Naver
Sign in to the Naver Search Advertiser Center, then go to Tools → API Manager and create an API license. Copy:
The API License Key (used as
X-API-KEY)The Secret Key (used to compute the request HMAC
X-Signature)Your Customer ID (used as
X-Customer)
Treat the Secret Key like a password. It is shown only once at creation time — if you lose it, you must reissue a new API license in Naver.
Step 2 — Add Naver in Clarisights
In Clarisights, go to Integrations → Naver → Add Account.
[TODO: Screenshot needed — Integrations page Naver row]
Step 3 — Enter credentials
Provide:
Account Name — a friendly label for this connection
API License Key — from Naver API Manager
API Secret Key — from Naver API Manager
Customer ID — from Naver Search Advertiser Center
Account ID — the Naver advertiser account to connect
Click Submit. Clarisights signs a test request with the Secret Key, validates the credentials against Naver's API, and creates the ad account on success.
[TODO: Screenshot needed — Naver credentials form]
⚠ Validation fails with HTTP 401 / 403 → The API License Key, Secret Key, or Customer ID is incorrect, or the API license has been revoked in Naver. Reissue the license in Tools → API Manager and retry.
⚠ HTTP 429 "TooManyRequests" → Naver enforces strict per-customer rate limits. Wait a minute and retry; if it persists during normal use, contact Clarisights support.
Verify the connection
Go to Integrations → Naver. Your account should appear with a "Connected" status.
First data appears within ~24 hours (Naver data syncs daily).
Quick start: create a new report, add Naver as the data source, and add Account · Campaign · Ad Group · Impressions · Clicks · Cost.
Data available
Hierarchy
Naver Search Ads exposes a five-level hierarchy that maps directly onto the standard Clarisights levels, with Keyword surfaced as an additional reporting dimension under Ad Group.
Native level (Naver) | Clarisights level |
Ad Account | Account |
Campaign | Campaign |
Ad Group | Ad Group |
Ad | Ad |
Keyword | Keyword (reporting dimension under Ad Group) |
Dimensions
Dimension | Level | Description |
Account ID | Account | Naver advertiser account ID |
Campaign / Campaign ID | Campaign | Campaign name and ID |
Campaign Status | Campaign | Current status of the campaign |
Campaign Type | Campaign | Determines where customers see your ads and the settings available (e.g. Shopping, Website) |
Ad Group / Ad Group ID | Ad Group | Ad Group name and ID |
Ad Group Status | Ad Group | Current status of the ad group |
Mobile Channel ID | Ad Group | Unique ID of the mobile business channel containing this Ad Group |
PC Channel ID | Ad Group | Unique ID of the PC business channel containing this Ad Group |
Ad / Ad ID | Ad | Ad name and ID |
Keyword / Keyword ID | Keyword | Keyword text and ID (under Ad Group) |
Platform Type | All levels | PC vs Mobile breakdown — metrics are stored separately for the two platforms |
Metrics
All performance metrics are stored separately for the two platforms (PC & Mobile) so you can break down or filter by Platform Type.
Metric | Description |
Impressions | Total impressions |
Clicks | Total clicks |
CTR | Clicks ÷ Impressions |
Cost | Total spend in KRW |
CPC | Cost per click |
CPM | Cost per thousand impressions |
CPA | Cost per conversion |
Conversion Rate | Conversions ÷ Clicks |
Conversion metrics are split into Direct Conversions and Indirect Conversions:
Conversion metric | Description |
Purchase Conversions | Completed purchase events attributed to Naver clicks |
Advanced Purchase Conversions | Higher-intent purchase events (e.g. specific funnel stages) |
Cart Conversions | Add-to-cart events |
Subscription Conversions | Subscription / signup conversions |
Other Conversions | Other tracked conversion events |
Conversion Revenue | Total revenue from attributed conversions, in KRW (also available converted to reporting currency) |
Limitations & known constraints
One account per credential set: a Naver API license issued for a Customer ID covers a specific Account ID. Use separate credential sets to onboard additional Naver accounts.
Account ID is fixed at connect time: changing the Account ID for an existing connection requires creating a new connection rather than editing the existing one.
Asia/Seoul timezone: report timestamps are always in Asia/Seoul (KST). Per-account timezone overrides are not supported.
KRW only: cost and conversion revenue are reported in KRW. Clarisights converts to your reporting currency on ingest.
Rate limits: Naver enforces strict per-customer rate limits (HTTP 429). Backfills are paced automatically; brief 429s during a refresh are retried internally.
Async stat reports: Naver returns daily performance via async stat-report jobs (REGIST → WAITING → AGGREGATING → RUNNING → ready). Refreshes wait for the day's report to be in a non-running state before pulling.
2-day pull window: Each refresh pulls the last 2 days of data. Older data is not back-pulled automatically; contact support for longer historical backfills.
Operating notes
Refresh schedule: daily.
Lookback: last 2 days re-pulled on every refresh, so late-arriving Naver updates are picked up automatically.
Multi-account: each Naver API license + Customer ID + Account ID combination is one Clarisights connection. To onboard multiple Naver advertisers, add a separate connection per advertiser.
Currency conversion: cost and revenue are stored in KRW and converted to your reporting currency on ingest.
Credential rotation: rotate the API license in Naver under Tools → API Manager, then update both keys in Clarisights via Integrations → Naver → Edit Credentials. The Customer ID and Account ID stay the same as long as you continue advertising under the same Naver account.
Need help?
When contacting support from the in-app messenger, please include:
The integration name and account name (Integrations → Naver)
The exact error message or screenshot
The step where the issue occurred
When the issue started