Choosing between a short link and a QR code
They solve the same problem in different physical situations. Sometimes the answer is both, pointing at the same destination.
A short link is for a screen. A QR code is for a surface.
Use a short link when the reader can click
Email, social posts, chat messages, slides shown on a call. Anywhere a tap is possible, a QR code adds a step for no benefit.
Short links also survive being read aloud and typed, which matters for radio and podcasts — keep the alias pronounceable.
Use a QR code when the reader cannot click
Packaging, posters, menus, receipts, business cards, signage. The reader is holding a phone in front of a physical object, and typing a URL is the thing you are eliminating.
Use both when the medium is ambiguous
A printed brochure that is also distributed as a PDF should carry both: the code for the printed copy, the readable link for the digital one. Point them at the same destination with different `utm_content` values and you learn which format people used.
Keep attribution clean
Whichever you choose, tag it. An untagged short link and an untagged QR code both arrive as "direct" traffic, which is where campaign budgets go to become unaccountable.
What each one actually costs the reader
The decision is usually framed as a channel question. It is better framed as a question about effort.
A short link asks for a tap if it is clickable and a full retype if it is not. On a printed page, a URL is roughly twenty characters of error-prone typing on a phone keyboard, which is why printed URLs convert so poorly compared to how often they are read.
A QR code asks the reader to raise a phone and point it. That is close to zero effort where a camera is already in hand, and impossible where the medium is itself a screen the reader is holding — nobody scans a code on the phone they are scanning with.
The case for putting both on the same asset
On anything that might be read either on paper or on a screen — a PDF invoice, a presentation deck, an email that gets printed — put both, pointing at the same destination but as two separate trackable objects.
The reader takes whichever route their situation allows, and you learn something useful for free: the split between them tells you how your material is actually being consumed. A deck where the code dominates is being projected; one where the link dominates is being read at a desk. That is worth knowing before you design the next one.