WebmasterID logoWebmasterID
UTM tracking

Naver Ads UTM tracking

Naver is South Korea's leading search portal, and Naver Search Ad (and GFA display) drives a large share of Korean-market paid traffic. Because Naver's own analytics ecosystem is separate from Google's, you tag landing-page URLs with UTM parameters to attribute Naver ad clicks correctly in tools like GA4 or a privacy-first analytics platform.

Partially verified

Tag the landing URL

Naver Search Ad does not push UTM values for you, so append them manually to the final URL you register for each ad. Use a stable utm_source=naver, choose utm_medium=cpc for search ads and utm_medium=display for GFA banners, and set utm_campaign per campaign.

Keep the source token lowercase and identical across every Naver ad so the portal aggregates as one channel in your reports.

Naver vs Google in Korea

In the Korean market Naver and Google compete for search share, so collapsing both into a single "search" bucket hides real channel performance. Distinct utm_source values keep them separable.

Naver provides its own conversion and analytics tooling; UTM tags are the bridge that lets the same Naver click appear in a cross-platform analytics tool alongside other sources.

How it appears in analytics and logs

A landing hit with your Naver UTM set indicates a paid click from the Naver portal. The medium (cpc vs display) tells you which Naver ad product drove the visit; it says nothing about the person.

Diagnostic use case

Distinguish Naver paid search and display from Google and organic Korean search, and report Naver as a first-class acquisition channel.

What WebmasterID can help detect

WebmasterID logs the tagged Naver landing hit as a campaign touch, keeping Korean paid search separate from organic and direct so the channel is visible without a Naver-only analytics tool.

Common mistakes

Privacy and accuracy notes

UTM values describe the Naver ad product and campaign, not the visitor. Korean-market geography is inferred coarsely at the edge and never pinned to an exact location or a raw IP.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.