What Graklink tracks when your QR code gets scanned, and what it doesn't

What an ordinary scan or click records

A dynamic QR code or short link receives a request and sends the visitor to its configured destination. Graklink records available activity evidence for the owner. A static QR code points directly to its encoded URL and does not create a Graklink redirect event.

Activity data can include:

• Time, QR code or short-link identity, and the destination/rule/variant served when routing is configured.
• Approximate country, region and city derived from the network.
• Device, browser and operating-system categories from request information.
• Referring source and request-quality information used to distinguish qualifying activity from known automation.
• Pseudonymous measurement signals where the configured policy permits them.

A raw IP address is not stored in the scan/click analytics records. It can be processed to derive location or a keyed network identifier, and infrastructure or security systems can process it separately. A keyed identifier is not a QR pattern or a known device identity.

Estimates are not people

Shared Wi-Fi can make different visitors look alike to network-based measurement. A changing network can make one visitor look different. Device categories describe the browser opening the link, not proof that a desktop computer used a camera to scan a printed QR code.

Read the method and coverage beside an audience measure. Do not add estimates from incompatible periods, assume missing geography means a particular place, or treat a count as a list of customers. Total and estimated scanners explains the distinction.

Optional experiment measurement

Ordinary redirects do not show a measurement dialog. An explicitly configured outcome experiment can use a random first-party browser identifier, scoped to the customer and measurement period, and a signed receipt passed to the configured destination. A validated outcome can then be associated with that eligible experiment visit.

This path depends on measurement eligibility, source coverage and the configured privacy policy. Where consent is required and absent, identifier-based measurement is excluded. The customer can opt into a supported consent dialog; visitors reach the destination whether they allow measurement or decline. It is not a default interruption added to every QR scan.

The Privacy policy explains the identifier, withdrawal, storage period and destination integration. These settings do not establish a blanket legal exemption for every jurisdiction.

Connected results and reports

Track can connect a selected Google Analytics 4 property through read-only OAuth access. It shows the connection’s source quality, coverage and last successful sync, and supports reconnecting, revoking access and deleting the connection. QR activity and comparisons still work without GA4. Website outcomes need their own evidence; a scan alone does not establish a purchase or donation.

Your confirmed Business Intelligence Profile and Business goals tell the report what the business is trying to achieve. The report ties its observations and recommendations to the measured facts it used, but recommendations still require judgment. Report snapshots preserve the period and source qualifications used when generated, and Track includes one eligible weekly report.

Who can use the information

Customer analytics are private to the account and authorized service processing. They are not sold or published as another customer’s results. Providers help host, protect and operate the service; legal disclosures and customer-directed exports are separate from selling data.

Exports contain the selected tables and reporting context shown before download. They do not promise every raw historical request. Export help explains the available formats. The Privacy policy covers service providers, retention and privacy requests.