An events manager in Antwerp ran a 400-person product conference last autumn. Every attendee badge had a QR code under the name — scan it, land on the live agenda with room numbers and session times. It worked beautifully for the two days of the event. People scanned it between talks to find the next room. The signage at the entrance had the same code, blown up to A1 size on a foam board. The sponsor banners had their own codes pointing at booth landing pages.
Three weeks after the event, she sent a follow-up email to all 400 attendees: thanks for coming, the session recordings are now up. She linked the recordings in the email. But she also still had the badges, the foam boards, and the banners in a storage room, and a handful of attendees who had kept their lanyard as a memento tried scanning the badge again to find the recordings. The code still pointed at the agenda — a page that now said “Day 2, Room B, 14:00,” for an event that had finished. The agenda CMS subscription she’d used to build it had a 30-day post-event window, after which the published page reverted to a generic “your trial has ended” screen .
She didn’t reprint anything. The badges were single-use, the banners were rolled up in storage, and nobody was going to scan them again — except the next year, when she pulled the same A1 foam boards out for the follow-up event and found the codes on them pointed at a dead agenda for last year’s conference.
This article is about the qr code for conference badge — and, more usefully, about the whole printed surface of an event: lanyards, signage, banners, sponsor collateral, and the post-event lead-capture pages those codes point to. It’s a companion to our broader guide to QR codes that don’t expire, applied to the one setting where the printed code and the thing it points at are almost guaranteed to drift apart. Heldqr is our product, and the section near the end says plainly where it fits and where it doesn’t.
The conference durability problem isn’t the badge — it’s the destination
Most QR durability problems are about the code dying — a free trial that deactivates after you’ve printed, so the printed pattern scans to nothing. That happens at conferences too. But conferences have a second, subtler problem that’s almost unique to events: the printed code is correct, and the destination is what goes stale.
Consider the lifecycle of a single piece of event collateral. A badge gets printed weeks ahead. During the event, the natural destination is the live agenda — rooms, times, “what’s on now.” Immediately after, what people want changes: the slides, the recordings, the speaker contacts, the survey. Six months later, the most useful destination is next year’s announcement. A year later, when you reuse the same banners and foam boards, you want them pointing at the new agenda.
The physical object doesn’t change — it’s printed. But the single most useful thing to point it at changes at least three times across that lifecycle:
- During the event: the live agenda, the floor map, the “now and next” view.
- The weeks after: recordings, slides, the feedback survey, lead-capture follow-up.
- The following year: next year’s registration page, or the new agenda if you’ve reused the collateral.
A static QR code — one with the destination URL baked directly into the pattern — can’t follow that lifecycle. It points where it pointed on print day, forever. A dynamic QR code — a short URL that redirects through a server you control — can. You change the destination from a dashboard and every printed badge, banner, and foam board updates at once, with no reprint. That updatability is the entire reason to use a dynamic code on event collateral.
Which means the durability question for a conference isn’t “will the code still scan?” It’s “will I still control where it points, two days and two months and two years from now?” And the moment that control runs through a vendor’s subscription, the answer is: only while you keep paying, and only while that vendor still exists.
Why subscription-deactivation is especially bad for events
The standard QR-SaaS business model is a subscription. You pay monthly, your dynamic codes resolve; you stop paying, and on most platforms the codes deactivate . For a business card or a restaurant menu, that’s a slow-burn problem — you notice eventually because you use the thing.
Events make deactivation land harder because of how event budgets work. A conference is a project, not an ongoing operation. The platform gets bought for that event, charged to that event’s budget, and the natural instinct afterward is to cancel — the conference is over, why keep paying? The events manager from the opening did exactly the sensible thing: the event ended, so the recurring charge ended too.
On a subscription-deactivation platform, cancelling is precisely what orphans the printed collateral. The badges and banners that survive the event — the ones you’d want to repoint at recordings, or reuse next year — go dark the moment you do the financially responsible thing and stop paying for an event that’s finished. The vendors on this model are quietly relying on organisers either keeping a subscription alive for collateral nobody’s using, or accepting that last year’s printed materials are now landfill. Neither is stated on the pricing page. The generic event-QR trial-and-subscription pattern — free trial to generate, monthly fee to keep codes live, deactivation on cancellation — is common enough across the category that you should assume it’s the default unless a vendor explicitly tells you otherwise .
There’s a worse version, too: the vendor that shuts down or pivots entirely. Then it doesn’t matter whether you kept paying — every code issued under that platform dies at once. For a one-off event that’s an annoyance; for an annual conference that reuses signage year over year, the printed assets you invested in have a hard expiry date set by someone else’s business decisions.
What a conference QR code should actually point at
Most organisers point the badge code at the wrong layer: directly at the agenda page, or the recordings page, or any single destination that’s only correct for one phase of the lifecycle. The badge is then right for a week and wrong forever after.
The better pattern is to point the code at a stable hub — one short destination per event that you control and repoint over time. “Antwerp Product Conf 2026,” a single landing page. During the event, the hub shows the agenda; after, recordings and the survey; the following year, it redirects to the new event or shows an archive notice with a link forward. The printed code never changes; the hub’s content does. It’s the same discipline a good wedding or memorial QR uses — point the durable printed thing at a layer you control, not at whatever third-party page happens to be useful this week.
This matters per surface:
- Badges and lanyards: point at the attendee hub — agenda during, recordings and survey after. Attendees who keep the lanyard get a working code indefinitely.
- Entrance and directional signage: point at the floor map or “now and next” during the event; repoint at a generic “thanks, see you next year” page after, so a reused foam board next year doesn’t show a dead agenda.
- Sponsor banners and booth collateral: each sponsor or booth gets its own code and hub. Sponsors often want scan analytics — give them a code you can hand them numbers for, and that they can repoint at their own follow-up.
- Post-event lead-capture pages: the form a booth visitor scans to “get the whitepaper” or “book a demo” — these genuinely change between events, so a repointable code is the difference between reusing booth hardware and reprinting it.
Point the code at a hub you own and the lifecycle problem dissolves into a few dashboard edits. Point it at a third-party page on a subscription you’ll cancel, and the lifecycle problem is baked into the print run.
The checklist for a conference QR code that survives the event
Run this before you send badges and banners to print, not after. It’s the pillar checklist adapted to events.
- Is the code dynamic, and do you control where it repoints? A static code can’t follow the agenda → recordings → next-year lifecycle. You need a dynamic redirect and the ability to edit the destination yourself, on demand.
- What happens when you cancel after the event? The event-specific killer. If the answer is “codes deactivate,” then cancelling — the natural post-event move — orphans every badge and banner. Find it in the TOS , not the marketing page.
- Is the free tier actually free, or a trial? “14-day free trial” near badges means the code can die mid-event or just after. A genuinely free tier with no expiry has nothing to lapse.
- Can you export your codes and mappings? For an annual event, you want your shortcode-to-URL mappings portable year over year, not held hostage by a platform you re-evaluate each cycle.
- Does the print quality scan reliably? Lanyard badges flap, foam boards get lit badly, banners get scanned from a distance. Test on the real stock, average phone, actual lighting. 20mm minimum on a badge, larger on signage, high error-correction.
- If the provider shuts down, what survives? The only honest answer is a published continuity plan, plus — for codes you genuinely need to outlive any vendor — a custom domain you own, so the code resolves through your domain rather than the vendor’s.
Fail more than one or two and the codes on next year’s reused banners will very likely point at a dead page, regardless of what the pricing page promised.
How to do this with Heldqr
Full details on the pricing page. Heldqr is our product; here’s where it fits an event and where it doesn’t.
For an organiser running a real conference, Pro (€9/month) or Business (€29/month) is the right tool. The features that matter for events are concentrated above the free tier:
- Custom shortcodes let each session, room, sponsor, and booth get its own clean, human-readable code rather than a random string — useful when you’re labelling forty things and want to tell them apart in a dashboard.
- 30-day country + device analytics on Pro (daily, with a one-year history on Business) tells you which sessions and which sponsor booths actually got scanned — the post-event number sponsors ask for, without cookies or IP tracking.
-
The custom domain (Pro and up) is the piece that solves the durability problem. Print your badges and banners against your own event domain. Under our published continuity plan, codes printed against a custom domain keep resolving even past a Heldqr shutdown — so an annual conference’s reused signage isn’t hostage to our survival. Bare
heldqr.ioshortcodes stop if we ever shut down; codes on your own domain are the printed-QR survival path. - Business (€29/month) adds three seats, bulk CSV import, and API access — which is how you generate one code per session for a 40-session agenda, or one per booth for a 60-sponsor floor, without doing it by hand. The bulk CSV is the realistic path for any event larger than a handful of codes.
The thread through all of it: on every Heldqr tier, cancelling after the event does not deactivate anything. You can run the conference on Pro, repoint the codes from agenda to recordings, drop to the free tier when the event’s over, and every printed code keeps resolving. The natural post-event “cancel the subscription” move doesn’t orphan your collateral, because the free tier is a real product, not a holding pen.
For a single speaker putting a QR on their own badge or slide, the free tier is enough. One code, no expiry, no scan limit, no credit card, no trial. Point it at your talk’s slides, your booking link, or your LinkedIn, and repoint it later when the slides move to a permanent archive. You don’t need Pro to keep one personal code alive.
What Heldqr is NOT the right answer for
Heldqr forwards a scan to a destination you control. It is not an event platform, and there’s a large, legitimate category of event tooling it doesn’t replace.
If you need a full event app — check-in and registration scanning at the door, attendee networking, in-app schedules, on-site badge printing, lead-retrieval hardware that sponsors rent to scan visitor badges and capture contact data — use a dedicated event platform. Cvent, Swapcard, Brella, Whova, and similar products do this . Lead-retrieval in particular is its own thing: a scanner (often rented hardware or a dedicated app) that reads an attendee’s badge and pushes their contact details into a sponsor’s CRM. Heldqr does none of that — no check-in, no attendee database, no lead capture. It just makes sure that when someone scans your printed badge or banner, they land where you currently want them to.
The honest hybrid is the same as everywhere else: use the event platform for what it’s good at during the event, and use a Heldqr redirect for the printed surfaces that need to outlive the event — the badge a sponsor keeps on their desk, the banner you’ll reuse next year, the recordings page the collateral should reach in month three. Point your durable printed codes at Heldqr; point your live, in-event experience at the platform built for it.
The Heldqr wedge for events is narrow and specific: a printed code on a badge, banner, or sign that still resolves after you’ve cancelled everything else and packed the foam boards away, and that you can repoint from agenda to recordings to next year without reprinting a thing. If that’s the problem, we’re the right answer. If you need the event app itself, the paragraph above tells you where to look.
In closing
Three takeaways.
One: the conference durability problem is rarely the code dying — it’s the destination drifting. The badge stays correct; the agenda it points at becomes last year’s. Point the code at a stable hub you control, and repoint the hub through the lifecycle, instead of pointing it at any single page that’s only right for one week.
Two: subscription-deactivation is uniquely bad for events because cancelling after the event is the financially sensible thing to do — and on most platforms, it’s also exactly what orphans your badges and banners. Check the cancellation behaviour in the TOS before you print, and prefer a model where stopping payment doesn’t break anything already in the room.
Three: for collateral that genuinely has to outlive any vendor — an annual conference’s reused signage, a sponsor’s desk keepsake — the only real durability is a custom domain you own plus a published continuity plan. A code on your own domain is the one that’s still resolving when both the event and the subscription are long over.
If Heldqr fits — bulk codes per session and booth, a custom domain so the printed collateral survives, analytics to hand sponsors — start with a code. If you only need one personal badge code, the free tier covers it. And if what you actually need is an event app with check-in and lead-retrieval, the section above points you elsewhere, honestly.
Written in June 2026. Heldqr is our product. If you have a specific conference or event-collateral scenario not covered here, or a vendor pattern worth adding to the public record, email us at hello@heldqr.com. For the full durability argument, start with the pillar guide.