Data reference - Adriel Knowledge Base

Introduction

Naver Blog is Naver’s blogging platform in South Korea. This connector reports on blog-level engagement (visitors, impressions, follower and neighbor counts, post count) and on post-level rankings (top posts by views, likes, and comments). Data is captured from Naver’s blog admin pages using headless-browser automation because Naver does not expose a public API for blog statistics. To connect this data source, see How to connect Naver Blog to Adriel.

Data refresh strategy

Blog data refreshes on a daily cycle. Blog-level statistics are stored with an upsert strategy — each day’s snapshot is appended to the historical time series, keyed by the date and blog ID. Post-ranking tables use an atomic-replace strategy — the entire ranking is overwritten on every sync, so only the latest ranking snapshot is available. To limit repeat scraping within a single refresh window, raw scraped results are memoized in cache for 4 hours per blog.

Metrics

How to read the columnsData type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.Naver Blog does not have an official API, so no literal API field name applies. The Source column notes the Naver admin page each value is scraped from.

Blog-level metrics

Metric	Description	Data type	Source
Blog ID	The Naver blog URL slug for the connected account.	Text	Derived from account credentials at connection time.
Blog visits	Total visits to the blog on the given day.	Number	Scraped from `admin.blog.naver.com/{blogId}/stat/visit`.
Blog unique visitors	Distinct visitors to the blog on the given day.	Number	Scraped from `admin.blog.naver.com/{blogId}/stat/uv`.
Blog impressions	Total page views on the blog on the given day.	Number	Scraped from `admin.blog.naver.com/{blogId}/stat/visit_pv`.
Blog post count	Total number of published posts on the blog.	Number	Scraped from the blog’s public post list.
Neighbors added	Number of blog neighbors (mutual connections) the account has added.	Number	Scraped from the buddy management admin page.
Followers	Total followers of the blog.	Number	Scraped from the buddy management admin page.

Post-ranking metrics

Post-ranking metrics are only returned when the report uses a ranking breakdown (see below). The Naver ranking page returns up to 100 posts per ranking type (5 pages of 20).

Metric	Description	Data type	Available with breakdown
Post views	Views on a ranked post.	Number	Post view ranking, Post title view ranking
Post likes	Likes on a ranked post.	Number	Post like ranking, Post title like ranking
Post comments	Comments on a ranked post.	Number	Post comment ranking, Post title comment ranking

Breakdowns

Time & date grouping

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

Breakdown	Description
Auto Time Breakdown	Automatically picks the best granularity for the date range.
Daily	Split reports by day.
Weekly (Start: Mon)	Split reports by ISO week, starting Monday.
Monthly	Split reports by calendar month.
Quarterly	Split reports by calendar quarter.
Yearly	Split reports by calendar year.

Post rankings

Breakdown	Description
Post view ranking	Rank posts by number of views (grouped by post URL).
Post like ranking	Rank posts by number of likes (grouped by post URL).
Post comment ranking	Rank posts by number of comments (grouped by post URL).
Post title view ranking	Rank posts by number of views (grouped by post title).
Post title like ranking	Rank posts by number of likes (grouped by post title).
Post title comment ranking	Rank posts by number of comments (grouped by post title).

Overview

Breakdown	Description
No Grouping	Do not break down; return one aggregated row.
Data source name	Group by Adriel data source name.

Limitations

Scraped, not API-backed — Naver Blog does not expose a public REST API. All data is captured by a headless browser navigating the Naver admin pages, which makes the connector sensitive to UI changes on Naver’s side. Occasional scrape failures are expected and are automatically retried.
ID + password required — the connection requires the Naver login ID (or phone number) and password. Naver accounts that use an email-format ID (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.
Post rankings are capped at 100 posts per ranking type (5 pages of 20 posts).
Post rankings do not retain history — each sync fully replaces the ranking tables. Only the latest ranking snapshot is available; historical rankings are not preserved.
Cross-metric queries are limited — blog-level metrics and post-ranking metrics cannot be selected together in the same report unless a compatible ranking breakdown is chosen; incompatible selections return an error.
CAPTCHA fallback — Naver may occasionally serve a CAPTCHA during login. The connector attempts to solve it up to five times before disconnecting the data source.

API references

Naver Blog does not publish an official API for blog statistics or post rankings. The connector reads from Naver’s blog admin pages directly:

Naver Blog (blog.naver.com)
Naver Blog admin (admin.blog.naver.com) — requires login

​Introduction

​Data refresh strategy

​Metrics

​Blog-level metrics

​Post-ranking metrics

​Breakdowns

​Time & date grouping

​Post rankings

​Overview

​Limitations

​API references

​See also

Introduction

Data refresh strategy

Metrics

Blog-level metrics

Post-ranking metrics

Breakdowns

Time & date grouping

Post rankings

Overview

Limitations

API references

See also