Tracking, QR & Attribution
Can You Tell Which Prospect Scanned a Postcard?
Yes, as long as that postcard carried a QR code unique to them rather than one shared across the whole campaign. The scan resolves to the exact record it was printed for, which is a reliable way to know which piece got scanned. Whether the person who physically scanned it is the named recipient specifically is a related but separate question, and it's worth understanding the difference.
Practical guide · Published August 22, 2026 · Written by Jeffrey Huis in 't Veld
The short answer
If a campaign uses a unique QR code per recipient, as opposed to printing the same code on every postcard in the run, then yes, a scan can be traced back to a specific prospect. The code doesn't just confirm that someone in the campaign scanned something, it identifies exactly which piece, and therefore which name and account, the scan belongs to. This is the mechanism that makes real-time sales alerts and per-account attribution reporting possible in the first place.
Why this works: one code per recipient
The mechanics are covered in more depth in how unique QR codes work, but the short version is that each recipient's postcard is printed with a code pointing to a link that includes a token specific to them. When that code is scanned, the system looks up which record the token belongs to before doing anything else. That lookup is what turns "a scan happened" into "this account's postcard was scanned," and it's the piece that a single shared code across the whole campaign can't provide.
Where "which piece" and "which person" diverge
Here's the distinction worth being precise about: the system can tell you with certainty which piece of mail generated the scan, because that's what the code encodes. It can't put a camera on the hand holding the phone. In the large majority of cases those two things are the same, the person the postcard was addressed to is the one who opens their own mail and scans it. But mail doesn't always work that way in an office setting, and it's worth knowing the situations where the gap can show up.
Common scenarios worth knowing about
A front-desk assistant or office manager who opens mail before it reaches the addressee might scan a code out of curiosity on behalf of someone else. A colleague could see an interesting postcard on a coworker's desk and scan it themselves. In a household with a shared mailbox for high-value B2C campaigns, a spouse or family member might be the one who actually picks up the phone. None of these scenarios are common enough to make the data unreliable, but they're real enough to keep in mind before treating a single scan as a guarantee that the exact named person is now personally engaged.
How confident should you be in a single scan?
In practice, one scan is a good enough signal to justify a personal follow-up, since even in the scenarios above the scan still means someone at that specific account engaged with the mailer, which is valuable regardless of exactly who held the phone. What builds real confidence is what happens after the scan: if the recipient later replies to an email referencing the postcard, or shows up to a meeting booked through the landing page, that closes the identity gap on its own. A rep doesn't need to resolve the "who exactly scanned this" question before reaching out, they just need to reach out in a way that makes sense whether it was the named contact or someone else at that company.
Frequently asked questions
Not much. A shared code can tell you a total scan count for the campaign, but every scan resolves to the same destination, so there's no way to trace any individual scan back to a specific recipient. That's the core tradeoff covered in static QR codes vs unique QR codes.
Only if the campaign assigned one code per account rather than per individual contact. If two people at a company each got their own postcard with their own code, their scans are tracked separately even though they work at the same place.
Not automatically. A scan shows interest or at least curiosity, which is a reasonable trigger for a timely follow-up, but it's not the same as a form fill or a reply that states clear intent. Treat it as a prompt to reach out, not as a qualified lead on its own.
Some setups can capture an approximate location based on where a scan occurred, useful mainly for confirming a scan happened somewhere plausible, like the recipient's office area. It's not precise enough, and shouldn't be treated as precise enough, to draw conclusions beyond that.
Follow up in a way that works either way, referencing the account or the offer rather than assuming a specific individual's personal interest. If it turns out to be a different person at the company, that's still a legitimate lead worth pursuing.
Related topics
Work with Yotru
How Yotru identifies who scanned
Every postcard Yotru mails carries a QR code unique to the recipient it was printed for, so a scan resolves to that specific person's or account's record rather than an anonymous entry in a campaign-wide total. That identification is what powers real-time sales alerts and per-account attribution, and it's a meaningfully stronger signal than the shared, non-personalized codes some campaigns still rely on. .
