QR Code Tracking: How to Track Scans and Read the Numbers

QR code tracking starts with a dynamic code: give each placement a separate code and review activity over a defined date range. Scan tracking records requests reaching the managed destination. It does not count everyone who saw the material, every camera recognition or completed sales.

This walkthrough is for campaign operators. For software selection, read our QR analytics buyer guide.

Can an existing static code be tracked?

A static code has no QRCodeStack scan reporting because its content is encoded directly in the pattern. An existing printed pattern cannot be converted into a dynamic one.

You may separately measure the website it opens if you control that website. Its page can change while the encoded URL stays fixed. Such website activity does not reconstruct missing QR-level history or necessarily distinguish QR visitors from other visitors.

How should you prepare the campaign?

Separate the placements you need to compare and test the complete journey. One code shared between flyers and signs gives a combined total.

1. Create a dynamic QR destination for each independently measured placement.
2. Record the code name, artwork, location, launch date and responsible owner.
3. Scan the final proof or actual display; follow the link and complete the advertised action.
4. Record your test window so test activity is not mistaken for campaign response.

Your own phone scans can appear in reports. Keep destination edits and distribution dates in the same campaign log.

What does the analytics dashboard show?

The Analytics page for a dynamic code reports these measures:

• Totals: Total Scans, Unique Visitors and Avg Scans/Day.
• Technology: Device Types, Operating Systems and Browsers.
• Source and timing: Referrers and Daily Scans.
• Where and when: countries, cities, the map and a Busiest Times heatmap, included during the trial and on Business.

Pro and Business can use Export CSV to download the loaded date range. Compare codes over the same dates before drawing conclusions.

Which reporting settings matter?

Use matching dates and traffic filters when comparing codes. The scan analytics instructions explain the people-focused view, which separates automated, preview and rapid repeat activity.

Visitor estimates are technical approximations, not named customers. Unexpected location data is not proof of fraud or physical presence. If activity disappears, check the code, date range, destination and active entitlement before changing the artwork. City and map views require Business among paid plans, or an active trial; check reporting access by plan.

Why do scans and sessions differ?

They measure different points in the journey. A page might fail to load, tracking may be blocked or declined, and session rules can combine visits.

Hypothetical diagnostic example: 80 QR interactions and 60 campaign sessions produce a 75% reconciliation ratio: 60 ÷ 80. That is not a conversion rate or proof that 20 people abandoned the page. Investigate collection and definitions first.

For labelled website sessions, Google’s UTM guidance explains campaign parameters. Tags alone cannot record a submitted form.

What should the review produce?

Record the window, settings, tests and next investigation. Compare placement duration and exposure before reallocating spend. If exposure is unknown, report activity counts without inventing a scan rate. Confirm business outcomes separately.