Attendee badges
One scan for the profile, the app download, or today’s help desk note.
QR codes for conference badges
The badge prints early. The session link can wait.
Badge files go to the printer weeks out. The agenda does not. Put a dynamic code on the badge so you can point it at check-in, then the app, then the survey.
Create a QR code
Paste the conferences URL. Download asks for email. You can change the destination after you print.
Where it goes
One scan for the profile, the app download, or today’s help desk note.
Exhibitors get a tracked code. You see which booth was busy.
A door sign can open this hour’s form. Next hour, a different form, same sign art if you want.
Lanyard hardware can keep last year’s code if you retarget it. Most teams print a new badge and keep the same short-link style.
Why dynamic
Dynamic codes close that gap.
A code per booth is a number you can send on Monday.
Point leftover signage at the recap or ticket page for next year.
How to
01
Check-in, profile, or the conference app page.
02
Badge, booth, and session codes stay easier to report.
03
High contrast. Do not shrink it into the logo.
04
Help-desk hours and room changes go in the dashboard.
Only if that data will not change. A URL you control is safer for agendas and support.
Yes. Create one per booth. That is how you compare traffic.
If they used a dynamic short link, edit it. If they encoded a raw URL, you reprint.