How to create a QR code for events

An event QR code can open registration, a live schedule, a venue map, session resources or a follow-up form. It is not a ticketing system. One shared link cannot validate identity, capacity or single use. For access control, use the unique QR code issued by your ticketing platform and its check-in app.

Choose the right QR code for each stage

Create an event QR code in five steps

1. 1

   Define one task

   Decide whether the code is for registration, the schedule, directions, resources or feedback. If people need several actions, use a clear event hub or separate labelled codes.

2. 2

   Prepare the mobile destination

   Publish the page or form and open it in a private window. Check the date, time zone, address, price, capacity, permissions and completion screen without relying on your own login.

3. 3

   Create one URL per placement

   Separate posters, badges, stage screens, tables and email when you need comparisons. Add consistent UTM values for Analytics and keep a placement-to-URL register.

4. 4

   Generate, save and download

   Paste the URL into the generator, claim the link in your account before distribution and download the SVG for print. Keep a readable short URL as a fallback.

5. 5

   Test as an attendee and organiser

   Scan on iPhone and Android over mobile data, then complete the registration or open the resource. For entry, separately rehearse the unique ticket, any provider-supported offline mode and the manual backup process.

One event hub or several codes

A hub works when the same person needs the schedule, map and notices together. Separate codes work when each touchpoint has one unambiguous action: “Register”, “Open the programme”, “Download the slides” or “Give feedback”. Never place two unlabelled codes side by side.

Print and place the code for real conditions

• Preserve a clear four-module quiet zone around the pattern; keep text, logos and borders outside it.
• Use dark modules on a light background and avoid glare, folds or curved surfaces that distort the code.
• Size for distance, density and material; a badge and a screen at the back of a room need different tests.
• Place an exact prompt beside the code and state whether the destination needs a connection or account.
• Test the exported SVG and then the final poster, badge or screen from the intended scanning position.
• Provide a short URL or manual path for accessibility, a flat battery or a camera failure.

Measure interest, registration and attendance separately

1. 1

   Record the baseline

   Log the URL, placement, asset, prompt, active dates and intended outcome before distribution.

2. 2

   Count opens

   taap.at records requests during the redirect. One person may open several times, and an open does not prove that the destination loaded.

3. 3

   Count sessions and submissions

   Analytics may receive UTM values after page load; the form or ticketing platform records submissions and purchases. Consent, blockers and abandonment create differences.

4. 4

   Count attendance in the entry system

   Use valid check-ins from unique tickets. Do not infer attendance from promotional QR opens.

5. 5

   Evaluate after 14 and 28 days

   Compare placements over equivalent windows. Opens without registrations suggest the offer, price or form; few opens suggest visibility, size, position or wording.

Pre-opening checklist

• Every destination opens without unexpected permissions and shows the correct date, time and zone.
• Every QR code has a label and a fallback URL.
• Registration, payment or feedback was completed end to end on mobile.
• The physical proof works at the actual distance and lighting.
• Staff can distinguish promotional, information and individual ticket QR codes.
• A manual process exists if the network or scanner fails.
• Opens, registrations, purchases and check-ins will be reported as separate metrics.