Naver began providing reach reporting for display advertising on August 12, 2026. Campaigns that could previously only be judged on impressions and clicks now get a second axis: how many people were actually reached.
What the report shows
The report counts users exposed to an ad at least once — reach. It aggregates at the campaign and ad group level, across daily, weekly and monthly periods, and delivers results as a CSV download.
Numbers arrive in 10,000-unit buckets
The key constraint sits here. Reach is not reported as an exact figure but bucketed in units of 10,000. Campaigns running small budgets or narrow targeting may never cross a bucket boundary, making changes effectively invisible. Using reach as a performance metric presupposes enough spend to move those buckets.
Logged-in users only
Aggregation is based on signed-in Naver users. Impressions served to logged-out visitors fall outside the count, so the figure functions as a floor rather than a true total. If you divide impressions by reach to estimate frequency, remember the numerator and denominator are measured on different bases.
Lookback limits and exclusions
Only the last 62 days are queryable, and same-day real-time data is not provided. The maximum single query span is 31 days at daily granularity, 4 weeks at weekly, and 1 month at monthly. ADVoost shopping campaigns and reach at the creative or placement level are excluded from aggregation.
How to actually use it
The practical value of reach is frequency control. If impressions rise at constant spend while reach stays flat, you are hitting a small pool repeatedly — which produces creative fatigue and stalled brand awareness. For awareness campaigns the logic inverts: expanding reach is the objective itself, so reach can replace impressions in the reporting slot it used to occupy.
The 62-day retention and 31-day query cap are really instructions to change your operating habit. Pulling data when the quarterly report is due means the early weeks are already gone. Download the CSV monthly and accumulate it in your own store. For the same pattern of wiring platform-side validation and reporting in before you need it, see Google Adds a Campaign Data Import Validation Report; for organizing metrics into layers, see A 5-Layer Framework for Measuring AI Search Performance.