🎟️ Events
How to create a QR code for events, registration and access
If you need event access with a QR code, separate three assets: the promotional QR for registration or schedule, the individual ticket issued by the ticketing platform, and the check-in scan that validates attendance. Create a dedicated URL for every poster, email, badge or screen, download the SVG, test the full journey over mobile data, and measure opens, registrations, tickets and attendance separately.
7 min readUpdated
On this page
- 01Choose the right QR code for each stage
- 02Event access with QR codes: registration, ticket and check-in
- 03QR codes for in-person sign-in and lead capture
- 04Create an event QR code in five steps
- 05One event hub or several codes
- 06Print and place the code for real conditions
- 07Measure interest, registration and attendance separately
- 08Pre-opening checklist
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
| Stage | Destination | Outcome to measure |
|---|---|---|
| Before the event | Registration, ticket sale or waitlist | Submitted registration or confirmed purchase |
| Confirmation | Schedule, calendar, directions and requirements | Saved event or viewed information |
| Entry | Individual ticket from the access system | Valid check-in, not a link open |
| During | Programme, map, resources or contact page | Opened session or resource |
| After | Feedback, certificate, recording or next edition | Response, download or registration |
An information QR code is not a ticket
taap.at creates a QR code for a URL and can count redirect opens. It does not issue unique tickets or mark one as used. If you must validate entry, let the ticketing platform create a different code for every attendee and scan it with its official tool.
Event access with QR codes: registration, ticket and check-in
To capture event-access demand without mixing metrics, use a measured link for promotion and registration, but leave door validation to the ticketing system. Ticketing platforms can generate a unique QR code for each ticket, and organizer apps can scan it or check attendees in manually; if a ticket has already been used or is not valid, the system should show that during check-in.
| Need | Recommended QR | What to report |
|---|---|---|
| Promote the event | Measured link to the landing page or ticketing page | Opens, sessions and registration clicks |
| Register attendees | Form or checkout with placement-level UTM | Confirmed registrations or purchases |
| Control entry at the door | Individual ticket from the provider | Valid, duplicate or rejected check-in |
| Backup without scanning | Manual list or attendee-name search | Documented manual entry |
QR codes for in-person sign-in and lead capture
At an open house, fair, showroom or live demo, the QR code does not need to validate entry: its job is to open a short, labelled form and collect permission-based contact details. Keep a paper backup, but use a different link for each property, booth or table so every lead keeps its source.
| Context | Recommended destination | Metric that matters |
|---|---|---|
| Open house or viewing | Form with property, date and source prefilled | Valid contact and follow-up, not only an open |
| Fair or booth | Short landing page with a benefit and form | Accepted lead or booked meeting |
| Demo, talk or workshop | Registration, materials or follow-up survey | Completed registration, attendance or response |
| No-signal backup | Paper form or manual capture | Documented later entry |
Ask only for the data you need
Name, phone or email and one intent question are usually enough for first follow-up. Fields such as address, budget or financing status can reduce completion; keep them optional unless they are required to fulfil the promise.
Create an event QR code in five steps
- 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
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
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
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
Test as an attendee and organiser
Scan on iPhone and Android over mobile data, then complete the registration or open the resource. For access, separately rehearse the unique ticket, duplicate or invalid-ticket warning, any provider-supported offline mode and the manual backup process.
Save the link before publishing
An anonymous taap.at creation lasts 30 days and records no analytics. Free removes automatic expiry, shows seven days of data and supports 100 monthly opens before an ad-supported interstitial; it cannot edit the destination. Editing requires Basic or Premium.
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.
| Setup | Advantage | Risk |
|---|---|---|
| One QR to an event hub | Update content and gather resources | Adds a screen before the primary action |
| One QR per task | Clearer promise and measurement | More links and assets to control |
| One QR per placement | Compares channels, rooms or signs | Fragments data without a version register |
| Unique ticket per attendee | Supports validation in the correct system | Must not be replaced by a shared promotional QR |
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
Record the baseline
Log the URL, placement, asset, prompt, active dates and intended outcome before distribution.
- 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
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
Count attendance in the entry system
Use valid check-ins from unique tickets. Do not infer attendance from promotional QR opens.
- 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.
Frequently asked questions
How do I create a QR code for an event?
Publish the exact registration, schedule or resource page, create a dedicated URL, generate the code, download the SVG and test the complete journey on another phone before distribution.
Can the same QR code handle registration and entry?
Usually not. A registration code can be shared; secure entry requires a unique ticket per attendee that the access system validates, rejects if already used and backs up manually if scanning fails.
Can I change the schedule after printing?
Yes if you update content at the same page or point the code to an editable link. On taap.at, changing the destination requires Basic or Premium.
How do I know which poster drove registrations?
Use a separate link and UTM values per poster, record its placement, then compare opens, sessions and confirmed registrations over the same window.
How large should an event QR code be?
There is no universal size. Modules, distance, material, print, camera and light all matter. Keep four clear modules, use the available space and test the final asset.
Does an open equal an attendee?
No. An open is a request to the link; registration belongs in the form or ticketing system, and attendance requires a valid check-in.
Make it yours and track every click
Create a free account so your links do not expire and you can measure country, device, and source.