City-by-City QR Scan Analytics: How to Run Smarter Pan-India Campaigns

"12,000 scans this month" tells you almost nothing useful on its own for a campaign running across multiple Indian cities. A national aggregate flattens exactly the variance that actually matters — Mumbai and Kochi don't behave the same way, a metro launch and a tier-2 rollout don't convert at the same rate, and device mix, language response, and print-vs-digital weighting all shift meaningfully by city. Our tier-2 cities guide covers the placement and design side of this; this post is about the analytics side — reading the data once the campaign is live.

City data comes from IP-based geolocation at the moment of the scan — an estimate derived from the network the scanning device is on, not an exact GPS coordinate. This is genuinely accurate at the city level for the overwhelming majority of scans, but it's worth being precise about what it isn't: it can occasionally misattribute a scan where a mobile carrier's IP routing doesn't perfectly match the user's physical location, and it won't tell you the exact street or store a scan happened at. Exact GPS-level location (available on the Premium plan, ₹14,999/month) is a separate, more precise capability for when city-level granularity genuinely isn't enough.

Geo heatmaps (Pro plan, ₹4,999/month, and up) turn the same city-level data into a visual map of where scan activity is actually concentrated across the country, which is a genuinely faster way to spot an unexpected pocket of activity — or a conspicuous gap — than scanning a table of city names and numbers.

One thing worth stating plainly, since it comes up often: SMLLR has no geographic redirect rule — a single QR code cannot show a different destination based on the scanning city. What city-level analytics gives you is accurate scan reporting by location, not location-based routing. If you need genuinely different content per city (a city-specific offer, a regional-language landing page), the working pattern is a separate QR code per city, each pointing at its own destination — which also happens to give you cleaner, code-level attribution rather than needing to infer city performance from location data alone.

A few habits that keep city-level data from misleading you: don't overreact to a handful of scans from an unexpected city — three scans from a place you never advertised is more likely a forwarded link or a coincidence than a real signal, and needs volume before it means anything. Compare relative distribution across your target cities rather than fixating on absolute counts, since raw scan numbers are also a function of how much print or media you ran in each city, not purely how well the city responded. And corroborate city data with device and language patterns — a city showing unusually low engagement alongside a heavy Android-and-vernacular-browser mix might be telling you your landing page isn't working there, not that the city itself is unresponsive.

The actual payoff of this data is reallocation: after a campaign cycle, city-level scan and conversion data tells you which markets are earning their media spend and which aren't, in a way a single national number never could. A brand running print across ten cities might find three of them driving disproportionate results — worth a bigger share of next quarter's budget — while two others barely register despite equal spend, worth cutting or redesigning before repeating the same placement.

Create a separate QR code per city or market and group them under a campaign in Campaign Manager (Basic plan, ₹1,999/month, and up), giving you both the national rollup and the per-city breakdown from the same data. For an agency reporting this to a client, a Client Dashboard report link (Pro plan, ₹4,999/month, and up) gives them a live, bookmarkable view of the same city breakdown without a manual report needing to be built and sent each time.

Create your QR code on SMLLR, structure it by city from day one, and let the geography tell you where the campaign is actually working.