QR codes for event and conference apps

An event app is only useful if people install it before the first session. You get a few moments of attention — at registration, on the badge, on the first slide — and one code has to work for every phone in the room.

The moments that count

Why one code, not two

Two codes next to each other — one for iPhone, one for Android — make every attendee stop and choose, and some scan the wrong one. A single code that routes by device is simpler to design and impossible to get wrong. Huawei phones go to AppGallery, and attendees on a laptop get your event website.

Before, during and after

  1. Before: while the app is in review, point the link’s iPhone destination at your TestFlight public link or at your event website. Print the code. When the app goes live, change the destination — the printed badges keep working.
  2. During: watch scans by day. A spike after the keynote and nothing on day two tells you where to put the next reminder.
  3. After: point the link at next year’s registration page or a recording, or pause it. A paused link shows a clear page instead of an error.

Knowing what worked

Give the badge, the posters and the slide their own links and codes, and compare scans afterwards. With store campaign attribution on, where your plan includes it, App Store Connect and Google Play Console show installs per link. Organisers who run several events a year can keep one team per event or per client.

Practical notes

SetLinks does not check people in, sell tickets or run the agenda. It gets them from a printed code to the right store, and shows you how many did.

Make your app link

One link and a QR code for every store. Free to start, no card required.

Create a link