Can QR Codes Be Tracked? What Scan Analytics Can—and Can’t—Tell You

KnowledgeConcepts & Principles

Published

Share
Illustration for Can QR Codes Be Tracked? What Scan Analytics Can—and Can’t—Tell You

Overview

A QR Code can be part of a tracking setup, but the pattern itself does not produce a scan report. It encodes data, such as a URL. [1] To measure activity, a system must observe an event: a website analytics tool can report campaign traffic that reaches a tagged destination, while a server can return an HTTP redirect to another URL. [2][3] Those are different measurement points. A scan attempt is not automatically a website visit, a session, or a conversion.

Two measurement points to understand

Measurement point What it can tell you What it does not tell you by itself
Website analytics on the destination Visits recorded on a site configured with analytics; UTM tags can identify campaign values in reports. [3] Scan attempts that never reach the measured page, or activity on a site you do not measure
A redirect endpoint A server can return an HTTP 3xx response that directs a client to another URI. [2] If its operator separately records requests, it may have request data to report. That a report exists, how it defines a “scan,” whether requests represent distinct people, or what visitors do on the destination

The second row describes a possible implementation, not a universal QR product feature. The HTTP standard defines redirects; it does not require an operator to log requests or offer an analytics dashboard. [2] If a service advertises scan reports, check its documentation for what it counts, filters, and retains.

Use UTM tags to measure campaign traffic on your site

If a QR Code opens a website you manage, you can add campaign parameters to the destination URL before encoding it. Google Analytics documents parameters such as utm_source, utm_medium, and utm_campaign, and explains how campaign data can appear in the Traffic acquisition report. [3]

For example, a restaurant menu link could be:

https://example.com/menu?utm_source=table-tent&utm_medium=qr&utm_campaign=summer-menu

Choose a consistent naming convention for each placement. You might use a different utm_source for a table tent and a takeout bag, while keeping the same utm_campaign. Google recommends setting utm_source, utm_medium, and utm_campaign when using campaign URLs. [3]

A simple GA4 setup sequence

  1. Choose a page you manage. Confirm that it is live and that your Analytics tag is configured to collect data there.
  2. Build the tagged URL. Set consistent values for utm_source, utm_medium, and utm_campaign. Keep names readable and avoid putting a person’s name, email, or other personal information in the URL.
  3. Encode the complete destination. Create the QR Code using the full tagged URL as its encoded content. The URL is part of the QR data; the code itself does not add analytics. [1]
  4. Test the path. Scan the actual image, check the link preview, and confirm the intended page opens. If the URL passes through a redirect, verify that the campaign parameters reach the destination as expected.
  5. Review the report. Google documents campaign parameters in the Traffic acquisition report. [3] Check the property, date range, and Analytics configuration; this report is not a camera scan counter.

A QR Code with a fixed URL can include UTM parameters from the start. Analytics can then classify visits that reach the tagged page. If you later change the encoded URL, the image does not rewrite itself; a redirect can lead to a different destination only if the server handling the encoded URL is configured to do so. [1][2]

Why scan counts and website visits can differ

Consider a QR Code that opens a tagged product page directly. If the visitor reaches the page and Analytics records the campaign, the report can show a tagged visit. It does not measure a camera scan that failed to open the link or never reached the instrumented page. [3]

Now consider a code that opens a URL which returns an HTTP redirect before sending the visitor to the tagged page. [2] The redirect endpoint and the destination website are separate points in the journey. The redirect operator could record requests if its system is configured to do so; Analytics could record a visit if the destination loads and collects the tagged campaign. The two systems would then be reporting different events. The HTTP redirect standard does not establish what any operator records, and Google Analytics campaign reporting does not count every camera scan. [2][3]

Neither measure alone proves a sale. A conversion is another event that must be defined and recorded in the relevant analytics setup. Treat redirect request data, website campaign traffic, and conversions as separate metrics unless your own implementation verifies how they relate.

What QR tracking cannot establish on its own

  • A verified person or intent: A QR image encodes data; it does not identify the person who points a camera at it. A count does not prove that a person read the page, intended to engage, or completed a purchase. [1]
  • A particular service’s “unique” or “location” meaning: These labels depend on that operator’s definitions and collection methods. Review its documentation and privacy information before using them to make decisions.
  • Every visit or conversion: Website analytics only describes events recorded by the setup on that website. It cannot, by itself, reveal events that did not reach that measurement point.
  • The accuracy of every tracking setup: Test the final URL and review the actual reports available in the analytics property. Do not infer a dashboard’s capabilities from the QR image or from the HTTP redirect standard.

Before enabling a tracking service, review what information it collects, why it collects it, who can access it, and how long it is retained. The FTC advises businesses to explain their data practices, collect only information they need, protect it, and dispose of it securely. [4] Keep campaign labels focused on placements and campaigns rather than identifying individuals.

Choose the measurement method for your question

  • You need to compare visits to your own website: Use tagged destination URLs and review the campaign traffic recorded by your Analytics setup. [3]
  • You need request data from a redirect endpoint: First verify that the endpoint operator documents and provides the specific report you need. HTTP redirection alone does not promise reporting. [2]
  • You need both views: Use campaign tags for website visits and a separate redirect measurement system only if its documentation confirms the metrics you need. Label the reports separately; they may count different events.
  • You do not need campaign measurement: Use the destination URL that fits your task. Do not add tracking merely because a QR Code can encode a tagged link.

Before printing, record the full encoded URL, UTM naming convention, redirect owner if applicable, Analytics property, and the person responsible for maintaining the destination. Scan the final code and confirm it opens the intended page.

Frequently asked questions

Can a QR Code with a fixed URL be tracked?

The image does not create a QR scan dashboard. If the encoded URL includes UTM parameters and opens a website configured with Analytics, the site may record campaign traffic when the page is reached. [1][3] That is not a count of every scan attempt.

Can Google Analytics count QR Code scans?

Google Analytics can report campaign traffic associated with UTM-tagged destination URLs. [3] It does not measure camera activity that never reaches the configured website, so do not treat its report as a raw scan counter.

Can a QR Code tell me who scanned it?

Not by itself. The QR image carries encoded data, not a verified identity. [1] Any additional information depends on the systems and data practices used after the scan; review those systems’ documentation and privacy information. [4]

References

[1] DENSO WAVE. “FAQ: QR Code’s Intellectual Property Right.” https://www.qrcode.com/en/faq.html/about/request.html

[2] Internet Engineering Task Force. “RFC 9110: HTTP Semantics,” section 15.4, Redirection. https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4

[3] Google Analytics Help. “URL builders: Collect campaign data with custom URLs.” https://support.google.com/analytics/answer/10917952?hl=en

[4] Federal Trade Commission. “Privacy and Security.” https://www.ftc.gov/business-guidance/privacy-security

Ready to create your QR code?

Create QR Code