A person scans the QR code.
The phone reads the encoded BizCity redirect URL and opens it in the browser or supported scanning experience.
Dynamic QR codes become measurable when each scan passes through a controlled redirect. Connect BizCity QR Analytics to your production tracking backend and review real scan activity without decorative or prefilled campaign numbers.
Enter a BizCity dynamic QR tracking URL or QR campaign ID and load its current analytics. The dashboard remains empty until a real response arrives from the production API.
The page intentionally starts without scan counts, countries or charts. Real data appears only after the QR analytics endpoint returns an actual dataset.
A trackable QR code normally contains a short redirect URL rather than the final destination itself. That redirect gives the platform a place to record the scan request before sending the visitor onward.
The phone reads the encoded BizCity redirect URL and opens it in the browser or supported scanning experience.
The production system records permitted event details such as timestamp, campaign ID, country and device information.
After the event is processed, the user is redirected to the website, menu, product, booking page or other destination.
Measure the number of recorded requests generated through a tracked QR redirect during the reporting period.
Use production visitor-identification rules to estimate distinct scanners instead of counting every repeat request as a new person.
Review geographic distribution when location information is available through the production infrastructure.
Understand which device, browser and operating-system categories are generating tracked QR activity.
If a QR directly contains the final website URL, BizCity does not automatically see the scan request. The destination site may still measure resulting visits with its own analytics.
A dynamic QR points to a BizCity-controlled redirect. That redirect can record the scan event and then forward the visitor to the destination.
Because the QR contains the stable redirect URL, the destination can be changed in the backend without reprinting the QR image.
Dynamic QR analytics is most useful where physical touchpoints need measurable digital outcomes.
BizCity QR Analytics keeps the front end empty until the production event system returns real values. If a campaign has no scans, the correct result is zero — not a sample chart.
The QR image is the entry point. Real analytics comes from the tracked redirect and event-processing backend.
Assign the destination and dynamic QR identifier in the BizCity backend.
Encode the stable BizCity redirect URL into the QR image.
The redirect engine records permitted event details and forwards the visitor.
The API aggregates real scan events and returns the current dataset.
Everything you need to know about tracking QR scan activity with BizCity.
QR code analytics measures activity generated through a trackable QR code, including scans, unique scanners, time, country and device information when available.
Yes, when connected to the real BizCity QR analytics API. The dashboard starts empty and only renders values returned by that endpoint.
For BizCity-level tracking, the QR should normally point to a BizCity-controlled redirect URL so the scan can be recorded before redirecting.
If a static QR directly contains the final destination, BizCity does not automatically receive the scan request. Destination analytics may still record the resulting visit.
Yes, when the QR encodes a stable BizCity redirect URL and the backend supports editable destinations.
Yes, when the browser supports the native BarcodeDetector API. If unsupported or unreadable, the page reports that instead of generating a fake decoded value.
The page defaults to /api/qr-analytics. That endpoint should read real QR scan events from the BizCity database.
The dashboard displays the generatedAt or updatedAt timestamp supplied by the backend and does not infer freshness.