How to Track QR Code Scans with QRLynx and GA4

QRLynx tracks a QR scan when a registered user saves a supported QR as dynamic and turns on Track Scans. The Free plan includes 3 active dynamic QR codes, unlimited scans, scan totals, a daily unique-scan estimate, activity over time, and top-performing codes. Country detail starts on Pro. City, device, browser, operating-system detail, and CSV export start on Business.

The scan and the website visit answer different questions. QRLynx measures the request to the dynamic QR route. A destination analytics tool such as Google Analytics 4 measures what happens after the browser reaches your website. To track QR traffic in Google Analytics 4, add UTM parameters to the destination website URL, confirm its GA4 tag can run with the visitor's consent settings, and check campaign reports after arrival. QRLynx scan analytics and GA4 website measurement are separate reports.

How scan tracking works in QRLynx

A static URL QR stores the final destination directly in its pattern. The phone can open that destination without contacting QRLynx, so QRLynx has no scan request to count. A tracked dynamic QR stores a QRLynx-managed short route. When the route is requested, QRLynx records the eligible scan event and then sends the browser to the saved destination.

Dynamic mode and tracking are related but separate settings. In the generator, turning on Track Scans automatically turns on Dynamic URL. Turning dynamic mode off also turns tracking off. This keeps the saved QR behavior consistent: tracking requires the managed redirect, while a dynamic QR can remain editable without recording scan analytics if tracking is disabled.

QRLynx analytics and GA4 measure different stages

QRLynx counts the eligible request to the managed QR route. GA4 begins after the visitor reaches a tagged website and its analytics setup runs. The two totals can differ because they measure different events. A scan may stop before the landing page loads, a browser or consent setting may limit website measurement, or one person may scan more than once before producing one website session.

For a website campaign, add campaign parameters to the final destination before saving the QR. Google recommends consistent utm_source, utm_medium and utm_campaign values. Use utm_content to distinguish the placement:

https://example.com/offer?utm_source=qr_code&utm_medium=print&utm_campaign=spring_sale&utm_content=store_entrance

Use the free QRLynx UTM Builder to assemble the URL. Keep values lowercase and stable, and use a separately named QRLynx QR for each placement you need to compare. These labels describe the campaign; they do not identify the person scanning. See Google's campaign URL guidance.

A direct static QR can also send a tagged website URL to GA4. It does not provide QRLynx scan analytics or an editable printed destination. Use a dynamic QRLynx URL QR with Track Scans enabled when you need both stages.

What we verified in a QRLynx-to-GA4 test

On October 16, 2026, the QRLynx team created a separate QA dynamic URL QR with Track Scans enabled, downloaded its SVG and decoded the actual short-link payload. Opening that decoded link preserved utm_source=qr_code, utm_medium=print, utm_campaign=qa_content_proof_20261016 and utm_content=counter_card at the destination.

A signed-out test visit with temporary measurement consent produced one observed page_view and the exact qa_content_proof_20261016 campaign value in GA4 Realtime. Temporary consent was restored after the check. This was a controlled browser test of the downloaded QR's decoded link, not a physical camera scan. It verified redirect and event receipt, not finalized acquisition attribution, a new registration or a paid conversion.

Our signed-in staff test visit was excluded from optional website measurement. That is a condition on our site, not a universal GA4 rule. Use the normal visitor path on your own destination and document any exclusions.

If your QR campaign is missing from GA4

• Check the final URL: a redirect or destination can remove campaign parameters. Test the exported QR, not only the address copied into the generator.
• Check the destination and property: a tagged URL cannot install GA4. Confirm the right tag is running on the final site and that you have access to its reports.
• Check consent and exclusions: declined measurement, blockers and internal-traffic rules can affect what you observe. Do not bypass a visitor's choice to make counts match.
• Check report scope and processing: Realtime supports a receipt check. Use processed Session campaign or Session source / medium for campaign analysis, rather than treating an empty First user source card as failure.
• Check the channel label: a custom medium such as print can appear under Unassigned because it does not match a default channel rule. Check source, medium and campaign before concluding the visit was lost.

Google documents Realtime's attribution limits, the Traffic acquisition report and default channel definitions.

Measure registrations and payments after arrival

A scan request or page_view does not prove that someone registered or paid. Verify a completed action in the destination system before treating it as a business outcome. Where appropriate, configure and test a corresponding GA4 event and mark the meaningful action as a key event.

Keep staff tests, duplicate actions and returning customers separate from new customer acquisition. A paid order also needs payment evidence; an opened checkout is not a payment. UTM tags label traffic but do not create these events or prove that the QR campaign caused the result.

What the unique-scan number means

QRLynx does not know whether a scanner is a specific person. For each QR code, the first scan request from an IP address during a UTC calendar day is counted as unique. A short-lived key marks that combination for 24 hours. The analytics dataset receives the resulting unique or repeat classification, along with derived device and approximate location categories. It does not expose a scanner's name or raw IP address in the dashboard.

Treat the number as a daily unique-scan estimate. Two people on one shared network can be grouped together. One person who changes networks can be counted again. A later scan on another day can also count as unique for that day. Use total scans and the unique estimate together, then validate important business outcomes in the destination system.

Location, device, browser, and referrer limits

Country and city are derived from the network request, not from the phone's GPS. VPNs, mobile carrier routing, relay services, and corporate networks can change the apparent location. Device, browser, and operating-system categories are derived from the request's user-agent information and can be incomplete or generalized. A referrer header may be available for some recent exported events, but camera and app handoffs often provide no useful referrer.

Use these dimensions for broad patterns and QA decisions. For example, a Business account can prioritize testing on the device and browser categories that appear most often, or compare broad city patterns across distinct placements. Do not use these fields to claim that a named person visited an exact location.

How CSV export works

CSV export is available on Business and Enterprise. For recent ranges up to 90 days, the export groups scan events that share the same second and dimensions, and includes the date, QR name and URL, country, city, device, operating system, browser, referrer, and represented scan count. It is not a list of identified people.

For eligible longer ranges, QRLynx can export aggregate history summaries with period, grain, QR, scan totals, unique estimates when available, dimension summaries, and a quality status. Choose the report that matches the decision. Use recent rows for operational review and aggregate history for long-range trends.

Build placement-level reporting that stays understandable

Create one saved QR per placement when you need a clean comparison. A single code printed on a storefront, receipt, table tent, and package can show total demand, but it cannot tell you which physical placement produced each scan. Distinct names and UTM content values create that separation.

• Name by campaign, location, and placement: spring-sale_downtown-store_entrance.
• Keep the same campaign vocabulary: use one spelling and capitalization across QRLynx and GA4.
• Test the landing action: scan volume is useful, but completed registrations, purchases, form submissions, or downloads answer the business question.
• Compare rates with context: record how many pieces were distributed or how much foot traffic a placement received before comparing performance.

For larger portfolios, folders help organize saved codes. Dynamic bulk creation begins on Pro and gives each generated code its own destination and analytics while consuming the plan's active dynamic capacity.

Privacy responsibilities

Network identifiers can be personal data under privacy law even when they are used to derive aggregate reports. QRLynx analytics does not identify scanners by name, but that does not remove the operator's responsibility to explain applicable measurement and choose an appropriate legal basis. Keep your privacy notice aligned with the data and tools used on the destination page, especially when forms, advertising pixels, or account logins are involved.

A scan alone does not provide consent to collect contact details. If the campaign needs a name, email address, or another submitted field, collect it through a clear destination form or an eligible QRLynx lead form and explain the purpose at the point of collection. Review the QRLynx privacy policy and obtain jurisdiction-specific advice when required.