Trade association · United States
How a trade association measures 39 pieces of print
Published September 19, 2026 · Customer since May 2026
A US industry trade association runs 39 dynamic QR codes across events, exhibition booths and member mailings, and has logged around 150 engaged scans. Judged on volume it is the quietest account in this collection. Judged on what it is actually for, it is the most disciplined: every piece of print reports separately, so next year’s budget is a decision instead of a guess.
Snapshot
- Codes in use
- 39
- Engaged scans
- ~150
- Customer since
- May 2026
- Code types
- Website and link codes
- Where scans come from
- Mostly United States, some EU
The situation
Thirty-nine codes, all website or link types, spread across events, booth materials and mailings to members. Roughly four scans per code since May 2026.
Nobody arrives at 39 codes by accident. This is a deliberate structure: one code per placement, per event, per mailing, so that every piece of print in circulation reports separately. For an association, that is the whole job. Membership is finite. Events are few. The question is never “did anyone show up” so much as “which thing earned the ones who did”.
The challenge
A trade association has a defined membership, a handful of events a year and a mailing list. It is not chasing footfall and never will be. The question that matters is not how many people responded but which thing they responded to: which booth, which mailing, which event earned the interest, because that determines where next year’s effort goes.
Conventional analytics cannot answer that for print. A single QR code across all the print cannot either — it returns one number for thirty-nine different decisions. Static codes make it worse: you cannot change the destination when a session page moves, and you still get no per-placement read. The association would be flying the next conference blind.
What they did
Mint a dynamic QR code per placement and accept that each one will show a small number. Thirty-nine separately reporting codes turn an unanswerable question into an answerable one, at no extra cost beyond the minute it takes to create each code. Plans are not billed per code, and paid plans include unlimited scans, so a quiet mailing and a busy booth cost the same.
This inverts the usual dashboard read. An account with 39 codes and 150 scans looks modest on volume. It is the only account here that can say with confidence which specific piece of print did the work. That is the report a board actually wants.
The university recreation team in this same collection arrived at the same structure from the opposite direction — around 125 codes across a campus, one per placement. Two organisations with nothing in common, both running print at scale, both independently concluding that the code should be minted per placement rather than per campaign. That convergence is the strongest evidence in this collection that the per-placement habit is the one worth copying.
The results
Around 150 engaged scans between May and September 2026, the majority resolving to the United States with a small European tail from the Netherlands, Germany and Ireland — consistent with a domestic membership and events that draw some international attendance.
The useful output is not the total. It is that all 150 are attributable to a specific placement. Four scans on a booth graphic and forty on a member mailing are two different budget decisions. A single shared code would have hidden both.
At a few scans per placement the numbers are directional across a season, not a weekly dashboard. Set that expectation internally and the report becomes usable: you drop the print that never moved, you double the mailing that did, and you do it with evidence instead of anecdotes from the stand.
39
codes, one per placement
~150
engaged scans in four months
~4
scans per code — and that is the point
Why this works
This is QRCodeStack as a print measurement system, not a scan-volume contest. One code per booth, mailing and event. Name them on day one, drop them in folders, and export the date range currently loaded on screen when you want a CSV for the board — set the range first, because the export follows what is on screen rather than full history.
Thirty-nine codes called “QR code 12” will teach nobody anything by next season, and nobody goes back to fix naming after the fact. The discipline is the product: create, name, place, read. When a landing page moves after the brochure is printed, change the destination in the dashboard. The print stays in members’ bags.
If you run events, member mailings or a conference programme, copy this before the next print deadline. See plans, or start the 7-day trial and mint a code for every piece of print you were about to send out with the same URL.
What to take away
- Code count measures organisation; scan count measures reach. Confusing the two makes disciplined accounts look like failures.
- For low-volume, high-value audiences, “which placement” is a far more valuable answer than “how many scans”.
- At a few scans per placement, read the data across a season. A weekly view is noise.
- Name and folder codes from day one, or a 39-code structure is worthless by next year.
See which print actually worked
Create a dynamic QR code per booth, mailing and event, then read next year’s plan off the report. 7-day free trial, no credit card.
Start your free trialThis customer is described by sector and region rather than named. Every figure is taken from our own analytics and rounded. Scan counts are engaged scans: bots and link-preview requests are excluded.
Related case studies
Higher education · United States
How a university recreation team runs 125 QR codes across a campus
A large US public university runs the biggest QR deployment on our platform: around 125 codes across campus, each placement reporting separately. Here is how it is organised.
Media agency · Europe
How a media agency keeps client campaigns live after print
A European media agency has run the same five dynamic QR codes for client campaigns since March 2026 without a break. Proof that the value of a dynamic code is the reprint you never have to do.