The programme changed. The QR codes did not have to.

Print deadlines run weeks ahead of the programme

Every event has the same collision. Signage, badges and printed programmes are committed to a printer long before the schedule is final, and then the schedule changes: a session moves rooms, a speaker drops out, the sponsor page is not ready, the app store listing appears three days late. A static QR code encodes the destination inside the pattern itself, so every one of those changes turns printed material into a dead end.

A dynamic QR encodes a short link instead, and the link decides where the scan lands at the moment it happens. The printed artwork is fixed the day it goes to press; the destination is a field you edit from a phone while standing in the hall. Nothing about the pattern changes, so codes already printed on a thousand badges keep working.

This also removes the worst failure mode of event print, which is a QR that leads somewhere embarrassing after the event has finished. Set an expiry date on the link and the code stops resolving to a live session page on its own, showing a branded page you control rather than a 404 from somebody else's server.

• ✓Destination editable after printing, with no change to the printed pattern
• ✓Expiry date per link, so codes retire on schedule
• ✓Branded stub page instead of a stranger's 404 when a link is retired
• ✓Vector export for large-format signage that has to stay sharp

Which stand, which badge, which page of the programme

The useful question after an event is not how many scans there were. It is which placement earned them. That only becomes answerable if each placement carries its own link, which is why the workflow here is built around generating many links at once rather than one at a time: a link per stand, per session, per printed page, per badge type, each with the same destination and its own identity.

Every scan is then attributed on its own. You see the split between the entrance banner and the programme insert, whether the sponsor panel at the back of the hall was ever noticed, and how the badge QR performed against the one on the lanyard card. Tags and folders keep several hundred of these organised by day, hall or sponsor.

Timing is where event data differs from ordinary campaign data, and the reports are built for it: activity is reported by the visitor's own local hour, so the coffee-break spike and the keynote-exit spike land where they actually happened rather than being smeared across a server time zone.

• ✓One link per placement, generated in bulk before print
• ✓Scans attributed per stand, session, page and badge type
• ✓Activity by the visitor's local hour, not the server's
• ✓Folders and tags to keep hundreds of links navigable

A phone in a conference hall is a hostile environment

Scans at events come from phones on congested networks, often inside an in-app browser because the attendee opened the code from a social feed. The mobile section on each link handles that explicitly: your app when it is installed, the correct store page when it is not, a web fallback when neither applies, and a separate setting for what happens inside the embedded browsers of Instagram, TikTok and Facebook, which handle app links inconsistently.

Country and language routing matters more at an international conference than almost anywhere else. One code on one badge can send a visitor from Germany to the German programme and everyone else to the English one, without printing two versions of the badge.

If your app is the thing you are promoting at the event, deferred context is the piece that keeps the attribution intact: the visitor scans, installs from the store, and the app receives the original campaign context on first launch, so the signup is still tied to the stand that produced it.

Running it for a client, not just for yourself

Event agencies rarely run one event. Each client gets an isolated workspace with its own users, its own domain and its own links, so last year's conference and this year's trade show never share a reporting view. The sponsor who asks for numbers can be given a viewer role and read their own results without being able to edit anything.

Links can sit on the event's own domain rather than yours — a conference with its own brand usually wants scans landing on a hostname that matches the signage. Certificates are issued and renewed automatically on every plan, which matters when a domain is registered a fortnight before the doors open.

When the event is over, the workspace is the archive: the links, the scans, the timings and the geography stay together in one place for at least twelve months, which is long enough to plan the next edition from the last one.

• ✓One workspace per event or per client, fully isolated
• ✓Links on the event's own domain with automatic certificates
• ✓Read-only access for sponsors and stakeholders
• ✓At least 12 months of history to plan the next edition