For events
QR codes that know when your event starts
Print early, decide later. Time-windowed links, capped and one-time access, and check-in passes that rotate every 30 seconds — all on your own domain, with cookieless analytics.
What usually goes wrong
- A QR goes to print weeks early — and the destination still isn’t final.
- Last year’s poster still works, sending people to a dead event page.
- One VIP link gets screenshotted into a group chat and 300 people use it.
- No idea how many people actually scanned the poster versus the flyer.
What you get
Links that switch themselves on
Set an active-from and active-until time and the link only works inside it. Before and after, scans land on a fallback URL you choose — or a branded page explaining the event hasn’t started.
Entered in the venue’s timezone
Pick the event’s timezone and enter the window in local wall-clock time. Daylight saving is handled, so a 19:00 door time means 19:00 at the door.
Capped and one-time links
Limit a link to N scans for capped access, or exactly one for a single-use pass. Link checkers and chat unfurls don’t burn a scan, so a one-time link survives being previewed.
Rotating check-in passes
The holder’s QR changes every 30 seconds, computed on their device. A screenshot is worthless within the minute, and each code can only be redeemed once. No app to install on either side.
One-click event pack
One form creates the whole set — check-in pass, event page, venue map, schedule — sharing a single time window and an event tag, so the whole event is one row in your dashboard.
Retarget without reprinting
The QR points at your short link, not the destination. Change where it goes the morning of the event and every poster already printed follows along.
How it runs
- 1
Create the event pack
Name the event, set the window and the timezone, and add the links you need. Every link comes out on your own domain.
- 2
Print the QRs
Download each QR and send it to print. Destinations stay editable right up to the door — and after it.
- 3
Run the door
Scan holders’ rotating passes to check them in. Watch check-ins and scan usage live from the dashboard.
- 4
Report afterwards
Export check-ins as CSV and see scans over time by placement — cookieless, so there’s no consent banner in the way.
Why the pass can’t be shared
A normal ticket QR is a fixed image, so forwarding it forwards the ticket. An Einblik check-in pass shows a code derived from the current time, recomputed on the holder’s phone every 30 seconds. A screenshot expires before it reaches the group chat, and each code can only be checked in once — so even a live relay gets one person through, not fifty. The secret never leaves the holder’s browser: it travels in the part of the link that browsers don’t send to servers.
Run your next event on links you control
Start free, then add scheduling and check-in when you need them.