QR Code Scan Time of Day: How to See Peak Hours

Nookesh Karri

How Do I See What Time of Day People Scan My QR Code?

To see QR code scan time of day, use a dynamic code with an hourly report or GA4's Hour dimension, then check which time zone the hours are in.

Nookesh Karri Nov 10, 2026 · 9 min read

You see what time of day people scan your QR code by using a dynamic QR code that records each scan, then opening its hourly or time-of-day report. If your code links to your own site with UTM tags, Google Analytics 4 can show the same thing with its Hour dimension. Before you act on a peak, check which time zone the hours are shown in, because that is where most QR code scan time of day reports go wrong.

Why you need a dynamic code to see scan times

A QR code only has scan times if something records the scan, and a printed static code records nothing. A static code holds the final link in the pattern itself, so the phone goes straight to the destination with no stop in between. You can’t add timestamps to it later.

A dynamic code holds a short link that passes through a redirect server first. That server logs the moment of each scan, then forwards the person on. If you’re not sure which kind you printed, this guide on how to tell if a QR code is static or dynamic walks through the checks.

The second option works for any code that points at your own website. Add UTM tags to the link, and your web analytics records the visit with a time. The setup is in how to track QR code scans in Google Analytics 4.

How to see QR code scan time of day in your dashboard

Most QR tools that track scans show the time of day as a chart of scans per hour. Open the code, find the hourly section, and read off the tallest bars.

Open your QR code’s analytics page.
Find the time of day or hourly chart.
Set the date range to several weeks, not a single day.
Note the two or three busiest hours.
Filter by country or city if your code is scanned in more than one region.

In QRAnalytica, the Time of Day view gives hourly scan counts for each code, so you can see when each one gets scanned most. The Starter plan already includes scan time, city and device.

How to see scan hours in Google Analytics 4

Google Analytics 4 shows scan hours through its Hour dimension, which Google defines as “the hour when an event was collected, formatted as a two-digit number from 0 to 23” in its dimensions and metrics reference. You add it to a report filtered to your QR traffic.

Tag the QR link with UTM parameters, for example utm_source=flyer and utm_medium=qr.
In GA4, open Explore and start a free-form exploration.
Add the dimensions Hour and Session source / medium.
Filter to the medium qr, then put Hour in the rows.

If you want each day kept separate, use Date + hour instead. Google describes it as “the date and hour when an event was collected, formatted as YYYYMMDDHH.” That lets you spot one unusual evening instead of blending it into a weekly total.

GA4 counts visits that load your page, not raw scans. If someone scans and closes the tab before the page loads, the dashboard of a dynamic QR tool may count it while GA4 misses it.

Which time zone are your scan times in?

The time zone of a scan report depends on the tool, and the three common choices put the same scan in different hours. Some tools use UTC, some use the scanner’s local time, and GA4 uses your property’s reporting time zone.

Where the hour comes from	Example	What it means for your chart
The scanner’s local time	As of November 2026, QR Planet says “the scan time is taken from the local time of the location where the QR Code is scanned”	A 7 pm scan in Paris and a 7 pm scan in Chicago both land at 7 pm
UTC	Linkbreakers says it “timestamps scans in UTC by default”	Every scan is shifted by your distance from UTC
Your reporting time zone	GA4 uses the property’s zone “as the day boundary for reports, regardless of where the data originates”	Scans are shown in your office’s time, wherever the scanner was

QR Planet works out the local zone from the scanning phone’s IP address, not from where you registered your account, according to its time zone help article. The UTC approach is described in Linkbreakers’ scan timing guide.

A worked example: one 7 pm scan, three different hours

Picture a diner in New York who scans a table-tent code at 7 pm on a November evening. New York runs on Eastern Standard Time in November, five hours behind UTC, so the same scan can appear at three different times.

A tool that uses local time shows it at 7 pm, which matches the dinner rush.
Under UTC, it shows at midnight, on the next calendar day.
A GA4 property set to America/Los_Angeles, the example zone in Google’s Admin API reference, shows it at 4 pm, because Pacific Standard Time is three hours behind Eastern.

Read the wrong one and you could move a lunch promotion to the wrong hour. The UTC version is the most misleading, because it also pushes evening scans into the next day.

Daylight saving time adds one more wrinkle. Google says that “if the time zone honors DST, Analytics will automatically adjust for the changes,” so the hour labels stay true to your local clock. A tool that stamps in UTC doesn’t shift, so your real peak appears to move by an hour twice a year.

How to check your time zone before trusting a peak

You confirm a report’s time zone by scanning the code yourself and seeing which hour the scan lands in. It takes two minutes.

Scan the code with your own phone and note the exact local time.
Wait for the scan to appear in the report.
Compare the hour shown with the hour on your clock.
If they differ, the gap is the offset you need to apply.

In GA4, also check the reporting time zone under the property’s settings. Google warns that “changing the time zone only affects data going forward, and is not applied retroactively,” so if you fix it today, older weeks stay in the old zone. In older Universal Analytics, Google even suggested using “Greenwich Mean Time instead of your local time zone” if you didn’t want daylight saving adjustments.

What to do with your peak scan hours

Peak hours are useful when they change a decision, such as when to staff a counter, when to run an offer or which menu to show. Placement drives timing more than any general rule.

Linkbreakers gives examples such as packaging codes peaking when households unbox deliveries and trade show badges spiking during session breaks. It doesn’t publish a study behind those patterns, so treat them as ideas to test against your own data.

Restaurants: compare menu scans by hour against covers to see which meal service gets the most use. The restaurant QR code tracking guide covers table-level setups.
Flyers and posters: compare hours across locations to see which spot gets foot traffic at which time.
Events: match the scan spikes to the schedule to see which session drove interest.

Pair the hours with your scan counts too. A peak of five scans means little, and the guide on what a good QR code scan rate is helps you judge volume.

My take on hourly scan data

I’d look at day-of-week and hour together before changing anything, and I’d want the same peak to repeat over at least three weeks. One busy Saturday can make an hour look important when it was a one-off event.

The limitation: hourly charts tell you when a scan happened, not who scanned or why, and a small code with a handful of scans a day won’t show a reliable pattern at all. For what else you can and can’t learn, see can you see who scanned your QR code.

FAQ

Can I see the scan time of a static QR code?

No. A static code holds the link in the printed pattern and never passes through a server, so nothing records when it was scanned. You need a dynamic code or a tagged link that lands in your own analytics.

Why do my QR code peak hours look a few hours off?

The report is probably in a different time zone from your customers. Some tools stamp scans in UTC, some use the scanner’s local time, and GA4 uses the property’s reporting time zone.

Does changing my GA4 time zone fix old data?

No. Google says changing a property’s time zone only affects data going forward and is not applied retroactively, so older hours stay in the old zone.

How many scans do I need before trusting a peak hour?

There’s no official threshold. Look for the same peak showing up across several weeks rather than trusting a single busy day.

Sources

Track your dynamic campaigns. 7-day trial, no credit card.

Generate Dynamic QR