Track every scan in real time

On qrcode.ing, scan tracking is built into every QR code automatically. When someone scans your QR code, the event is logged and appears in your analytics dashboard in real time. You do not need to install any extra software or configure tracking — it works out of the box.

You can track the number of scans, the approximate location of each scan (country and city level), the device type used (iOS, Android, or desktop), and the time of each scan. For privacy reasons, qrcode.ing does not identify individual users by name or personal details. Tracking is anonymous.

qrcode.ing provides scan count totals, daily and weekly scan history, geographic breakdown (country and city), device type breakdown (iOS, Android, desktop), and scan timestamps. Advanced plans include CSV exports and extended analytics history.

Yes. Basic QR code tracking — including scan counts, location, and device data — is included free on all qrcode.ing QR codes. No sign-up is required for basic use. Advanced analytics features such as CSV exports and extended history are available on paid plans.

A trackable QR code is a dynamic QR code that records data about each scan event, including when it was scanned, where it was scanned from, and what type of device was used. All QR codes created on qrcode.ing are trackable by default.

Create a separate QR code for each campaign placement — for example, one for print ads, one for social media, and one for product packaging. Then compare scan data in your analytics dashboard to see which placement drives the most engagement. Combine this with UTM parameters in your destination URL for full attribution in Google Analytics.

QR code scan tracking on qrcode.ing records every scan event at the server level, so the scan count itself is highly accurate — each scan generates a server request that is logged immediately. Location data is derived from the IP address of the scanning device and is accurate to the country level in almost all cases and to the city level in most cases. Device type detection is based on the user-agent string and is accurate for the vast majority of standard iOS, Android, and desktop browsers. The only scans that may not be logged are those where a user scans but cancels before the URL loads, which is a rare edge case.

When a user scans a QR code, the scan request passes through qrcode.ing servers before redirecting to the destination URL, which is how scan data is captured. The user is not personally identified — no name, email, or persistent identifier is collected. The data recorded is similar to what any web server logs: timestamp, approximate location from IP address, and device type from the user-agent string. This is standard practice for any link-tracking system and is functionally equivalent to a shortened URL with analytics. If you want to be fully transparent with your audience, you can note in your campaign materials that scan data is collected for analytics purposes.

QR code tracking and UTM tracking measure different things and work best together. QR code tracking (via qrcode.ing) records events at the scan level — how many times the code was scanned, from where, on what device, and at what time. This data is captured before the user even reaches your website. UTM tracking uses parameters appended to your destination URL to attribute website sessions to specific campaigns in tools like Google Analytics. UTM data only starts once the user lands on your site. By combining both, you get a complete picture: scan-level data from qrcode.ing and downstream conversion data from your web analytics platform.

Yes. Only dynamic QR codes support built-in scan tracking. A dynamic QR code routes every scan through a server before redirecting to the final destination — this server request is what captures the scan event. Static QR codes encode the destination URL directly in the pattern, so scans go straight to the destination with no intermediary server and no tracking. All QR codes created on qrcode.ing are dynamic by default, which means tracking is included automatically at no extra cost.

Yes. Every qrcode.ing analytics dashboard shows a geographic breakdown of scans by country and city. Location is determined from the IP address of the scanning device and does not require any GPS data from the user. Country-level data is accurate in nearly all cases. City-level data is accurate for the majority of scans, with some variation for mobile devices on cellular networks that route traffic through centralized carrier infrastructure. The geographic data is especially useful for multi-region campaigns — you can compare scan rates by city or country to identify which markets respond best.

To measure QR code ROI, combine scan data from qrcode.ing with downstream conversion data from your web analytics platform. Step one: create separate QR codes for each campaign placement (print ad, packaging, social post, etc.) so you can attribute scans by source. Step two: add UTM parameters to each QR code's destination URL to track sessions in Google Analytics or your preferred platform. Step three: compare scan counts from qrcode.ing with conversion events (purchases, sign-ups, form submissions) in your analytics to calculate a conversion rate per QR placement. Step four: divide campaign cost by the number of conversions attributed to each QR placement to get cost per conversion. This method gives you end-to-end attribution from the physical scan to the final conversion.

Create one unique QR code per placement and give each a descriptive name in your qrcode.ing dashboard (for example, 'Spring Sale — Poster — NYC' or 'Social — Instagram Bio — May'). After deploying, let each placement run for the same period (two to four weeks for most print campaigns). Then open your analytics dashboard and compare total scans, scan-per-day velocity, geographic breakdown, and device mix side by side. Placements with high scan rates but low conversion rates (measured via UTM data in your web analytics) may need a stronger call-to-action or a better landing page. Placements with low scan rates may need better positioning or a larger QR code size.

Scan data on qrcode.ing appears in your analytics dashboard in real time. There is no delay between a scan event and when it shows up in your dashboard — each scan triggers a server request that is logged immediately. This means you can watch scans come in live during an event, a trade show appearance, or a product launch. The real-time nature of the data is especially useful for time-sensitive campaigns where you want to confirm that QR codes in a specific location are actually being scanned before committing to a full deployment.

QR code tracking refers to the real-time capture of each individual scan event — the exact moment someone scans your code, where they are, and what device they used. QR code analytics refers to the aggregated reporting layer built on top of that tracking data — charts, scan totals, trends over time, and CSV exports. Tracking is the data collection; analytics is the data interpretation. On qrcode.ing, both are included automatically. You get a live scan feed for real-time campaign monitoring and a full analytics dashboard for weekly reporting — without needing two separate tools.

Yes. QR code tracking on qrcode.ing works identically whether your code appears on a printed flyer, a product package, a digital screen, a social media post, or an email newsletter. Every scan — regardless of where the code was placed — is captured at the server level when the scanner's device loads your destination URL. For multi-channel campaigns, the best practice is to create a separate QR code per placement so that each channel has its own scan counter in your dashboard. This lets you compare, for example, how many scans your billboard generated versus your Instagram bio QR over the same period.