> ## Documentation Index > Fetch the complete documentation index at: https://docs.adriel.com/llms.txt > Use this file to discover all available pages before exploring further. # FAQs > Common questions, expected behaviors, and troubleshooting for the Naver Blog data source. Answers to common questions about expected behaviors, authentication, and limits for the Naver Blog data source. ## Why won't my Naver Blog connection authenticate? Naver Blog connects with a Naver account ID and password rather than through an authorization pop-up, so a few account-side settings have to be in place for the login to succeed. If any of them block the login, the data source is disconnected and reports an authentication error. Before reconnecting, confirm the Naver account meets these conditions: * **Two-step verification is turned off.** The connector signs in directly, and an active two-step prompt stops the login. * **Logins from the Seoul region are allowed.** Naver's region-block security setting will reject the connection otherwise. * **The ID and password are the current, valid credentials** for an account that owns the blog. Once the settings are corrected, reconnect from [How to connect Naver Blog to Adriel](/data-sources/g-n/naver-blog/how-to-connect). ## Why can't I use my Naver email address to connect Naver Blog? Naver Blog rejects an ID in email format (anything containing `@`) before the login is even attempted. The connection expects the plain Naver login ID or the phone number registered to the account, not the full email address. Entering the login ID without the `@naver.com` portion resolves this. ## Why don't I see historical post rankings? Post rankings always reflect the most recent snapshot. Each sync fully replaces the ranking tables, so only the latest ranking is kept — earlier ranking snapshots are not retained and cannot be reconstructed for a past date range. Blog-level metrics behave differently. Visits, unique visitors, impressions, followers, neighbors, and post count are stored as a daily time series that accumulates over time, so those metrics do support historical reporting. To track how the blog trends over time, use the blog-level metrics rather than the ranking breakdowns. ## Why can't I combine blog metrics and post rankings in one widget? Blog-level metrics and post-ranking metrics come from separate tables, so they cannot be selected together unless a compatible ranking breakdown is also chosen. An incompatible mix returns an error rather than an empty result. To report both, build them as separate widgets: one for blog-level metrics (for example, blog visits over time) and one for a post ranking (for example, post view ranking). For the full list of which metrics pair with which breakdown, see the [Naver Blog data reference](/data-sources/g-n/naver-blog/data-reference). ## How many posts appear in a ranking? Each post-ranking breakdown returns up to 100 posts, ordered by the ranked metric (views, likes, or comments). Rankings are available either grouped by post URL or grouped by post title. When the selected period has no ranking activity, the ranking returns a single placeholder row instead of post rows. ## Why does my Naver Blog data sometimes fail to update? Naver does not publish a public API for blog statistics, so the connector reads the figures directly from Naver's blog admin pages. That makes it more sensitive to changes on Naver's side than an API-backed data source, and an occasional sync failure is expected. These transient failures are retried automatically, so most resolve on the next cycle without any action. For how often the data refreshes, see the [Naver Blog data reference](/data-sources/g-n/naver-blog/data-reference). If a data source stays in a failed or disconnected state across several syncs, recheck the account security settings above, then reconnect. If the problem continues after that, email `support@adriel.com` with the blog ID and the affected dashboard URL. ## Related Step-by-step setup, including the required Naver security settings. Metrics, breakdowns, refresh cadence, and limits for the data source. Naver's local business analytics, connected with the same ID and password. Paid search reporting for Naver campaigns.