QR codes for tradeshow booths — capturing leads on the floor

A tradeshow booth is a one-week sales channel that costs as much as a quarter of marketing payroll. Booth space, freight, travel, hotels, the print run, the headcount on the floor — a mid-tier expo position in Hannover or Las Vegas runs $40,000 before anyone walks up. The same booth, run twice in a year, will produce somewhere between 200 and 1,200 scanned leads if the QR layer is set up correctly, and somewhere between zero and "we had a fishbowl of business cards" if it isn't.

The gap between those two outcomes is mostly QR codes for tradeshow booths — specifically, per-day codes, per-rep codes, and the lead-capture handoff to your CRM. None of it is hard. All of it gets skipped, because the team is busy pretending the badge scanners the show rented to them are doing the work. They aren't. Show-rented scanners give you a name and an email and that's it. Yours can give you the rep, the day, the booth zone, the conversation topic, and a destination tuned to whatever the prospect was actually asking about.

This is how to set that up before the truck leaves for the venue.

Per-day QR codes — why one code per booth is the wrong default#

The most common tradeshow QR setup is one code printed on a back-wall banner that points at the company homepage. Six days of show, one code, no segmentation. By Friday night the marketing manager has a number for "scans this week" and no idea whether Tuesday's foot traffic was different from Thursday's, whether the morning rush converted better than afternoon, or whether the panel-talk crowd was qualitatively different from the wandering-attendees crowd.

A per-day QR code fixes this with one decision: print six codes instead of one, each pointing at the same destination but routed through a different short link. Day 1 → yourbrand.com/expo-mon, Day 2 → yourbrand.com/expo-tue, and so on. The destination is identical. The analytics are not.

What this gets you, concretely, after the show:

• Day-by-day conversion rate. Tuesday's 142 scans turned into 31 booked demos. Wednesday's 198 scans turned into 12. Something about the audience or the messaging changed; you can investigate because the data exists.
• Hour-by-hour heat map. Most booths are quietest at 11am and 4pm and busiest right after the morning keynote. The data tells you when to assign your best rep to the front of the booth.
• Drop-off detection. If Friday's scan-to-form conversion craters even though the scan count is healthy, the lead-capture page is probably broken or the form provider is rate-limiting. You find out Friday night, not three weeks later when the spreadsheet finally gets cleaned.

The cost of switching from one code to six is one click in the dashboard per day and one extra column in the print file. The upside is the difference between "we got leads" and a report you can pitch the next show against. The mechanics of routing scans through a short link belong to the same family as the device-targeted short link pattern — the only difference is what you're slicing the audience by.

Per-rep QR codes — attribution from the lanyard up#

Per-day codes split the week. Per-rep codes split the team. Each person working the booth gets their own QR code — usually printed at credit-card size on the back of their lanyard, or on a small acrylic tile they can hand a prospect during the conversation.

The rep-coded QR resolves to the same destination as the booth-wall QR, but the URL carries the rep's identifier in a UTM parameter or a slug. The lead-capture page reads it, attaches it to the form submission, and the CRM records "this lead came from Anna at 11:14am at IBC". The full UTM mechanics are in UTM parameters that actually matter for short links — for tradeshow use, the only two you genuinely need are utm_source=tradeshow-name and utm_content=rep-anna. Three days after the show, you can rank reps by qualified leads, not just by scan count.

A few rules that keep per-rep codes from going sideways:

One destination, one slug per rep. Don't make new codes mid-show because the booth got busy. The slug is part of the rep's identity for the week.

Lanyards over business cards. A printed business card with a QR works fine, but reps run out by Wednesday and stop handing them out. A lanyard or laminated badge stays on for the whole show.

Track everyone, including managers. It is genuinely useful to know that the founder generated 80 of the booked demos on Tuesday and the regional manager generated three. The data is uncomfortable; the spending decisions it informs are valuable.

Include the rep on the page. When the QR resolves, the landing page can show "Continuing your conversation with Anna" with a thumbnail. It feels like the conversation is still warm, and it tells the prospect's brain that this isn't a generic landing — it's the next step in the booth visit.

The rep slugs themselves should be short, memorable, and predictable: mon-anna, mon-luis, tue-anna. When a prospect asks "can I send this to my CTO?", a short slug travels well via SMS. Anything cryptic feels like an affiliate hack — covered in the broader vanity short URL strategies post for the rest of the naming logic.

What goes on the landing page — the four-second test#

Tradeshow scans are different from normal QR scans in one specific way: the prospect is standing three feet from your booth holding their phone in front of their face. They have four seconds before the rep starts talking again or the next attendee steps up. Whatever lands has to make sense in those four seconds.

Most tradeshow landing pages fail this test because they were built to be standalone pieces of marketing — a hero, a value proposition, a feature list, three testimonials, a footer with a contact form at the bottom. By the time anyone scrolls, the conversation is over.

