QR Codes for Events: Tickets & Check-In

An event is the one place where everyone has a phone out, a reason to scan, and a moment of friction you can remove. That is the exact recipe a QR code is built for. A guest standing at a registration desk, a delegate deciding which talk to attend, a visitor leaning into your booth: each is a captive, high-intent scan waiting to happen. Trade-show codes regularly hit 35 to 50% scan rates during session breaks, far above the 1 to 3% you see on a billboard.

The problem is that most event QR codes are static, which means they do two damaging things. They encode a fixed destination that you can never change after printing, and they record nothing, so you finish the event with no idea how many people scanned the entrance sign versus the after-party map. You spent money on signage and learned nothing from it.

What a tracked event QR actually gives you

Point every code at a tracked short link instead of a raw URL and the entire event becomes measurable. You get four things a static code can never deliver:

• Scan counts per touchpoint so you know the entrance sign drove 1,400 scans and the sponsor table drove 30.
• Geo, device, and timestamp on every scan, which on event day reveals peak arrival times and which sessions filled up.
• An editable destination you can re-point as the event moves through its phases (more on that below).
• A clean, sparse code because a short link is far shorter than a full ticketing URL, so it scans from farther away on a crowded floor.

That distinction (static versus dynamic) decides whether your event QR is an asset or a liability, so we will keep coming back to it. If you want the deeper version of the argument, our guide to dynamic QR codes for print and digital lays out the mechanics, and the QR codes marketing strategy playbook covers placement and attribution across every surface.

The most useful way to plan event QR codes is to walk the attendee journey from the outside in and put a code at every point of friction. Each scan along that path becomes a tracked event in your dashboard, so you can see not just how many people came but how far down the funnel they got.

Pre-arrival: the ticket

The ticket QR is the attendee's first scan. Emailed or wallet-stored, it encodes a unique per-person link that your scanning app validates at the door. Because it is dynamic, you can disable a refunded ticket centrally without chasing the attendee to delete an email.

At the door: check-in

Staff scan the ticket code (or the attendee scans a desk code that opens a self-check-in form). Either way the scan is timestamped, so by 9:15am you know your arrival curve and can flex staffing in real time rather than guessing afterward (how scan tracking works).

On the floor: schedule and wayfinding

A single shared code on entrance signage opens the live schedule or a floor map. This is the highest-volume code at the whole event, and because it is dynamic you can update the schedule behind it all day without reprinting a thing.

In the room: session feedback

A code on each seat or slide opens a one-tap feedback form for that specific session. Per-session short links mean you can compare which talks people actually rated, not just which rooms looked full.

Ticketing is where QR codes earn their keep first, because they replace the slowest part of any event: a human reading a name off a list. A scan is sub-second and leaves an audit trail. But ticket codes carry real risk if you treat them like ordinary marketing codes, so the setup matters.

Unique codes, one scan each

Every ticket needs its own code tied to one attendee. The moment a ticket is scanned at the door, your system should mark it used so the same code cannot wave in three people. Shared or duplicated ticket codes are the single most common event-QR mistake, and they turn into a fraud problem the instant a code gets screenshotted and forwarded.

Where the validation actually happens

The phone camera only opens the link. The check is done by your ticketing backend or scanning app, which looks up the code and decides valid, used, or refunded. A dynamic short link helps here because the destination is server-controlled: a refunded ticket can be re-pointed to a "this ticket was cancelled" page without touching the attendee's saved code.

Offline fallback for bad venue WiFi

Conference halls are notorious dead zones. Plan for it: cache the valid-code list on each scanning device so check-in keeps working when the network drops, then sync the scans up when connectivity returns. Never design a door flow that fails the moment the venue WiFi does.

Once people are inside, QR codes shift from gatekeeping to engagement. The goal is to remove every "where do I find that?" moment by putting the answer one scan away. Done well, this also turns the venue into a measurement surface: you learn which sessions, sponsors, and amenities actually got attention.

Session feedback that people actually leave

Feedback rates collapse when you ask people to fill in a form after they get home. Put a code on the last slide and on each seat that opens a 30-second rating for that session, and completion jumps. Use a distinct short link per session so a low score is attributable to a specific talk, not a generic "the conference."

Live schedules and floor maps

A printed schedule is out of date the moment a speaker cancels. A QR on the program and on entrance signage that opens a hosted, editable schedule means you fix changes centrally and every attendee sees the current version. The same code can open an interactive floor map, which for a multi-room venue removes a huge amount of front-desk traffic.

Networking and content unlocks

Codes can open a networking directory, a speaker's slides, a shared photo album, or a post-event resource hub. Each is a chance to capture a scan and, if you want, an opt-in.

• Slides and handouts behind a session code, so nobody photographs the screen.
• Speaker bios and links from a code on the stage backdrop.
• Sponsor offers from booth codes, each on its own link for attribution.
• A post-event hub the same codes re-point to once the event ends.

The teams with the best event data are not running fancier software. They simply gave every sign, seat, and booth its own short link before the doors opened, so every scan had a name.

For sponsors and exhibitors, the booth QR is the whole point of buying the space. It replaces the fishbowl of business cards with a clean, opt-in, timestamped lead list. But a booth code only delivers if it is built for capture, not just for "scan to learn more."

Capture the lead, then deliver value

