Back to Blog
Case StudiesFeatured

Six QR Codes at a Michigan Arcade: What 179 Scans Showed Us

Real scan numbers from GottaGacha, an esports arcade in Warren, Michigan, over ten weeks: which codes got used, which did not, and what we would do differently.

S
Scantrail Team
November 11, 20264 min read

A note before the numbers: GottaGacha is run by the same people who build Scantrail. This is our own venue using our own product, not an independent customer review, and nobody was paid for it. We are publishing it because the numbers are real and we would rather show a small true example than a large invented one.

The setup

GottaGacha is an esports gaming clawcade in Warren, Michigan. Between September 1 and November 11, 2026 the team made six Scantrail codes for things it was already promoting in the venue: a workshop ticket page, a Halloween event page, the venue website, the Discord server, the mobile apps, and an order form.

Those six codes recorded 179 scans in that time. That count includes a handful of our own test scans, and a scan is not the same as a unique person, so read the figures as activity rather than headcount.

What each code did

  • Order form: 82 scans, 81 of them on a single day
  • Halloween event page: 44 scans spread over 18 different days
  • Discord server: 31 scans
  • Workshop tickets: 11 scans
  • Venue website: 6 scans
  • Mobile apps: 5 scans

Lesson 1: a code that asks for one thing beats a code that asks for nothing in particular

The website, Discord, and mobile app codes were made on the same day, in the same white-on-black style. Discord got 31 scans. The website got 6 and the apps got 5.

The difference was the ask. "Join the Discord" is a clear next step with a reason behind it. "Visit our website" is not. If a code does not answer "why would I scan this right now?", most people walk past it.

Lesson 2: event codes work for weeks, not just on the night

The Halloween code went up on October 10 and was scanned on 18 separate days through November 1. Until the last day it was one to four scans a day. That slow trickle is people checking details and deciding whether to come.

Put the event code out as early as the poster. People scan while they are still deciding, well before the day itself.

Lesson 3: action codes spike, so test the destination on a phone first

November 1 was the busiest day by a wide margin: 108 scans across four codes, with the order form alone taking 81. A code like that does nothing for days and then takes almost all of its traffic at once.

Of all 179 scans, 173 came from phones: 106 scans were on iOS and 69 on Android. If the page behind the code is slow or awkward on a phone, the busiest hour is exactly when it fails. Scan your own code on an iPhone and an Android phone before anything goes to print.

What did not work

The mobile apps code got five scans in two and a half weeks. We have not changed it yet. The likely fix is the same as lesson 1: say what the app gets you, next to the code, instead of only naming it.

What we would do differently

  • Print the reason to scan next to every code, in five words or fewer
  • Make one code per placement instead of reusing one everywhere, so the numbers show which spot is working
  • Put event codes out at least three weeks ahead
  • Check the scan count the morning after a busy day, while the context is still fresh

Try it on something you are already printing

Every code here was made on a normal Scantrail account, and the scan counts come from the same dashboard every account gets. The Free plan includes one editable code with scan analytics, and you do not need a card to start.

case studyeventssmall businessQR codes

Ready to create your own QR codes?

Put what you've learned into practice with Scantrail. Create beautiful branded QR codes with built-in analytics.

Start Free Today