The landing pages that work are roughly the same shape every time:

A line at the top that confirms the page belongs to this show ("From our IBC 2026 booth"). The prospect needs a quarter-second of recognition that they're in the right place — without it, the scan feels like it might have grabbed the wrong code.

One sentence about what the company actually does. Not a tagline. Plain language, the same words the rep would say if asked at the bar. "We help broadcasters cut transcoding bills by 60%". That's the whole positioning statement.

A primary action that matches the show's purpose. For most B2B booths, that's "Book a 15-minute demo" with a calendar widget embedded inline. Not a contact form. The prospect's energy at the booth is "I'd like to talk to you again later" — a calendar slot captures it before it cools.

A secondary action for the prospects who aren't ready to book. Usually "Download the deck" or "Get the case study" — something useful for the plane ride home, something that wants an email. Booths whose product is a phone-side app pair this with a "scan to install" tile beside the demo CTA — the App Store QR code generator writes a single code that routes iPhone scanners to the App Store and Android scanners to Play, which is the right shape for the booth audience that just wants to try the thing on the train home.

What the page should not have: a newsletter signup as the only call to action, a product feature comparison table, an "about us" section, an autoplaying video, or a 20-field demo-request form. Each of these has its place on the main site. None of them have a place on a page someone reached by holding their phone up at your booth.

The CRM handoff — the part everyone gets wrong#

A scan that doesn't end up in the CRM as an attributable lead is half a scan. The whole reason for splitting codes by day and rep is so that the qualified follow-up next Tuesday says "Hi Marco, great chatting at IBC on Wednesday afternoon — here's the spec sheet you asked about" instead of "Dear valued contact, here is our marketing email cadence."

The path looks like this, end to end:

The QR code resolves to a short link. The short link carries the day and rep parameters in the URL query string. The landing page reads those parameters before anything else on the page renders, stores them in a hidden form field, and pre-populates a data-source attribute on every button on the page. When the prospect fills the form or books a calendar slot, the parameters travel with the submission into the CRM as custom fields: tradeshow_event, tradeshow_day, tradeshow_rep, tradeshow_timestamp.

Most setups fail at one of three points. First, the parameters don't survive a redirect. If the short link bounces through one tracker that strips query strings, every lead lands without attribution. Test the full chain with the actual short link, not a localhost mock. The post on tracking links in email covers the same parameter-survival discipline for a different surface.

Second, the form doesn't carry the hidden fields. Many embedded form widgets (HubSpot, Marketo, Pipedrive's native form) need explicit configuration to accept custom URL parameters. The default behaviour is to drop them silently. Set them up before the show and submit a test form from your phone to confirm the data lands.

Third, the CRM doesn't route by rep. The lead gets attributed correctly, but it lands in a generic "marketing-qualified" inbox instead of going straight to Anna's queue. A two-line workflow in any modern CRM — "if tradeshow_rep exists, assign to the rep with that ID" — closes this gap. Without it, your reps spend Monday morning fighting over who gets to follow up with whom.

The UX wins that double scan rates#

The booth-side mistakes that lose half the scans are smaller than people think. Five fixes that consistently move the number.

The CTA copy on the QR frame. A QR sitting alone on a poster gets fewer scans than the same QR inside a frame with three words above it. "Scan for the demo" is fine. "Scan to skip the line" is better. "Scan for free coffee at booth 4C" is best, if that's true. The frame creates the affordance the QR doesn't have on its own.

The print size at booth distance. A QR printed at 4cm is fine for handheld scanning. A QR printed at 4cm on a back-wall banner six metres away from the aisle is invisible to phones. The rule of thumb is one-tenth of the maximum scan distance — covered in detail in QR codes for outdoor advertising, and the same physics apply on a tradeshow floor. Back-wall QRs need to be at least 30cm on a side; lanyard-level QRs can be much smaller.

The position relative to eye line. Booth QRs at floor level or above 2.1m don't get scanned. Eye line for a standing adult is roughly 1.5m to 1.7m; that's the sweet zone. Booth shells from the show provider often default to "logo at top, QR at bottom" — a 30-second decision before installation can fix it.

The lighting on the code. Booth halogen spots and LED tracks at 4000K colour temperature do strange things to printed contrast. Coloured QRs on coloured backgrounds that scanned fine in the studio sometimes don't scan at the booth. Print one full-size proof and test it under booth-spec lighting before the truck leaves the warehouse.

The QR's destination preview. When a phone scans a QR, modern cameras show the destination URL in a small banner before opening. A QR pointing at bit.ly/3xK7p1 reads as suspect to a senior decision-maker. A QR pointing at yourbrand.com/expo-wed reads as legitimate. The cost of the custom domain is roughly nothing relative to the booth budget; the impact on scan-through rate is real. The branded short links and the click you lose post quantifies the gap with the source data.

