Skip to main content

​
Introduction

Naver Smart Place is Naver’s local business listing platform in South Korea — the equivalent of Google Business Profile for the Korean market. Business owners register their storefront on Naver Smart Place and appear on Naver Search and Naver Map with reviews, reservations, and receipt-linked visitor data. This connector reports on that visibility: daily and cumulative review counts (including a breakdown of Naver Map review types), replied reviews, reservations, and receipts. Because Naver does not publish an official API for Smart Place, data is captured through headless-browser automation that logs in with Naver credentials and intercepts the GraphQL and statistics responses from Naver’s own frontend. To connect this data source, see How to connect Naver Smart Place to Adriel.

​
Data refresh strategy

Naver Smart Place data refreshes once daily. Each cycle logs in, navigates to the reviews, statistics, and Naver Map pages for the selected place, and upserts the day’s row into the historical time series (so past days are preserved). The list of places available on a Naver account is cached for 3 hours after credentials are validated.

​
Architecture levels

Each Naver Smart Place data source represents a single Naver place. When a Naver account owns multiple places, users can create up to 10 data sources per connection — one per selected place — from the multi-select step during the connection flow.

​
Metrics

How to read the columnsData type vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.Naver Smart Place has no documented public API, so no literal API field name applies. The API Key column instead notes, in italics, the Naver page or endpoint each value is intercepted from.

​
Reviews

​
Reservations & receipts

​
Place metadata

​
Breakdowns

​
Time & date grouping

Adriel groups Naver Smart Place’s daily-granularity results into these standard views for reporting alongside other connectors.

​
Place

​
Overview

These are Adriel-side groupings, not Naver breakdowns.

​
Limitations

  • Scraped, not API-backed — Naver Smart Place does not offer a public REST API. All data is captured by a headless browser logging in as the account owner and intercepting the responses that Naver’s own frontend calls. This makes the connector sensitive to UI or API-shape changes on Naver’s side.
  • ID + password required — the connection requires the Naver login ID (or phone number) and password. Email-format IDs (containing @) are rejected before login is attempted.
  • Two-step verification must be disabled on the Naver account, or login will fail with an MFA error and the data source will be disconnected.
  • Seoul-region logins must be allowed in Naver security settings. Naver’s default region-block behavior will block the connector’s login attempts and disconnect the data source.
  • Up to 10 places per connection — the multi-select step during connection is capped at 10 places. Accounts with more places must create additional connections.
  • Booking-type places skip Naver Map metrics — if a place redirects to Naver Booking rather than a Naver Map profile, the Naver Map metrics (total reviews, blog reviews, keyword/star reviews) return zero for that place.
  • Ownership transfer blocks scraping — while a place ownership change is under review on Naver, no data can be scraped for that place until the transfer completes.
  • CAPTCHA fallback — Naver may occasionally serve a CAPTCHA during login. The connector attempts to solve it up to three times before disconnecting the data source.

​
API references

Naver Smart Place does not publish an official API. The connector reads from Naver’s own frontend endpoints:

​
See also