Why you cannot track the QR code your design tool made

Does Canva track QR code scans?

Canva does not track scans, and neither does Adobe Express or most design tools. They generate a static code, meaning your web address is written directly into the pattern. A phone reading it goes straight to your site with nothing in between, so no counter exists anywhere for the tool to report from.

This surprises people because every other part of a design tool records something. The code is the exception, and the reason is structural rather than a missing feature.

Can you track QR code scans in Adobe Express?

You cannot track QR code scans in Adobe Express. It generates a static code, the same as Canva, so your web address is written into the pattern and the scan never reaches Adobe at all. There is no setting, no paid tier and no export that adds scan counts, because there is no counter to read from.

The Adobe case has one twist the Canva case does not, and it catches people who ought to know better. A company already paying for Adobe Analytics reasonably assumes the two connect. They do not, and the reason is the same structural one: a static code hands the phone a URL, the phone goes to that URL, and nothing in the journey touches Adobe. Analytics can only see what lands on your site, and it cannot tell a scan from a click unless the address in the code says so.

Which is the fix, and it is free: put campaign parameters on the destination before you generate the code. The UTM builder writes them for you, and the poster then arrives in Adobe Analytics, or Google Analytics, as itself rather than as direct traffic. It still will not separate a scan from somebody typing the address, which is its own problem, but it is the difference between knowing which poster worked and knowing nothing.

The same is true of the QR generator in InDesign, under Object, Generate QR Code. It is the one most print work actually goes through, it has been there for years, and it produces the same static object: a beautiful vector code, correctly drawn, that counts nothing.

There is nothing in the middle

A QR code is a way of writing text. When a design tool encodes yourshop.co.ke/menu, the finished picture contains those characters and nothing else. The phone reads them and goes there directly.

Counting requires something in the path: an address that belongs to a service, which records the visit and then forwards it. That is the whole difference between a static code and a dynamic one, and it has to be decided before the code is generated, because it changes what the pattern says.

So no setting in the design tool will retrofit this. There is no toggle, and a tool offering one would be quietly regenerating your code.

If it is already printed

It depends entirely on what the code encodes, and there are two cases.

It points at your own site. You are fine. You control that address, so you can redirect that page elsewhere and count the traffic on the way through, or read the visits in whatever analytics the site already runs. Nothing needs reprinting.

It points somewhere you do not control, a booking platform, a social profile, a shared document. Then the pattern is fixed, the destination is not yours to redirect, and no amount of configuration reaches it. The only fix is a new code, which means new printing. This is why the decision belongs before the print run.

What to do instead

Generate the short link first, then paste it into the design tool. The layout does not change: a QR code made from a different address is the same kind of object and occupies the same square.

What you gain is a counter, the ability to re-aim the destination without reprinting, and the separation between a camera scan and an ordinary tap, which is what tells you whether the printed thing is working or whether all the traffic came from the version you also posted online.

Adding campaign parameters to the destination is the other half and is worth doing as well, with one caveat: analytics counts arrivals at the page, not scans of the code, and those differ whenever the same link is shared anywhere else. Our UTM builder lower-cases the values, because analytics treats two capitalisations as two campaigns and halves your numbers.

What scan counts still will not tell you

Switching to a trackable code raises a different expectation, so it is worth setting the ceiling here.

You will learn how many scans, roughly where, on what kind of device, and at what hour. You will not learn who. That is not a plan limit, it is what the data is, and any product implying otherwise is selling you something. The full version of that argument, including where the legal line sits, is in can you track who scans a QR code.

One number to treat carefully from day one: chat apps fetch links to build previews, and those fetches are not people. A code shared in a group can look three times more successful than it was unless the bot traffic is separated out.