A booth QR pointing at a generic shortener is a $200 print mistake on a $40,000 floor. The branded domain is the cheapest way to claw back the trust you bought with the booth in the first place.

A pre-show checklist that catches the failures before they ship#

Bringing it back from the show — the 48-hour follow-up window#

The lead's interest in your booth decays fast. Day one after the show, recall is sharp. Day three, the prospect has been to four other booths and a partner dinner and is back in their own inbox triaging. Day seven, you're a faint memory and an email subject line they don't recognise.

The 48-hour follow-up rule is well-known in trade-show literature and consistently ignored in practice. Reps come back from the show exhausted, the marketing team is processing the badge-scan export from the show app, and Monday becomes Wednesday becomes "let's do a clean push next week". By then the lead has gone cold.

The version that works: every rep has a personal follow-up template ready before the show starts. The CRM, segmented by tradeshow_rep and tradeshow_day, hands the rep their list on Monday morning with the conversation context attached. The follow-up note references the specific session ("you mentioned your team is migrating off Snowflake — here's the case study we showed at the booth on Wednesday morning"). Reply rates are usually 3-4× the equivalent generic post-show email.

Per-rep QR codes are what make this work. Without them, the rep doesn't know who they talked to. With them, the conversation context is in the CRM record by Sunday night.

The supporting infrastructure — the link analytics dashboard, the rep dashboard, the per-day breakdowns — is described in real-time link analytics, and the platform-side mechanics live in the QR-codes platform docs. For the broader case on why event-style codes earn their keep over the static "company-homepage QR" default, the calendar event QR follow-up pattern is directly analogous — different format, same structural insight that the QR is a tool for a moment, not a sign on a wall. The booth itself is one slice of a wider event operation; the whole-event QR layer covering registration, schedule, and sponsor attribution is the version of this argument extended to the registration desk, the schedule signage, and the after-event sponsor report.

Hardware and printing — the boring details that decide the show#

The QR system on the dashboard side is half the work. The print side is the half that costs you scans if you cut corners.

Print stock. Matte vinyl for booth walls. Glossy laminates on a tradeshow floor with overhead halogen create glare patches that wipe out modules at common scan angles. The outdoor-advertising post on QR-friendly surfaces covers the broader rule; in the booth context, "matte everything" is the safe default.

Print resolution. 300 DPI minimum on the actual booth print, not just the design file. Some print providers down-rez files to 150 DPI for "cost savings" without flagging it. Small modules become muddy and stop scanning. Ask the printer to confirm the print resolution before approving the run.

Error correction level. Level Q for indoor booth use. Level H if you're putting the QR on a piece of merchandise that will travel home with the prospect and might get scuffed — covered in QR error correction levels.

Acrylic vs. paper tile. If you want a per-conversation tile the rep can put on a small counter and gesture at, etched acrylic with a black-fill inlay outperforms a paper tile in every way except cost. It survives the show, the rep can hand it over to the prospect to scan and hand it back, and it photographs better in event-photographer shots.

Backup batch. Print 20% more lanyard QRs than you have reps. Some will be lost in transit, some will tear on day one, some will end up in the hands of new contractors hired on Tuesday to cover the rush. Spares cost nothing relative to the cost of having a rep without a code on Thursday morning.

For a quick spin-up of a new code mid-show — a partner walks past, you want to give them a personalised slug — the free QR code generator and the short-link generator on the marketing site handle one-offs fast enough to do them from a phone at the booth. For the per-rep production batch, the dashboard is faster because it batches the design template across every code in one pass.

What to measure after the show#

The post-show debrief is where the per-day and per-rep work pays back. Five numbers worth pulling out of the dashboard:

Total qualified leads, segmented by day. Not raw scans — booked-demo and download counts. The conversation about whether to come back next year happens with this number on the table.

Cost per qualified lead. Total booth cost divided by qualified leads. A useful baseline; the better question is "cost per closed deal six months later", which only the CRM can answer.

Top-performer concentration. What share of the qualified leads came from your top two reps? If it's over 60%, you have a training issue with the rest of the team, not a booth issue.

Best-converting time window. Hour-by-hour conversion from scan to booked demo. Use it to staff next year's booth differently.

Decay curve. Scans by day-after-show. Most tradeshow scans happen on the day. Some happen in the week after, when prospects clean up their phone gallery and revisit screenshots. A long decay tail suggests the printed assets traveled home with the audience and are still working — usually a sign of a good post-show campaign.

The numbers feed forward. The shape of next year's booth — staffing, layout, CTA copy, which day to launch the big announcement — comes out of this data, not out of "we felt good on Wednesday".