The strongest booth flow is a quick gated form: scan, drop an email to get the demo recording or the discount, and you have a qualified, consented lead. Point the code at a branded short link that opens that form, and tag it with the booth and event so the lead source is unambiguous in your CRM.

One link per booth, per day, per offer

Sponsors love attribution, so give it to them. A unique short link per booth lets each exhibitor see their own scan count. Splitting by day or by offer (a giveaway link versus a demo-booking link) shows which incentive pulled, which is exactly the report a sponsor needs to renew next year.

Re-point the booth code after the event

This is where dynamic codes shine for sponsors. During the event the code opens the lead form. The day after, you re-point the same printed code to a "thanks for visiting, book a call" page. The sponsor's printed standee keeps working for weeks instead of dying when the hall clears.

This is the single most valuable trick in event QR codes, and it is impossible with static codes. An event has phases (pre-event promotion, the live day, the post-event follow-up) and your printed materials live across all of them. With a dynamic code you print once and re-point the destination as the event moves through its life.

The three-phase pattern

1. Pre-event: the code on your save-the-date, social posts, and early signage opens the registration or ticket page.
2. Live: on event day you re-point the same code to the schedule, check-in, or a live-updates feed.
3. Post-event: afterward the code opens session recordings, a feedback survey, and the signup for next year.

Every one of those switches happens in your dashboard in seconds, and every printed asset that already carries the code instantly follows along. A static code would have forced three separate print runs and three separate codes that all compete for the same square inch of your poster.

Annual events compound the benefit

If you run the same event yearly, a single evergreen code on a reusable banner can carry across editions: this year's registration, then next year's. You build scan history on one link over time, which is far more useful than a fresh dead code every year. The mechanics are identical to an expiring link or a link rotator: you own the redirect, so you control what happens at the destination.

The reason to do all of this is the data. When every code is a unique tracked short link, your event stops being a black box and becomes a funnel you can read line by line. Here is the stack that turns scans into decisions.

One short link per touchpoint

The biggest mistake is reusing one code everywhere. If the entrance sign, the program, and the after-party map all open flyn.to/event, you get a single number and no idea which surface worked. Split them: one link per sign, per session, per booth. The marketing strategy playbook covers this discipline in depth.

What every scan records

• Timestamp to the second, so you can chart arrival peaks and which sessions filled.
• Approximate location, which reveals scans from outside the venue (people who screenshotted and shared a code).
• Device and OS, useful for the next time you design a check-in flow.
• Total count per link, the headline number each sponsor and stakeholder wants.

Push event scans into your other tools

Click events can flow into your CRM or analytics via webhooks, so a booth scan from a named prospect becomes a real-time signal for the sales rep. The full setup is in our guide to how to track clicks on a link, and the detailed geo and device breakdowns live on a Pro plan.

A code that does not scan is worse than no code, because every failed scan is an attendee blaming your event for a broken experience in front of their peers. Event environments are uniquely hostile to QR codes: lanyards twist, signage gets viewed from across a hall, and lighting is unpredictable. Placement and sizing are not afterthoughts.

Badge and lanyard codes

A badge code is read up close but at an awkward angle while it dangles. Keep it at least 2cm by 2cm, print it flat (a code on a curved or folded badge edge fails), and leave the quiet zone clear of the attendee's name and the event logo. Test it on a real printed badge, not just on screen.

Signage and the 10:1 rule

For any code viewed from a distance, size it to at least one tenth of the viewing distance (the QR code size guide has exact sizes by distance). A code on entrance signage seen from 2 metres needs to be roughly 20cm wide. A stage-backdrop code seen from 5 metres needs to be 50cm. Undersized signage codes are the number-one reason a high-traffic event code gets few scans.

• Badge / handout (arm's length): 2 to 4cm minimum.
• Table tent / program: 3 to 5cm.
• Entrance signage (around 2m): 20cm.
• Stage backdrop (around 5m): 50cm or larger.

Contrast, quiet zone, and a real CTA

Keep dark modules on a light background (near-black or your brand #14532D green on white), leave a four-module quiet zone, and never reverse the colours on a poster you cannot test on every phone. Add a CTA with a payoff: "Scan to check in," "Scan for the schedule," "Scan to rate this talk." A code with a real CTA outscans a bare "scan me" by a wide margin. If a code refuses to read, our walkthrough on why a QR code is not scanning diagnoses it in order.

Most event-QR failures are not exotic. They are the same handful of avoidable mistakes, and every one has a clean fix. Run this list before your codes go to print.

Static codes you cannot change

A schedule moves, a venue changes, a speaker cancels, and your printed code is now wrong forever. The fix is to make every code dynamic so the destination is editable after printing. This one decision prevents most reprint emergencies.

One code for everything

Reusing a single code across all surfaces destroys attribution. Give each touchpoint its own short link so you can compare them. It costs nothing extra and turns a useless aggregate into a real funnel.

Never auditing before print

Printing a thousand badges before checking the destination is how you discover a dead link on the floor instead of on your desk. Run every code through the QR Destination Audit first: it resolves the link, checks HTTPS, counts redirects, and flags mobile-broken landers. After the event, decode a sampled printed code with the QR Code Reader to confirm it still points where you think.

Get these right and your event runs on codes that are fast, measurable, and forgiving. Build your first one free in the QR Code Generator, browse the rest of the kit in free tools, or create a Flyn account to make every event code trackable and re-pointable from day one.