Tracking, QR & Attribution
Static QR Codes vs Unique QR Codes
A static QR code is one code, printed on every piece in a run, that sends everyone to the same page. A unique QR code is one code per recipient, each pointing to a link that identifies exactly who scanned it. Static codes are cheaper to set up and fine for simple, unpersonalized uses. For a targeted B2B campaign, unique codes are what actually make attribution, personalization and real-time sales alerts possible.
Practical guide · Published August 22, 2026 · Written by Jeffrey Huis in 't Veld
The core difference
A static QR code is generated once and printed on the entire run. Scan it from any postcard in the campaign, and every scan opens the same URL, no matter whose piece it was printed on. That's fine when the destination is genuinely meant to be identical for everyone, a general company website, a public offer page, a menu.
A unique QR code is generated per recipient as the mailing list is processed, so each piece carries a code pointing to a link with a token specific to that person or account. Visually the codes are indistinguishable, both are just a printed pattern encoding a URL. The difference only shows up in what happens after the scan: a unique code lets the system know exactly whose piece was scanned before the landing page even loads.
Comparison at a glance
| Static QR code | Unique QR code | |
|---|---|---|
| Setup complexity | Low, one code generated and printed on the whole run | Higher, a code is generated and mapped to a record for every recipient before printing |
| Attribution capability | Campaign-level only, total scans with no way to trace individual response | Recipient- or account-level, each scan resolves to a specific record |
| Personalization capability | None, every scan lands on the same generic page | Landing page and follow-up can reflect who the visitor is |
| Best use case | A general, non-personalized destination shared across a broad, undifferentiated audience | A targeted B2B or high-value B2C campaign where knowing who responded matters |
Where static codes still make sense
Static codes aren't a mistake, they're a fit for a narrower set of situations. A local landscaping company putting a QR code on a yard sign that just links to its website doesn't need per-scan identity, it needs an easy way for a passerby to find the site. A single reusable code on packaging, a menu or a general awareness flyer works the same way, the goal is a low-friction destination, not attribution. In those cases, generating a unique code per piece would add setup cost for a benefit nobody's going to use.
Why unique codes usually win in targeted B2B mail
A targeted B2B campaign is built around a defined list, thousands of specific accounts chosen because they fit a profile worth pursuing individually. That's exactly the situation where a static code's biggest weakness shows up: it can tell you the campaign got a certain number of scans, but not which of those thousands of accounts actually responded. For a campaign where the whole point is following up with the right person at the right company, that gap defeats much of the purpose of tracking in the first place.
Unique codes close that gap. A scan resolves to the account it was mailed to, which is what makes it possible to route a real-time alert to the right rep, greet the visitor on the landing page with something specific to them, and build attribution reporting that shows which segments, industries or account tiers actually engaged rather than one flat number for the whole run.
What switching actually requires
Moving from static to unique codes isn't a print decision so much as a data decision. It requires the mailing list to have a distinct identifier generated for each recipient before the print file is built, a landing page system that can look up and respond to that identifier, and somewhere for the resulting scan event to get logged, typically a CRM. None of that changes what the postcard looks like to the recipient. It changes what the campaign can tell you afterward.
Frequently asked questions
Print cost itself isn't meaningfully different, modern variable-data printing handles a unique code per piece about as easily as a shared one. The added cost, if any, is in the setup work of generating and mapping codes to records, not the printing.
It's possible, but there's rarely a good reason to. If the campaign has any tier worth measuring at the account level, which most targeted B2B tiers are, a unique code costs little extra to include and closes the attribution gap for that tier entirely.
Not inherently, both are just a printed pattern encoding a URL. What matters for security is how the destination handles the identifier, sensitive information shouldn't be exposed in the URL itself regardless of which code type is used.
Not for pieces already printed and mailed, the code is fixed once it's on paper. A later run of the same campaign can switch to unique codes going forward, but it won't retroactively add attribution to pieces already in recipients' hands.
No, scanning a unique code looks and feels identical to scanning a static one from the recipient's side. All the added capability happens on the system side, invisible to the person holding the phone.
Related topics
Work with Yotru
How Yotru uses unique codes by default
Yotru generates a unique QR code for every recipient as standard practice, not an upgrade tier, because a targeted B2B or high-value B2C campaign gets little value from a shared code that can't identify who responded. Each scan can trigger a real-time alert to sales and rolls up into attribution reporting by account, segment or list tier, which is the kind of measurement a static code simply can't produce. .