UTM for QR codes vs NFC tags
QR codes and NFC tags both bridge a physical touchpoint to a tagged URL, but they differ in how the URL is delivered and scanned. Both can carry UTM parameters so an offline interaction is attributed online; the practical differences are in scanning behaviour, capacity, and which one suits a given placement.
How each delivers the URL
A QR code is a printed image the camera decodes into a URL; an NFC tag stores a URL that a phone reads on a tap. Both open the URL directly, usually with no referrer, so a UTM on that URL is the only signal of the offline source.
Use a consistent scheme — for example utm_source=qr or utm_source=nfc, utm_medium=offline, and a utm_campaign for the placement — so each physical channel is identifiable and the two are not conflated.
- QR: camera decodes a printed image into a URL
- NFC: phone reads a stored URL on tap
- Both open directly, usually with no referrer
Practical trade-offs
QR works on any flat printable surface and from a distance; NFC needs proximity and a tag with capacity for the URL, so keep tagged URLs reasonably short (a shortlink helps). Distinguish them with different utm_source values so you can compare scan-from-print against tap-from-tag for the same placement.
Scanning behaviour varies by device and OS, and there is no single vendor UTM recipe, so this entry is partially verified. Test that your encoded URL opens with its UTM intact on the devices you expect.
How it appears in analytics and logs
A tagged arrival from a QR or NFC touchpoint shows the UTM values you encoded, identifying the offline source. The referrer is typically empty because the URL opens directly, so UTM is what makes the offline channel measurable.
Diagnostic use case
Choose between a QR code and an NFC tag for an offline campaign while ensuring either delivers a UTM-tagged URL so the physical touchpoint is attributed in analytics.
What WebmasterID can help detect
WebmasterID records tagged QR and NFC arrivals server-side with no referrer, so you can attribute offline touchpoints by their UTM and separate them from web channels.
Common mistakes
- Using the same utm_source for QR and NFC, conflating the channels.
- Encoding a device, location, or person in the URL.
- Putting a long tagged URL on an NFC tag without considering capacity.
- Assuming a referrer will identify the offline source — there usually is none.
Privacy and accuracy notes
Encode only campaign metadata in the URL. Do not encode a specific device, location, or person in a QR or NFC URL; UTM describes the campaign, not the individual who scanned.
Related pages
- QR code campaign tracking with UTM
A QR code is just an encoded URL, so encoding a UTM-tagged link turns print, packaging, and signage into measurable offline-to-online traffic. This page shows the structure, a worked example, and the rule that no personal data goes in the encoded URL.
- UTM for TV and print attribution
Offline media — TV, radio, print, out-of-home — has no clickable link, so UTMs cannot ride a click. Instead you give each offline placement a vanity URL, QR code, or promo code that redirects to a UTM-tagged landing page. This page explains designing that offline-to-online bridge.
- UTM and shortlink services
Shortlink services redirect a short URL to a longer destination. They can carry UTM parameters to the final page, or strip and re-add them, depending on configuration. Knowing how your shortener handles the query string is essential so a memorable short URL does not silently lose its campaign attribution.
- Campaign links docs
Attribute QR and NFC touchpoints by their UTM.
Sources and verification notes
- Google Analytics Help — Collect campaign data with custom URLsUTM parameters that make offline QR/NFC touchpoints measurable.
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.