Back to blog
Guides

How to track QR code scans: static vs dynamic QR codes explained

Zayd
Nov 19, 2026·5 min read

QR codes had a strange career. For years they were a marketing punchline, and then, almost overnight, every restaurant table had one. Now they're on packaging, posters, business cards and conference badges. Yet for most of them, nobody can answer a simple question: how many people actually scanned it?

Whether you can answer that comes down to one decision you make before printing: static or dynamic.

Static vs dynamic QR codes

A static QR code stores the destination directly in the pattern. Your phone reads the full address straight out of the squares and goes there. Nothing sits in between, which sounds simple, but it comes with two hard limits. Nobody can count the scans, because no server is involved. And nobody can change the destination, because it's printed into the ink.

A dynamic QR code stores a short link instead. Scanning it takes the phone to that short link first, which then redirects to wherever you want people to go. That extra hop takes a few milliseconds, and it's what makes counting and editing possible.

  • Static: destination baked in, no scan data, can't be edited, doesn't rely on any service.
  • Dynamic: points at a short link, counts every scan, destination can change at any time.

For a one-off code on a Wi-Fi password card, static is fine. For anything printed in quantity, anything you'll want to measure, or anything that might need a new destination next month, go dynamic.

How a scan gets counted

When someone scans a dynamic code, their phone requests the short link like any other web address, and that request is the scan. The server notes when it happened, roughly where it came from and what kind of device made it, then sends the phone on to the destination. The person never notices; it's over before the page starts loading.

There's a catch that most QR tools ignore. If your QR code and your social posts use the same short link, you can't tell scans apart from clicks. To the server, both are just requests for the same address.

TRIMS fixes that by giving QR codes a path of their own. A code made for trims.app/menu actually encodes trims.app/q/menu. Both reach the same destination, but anything arriving through /q/ is counted as a scan, so your report shows how many people came from the printed code and how many from the link you shared online.

What scan data can and can't tell you

Scan analytics answer the questions that matter for print. When do people scan, and does that match your opening hours? Which cities did the flyers actually reach? Is the code on the front of the box beating the one on the back? Print two versions of a poster with two different codes and you can see which one earned more scans.

What they can't tell you is who scanned. A scan carries no name or email, and it shouldn't. If you want to know whether a scan turned into a sale, that's a job for conversion tracking on your website, which connects a visit to a signup or a purchase.

Printing a QR code that actually scans

A code that looks perfect on screen can fail on paper. A few rules of thumb:

  • Size it for the distance. A common guide is about 1 cm of code for every 10 cm between the code and the person scanning. A table card can be small; a shop window needs something much bigger.
  • Don't go below roughly 2 x 2 cm (0.8 inch). Smaller than that, older phone cameras struggle.
  • Leave the quiet zone alone. The empty border around the code is part of it, so don't crop it or set text right against the edge.
  • Keep the contrast strong. A dark code on a light background is the safe choice; pale colours and light-on-dark codes fail on some scanners.
  • Keep the address short. Fewer characters means fewer, larger squares, which scan more reliably at small sizes. It's one more reason to encode a short link rather than a long URL.
  • Test on several phones before the print run, including an older Android.

Logos, colours and error correction

QR codes have error correction built in, which is why you can cover part of one with a logo and it still works. There are four levels: L can recover from about 7% damage, M from 15%, Q from 25% and H from 30%. Higher levels make the pattern denser but more forgiving.

If you put a logo in the middle, use Q or H so the covered squares can be rebuilt. If the code will live somewhere it might get scratched or folded, like packaging, a higher level is worth it too. In TRIMS you can choose the level, colours, gradients and module shapes, and download the result as PNG or SVG. Send the SVG to your printer; it stays sharp at any size.

Changing the destination after printing

This is where dynamic codes earn their keep. The menu changes, the sale ends, the landing page moves. With a static code, those thousand printed flyers now point at the wrong place. With a dynamic code, you change the destination behind the short link and every scan from then on follows the new address. Nothing needs reprinting.

Because TRIMS answers each scan fresh instead of letting phones remember the old answer, the change applies from the very next scan.

Common questions

Do QR codes expire? A static code never expires, because it doesn't depend on anything. A dynamic code works for as long as the service behind it keeps the link alive. On TRIMS, links keep redirecting on every plan, Free included, and we don't switch off links you've already shared.

Can I track scans from a code I've already printed? Only if it's dynamic. A static code goes straight to its destination, so no service ever sees the scan. The fix is to replace it, or at least tag future codes with UTM parameters.

Should every code be dynamic? Almost always. The only good reason to choose static is a code that has to work forever with nothing behind it at all.

Zayd
Founder & Engineer, TRIMS

Building TRIMS — a fast, honest link platform with analytics that actually help you decide.

Next up
Branded short links: how to set up your own short domain