Current Article
Tracking Overview
Tracking Overview
A complete guide to how Lifetime QR Codes tracks QR code scans — from built-in analytics to UTM parameters, pixel tracking, GPS, and IP-based location — and how to stay compliant with GDPR and CCPA.
Built-In Analytics vs. Third-Party Tracking
Lifetime QR Codes uses two distinct tracking layers that work alongside each other:
- Built-in analytics — collected server-side by Lifetime QR Codes every time a scan redirect is processed. This includes timestamp, device type, OS, browser, country, and city. It is always active, requires no configuration, and is visible directly in your Lifetime QR Codes dashboard. Because it runs server-side, it is not affected by ad blockers or JavaScript being disabled.
- Third-party tracking — optional integrations such as Google Analytics 4, Meta Pixel, or custom webhooks. These fire client-side (in the scanner's browser) as the redirect landing page loads. They allow you to share scan data with external platforms, but they depend on JavaScript running in the browser and can be blocked by privacy tools.
For the most complete picture, use both layers. Your Lifetime QR Codes dashboard will always show the authoritative total scan count, while third-party tools provide richer attribution and audience capabilities.
UTM Parameters
UTM parameters are tags appended to a destination URL that tell analytics platforms where traffic came from. Lifetime QR Codes supports auto-appending UTM parameters to any QR code that points to a web URL.
To configure UTM parameters for a QR code, open the code editor and go to Advanced Settings > UTM Parameters. You can set:
utm_source— where the traffic originates (e.g., Lifetime QR Codes, flyer).utm_medium— the channel (e.g., qr_code, print).utm_campaign— the campaign name (e.g., summer_sale_2026).utm_content— optional, for distinguishing multiple codes in the same campaign.utm_term— optional, typically used for paid keyword tracking.
These parameters are appended automatically to the destination URL on every scan. You do not need to modify the QR code itself — changing UTM values in the dashboard takes effect immediately because the code is dynamic.
Pixel Tracking
Pixel tracking works by firing a tiny JavaScript snippet in the scanner's browser as the redirect page loads. Lifetime QR Codes supports two pixel integrations:
- Google Analytics 4 Pixel: Sends a
page_viewand a customqr_scanevent to your GA4 property. This populates GA4's Acquisition and Engagement reports with scan data. - Meta Pixel: Fires a
PageViewevent to your Meta Pixel, enabling Custom Audience creation and ad attribution on Facebook and Instagram.
Pixel events fire within milliseconds of the redirect page rendering. Because they are client-side, a scanner using an aggressive ad blocker or a browser with strict privacy settings (e.g., Firefox with Enhanced Tracking Protection) may block the pixel. In those cases, the scan is still counted in Lifetime QR Codes's built-in analytics via the server-side layer.
GPS Tracking
When GPS tracking is enabled on a specific QR code, the redirect page requests the scanner's precise location via the browser's Geolocation API. This produces highly accurate coordinates — typically within a few meters — compared to IP-based location which can only resolve to city level.
Key points about GPS tracking:
- The scanner must explicitly grant location permission in their browser. If they deny or dismiss the prompt, Lifetime QR Codes falls back to IP-based city/country data.
- GPS coordinates are stored only for that individual scan record and are visible on the Scan Map in your analytics dashboard.
- GPS tracking must be enabled per QR code under Advanced Settings. It is off by default.
- Enabling GPS tracking requires that you disclose this to your end users in your privacy policy or at the point of scan. See the Privacy Compliance section below.
IP-Based Location
For every scan, Lifetime QR Codes performs a server-side IP geolocation lookup to determine the scanner's approximate country and city. This happens automatically using the request IP before the redirect occurs, so it works even if JavaScript is disabled or the user denies GPS permission.
Accuracy varies by region. In major metropolitan areas it is typically city-accurate. In rural or remote areas it may resolve only to a region or state. Mobile carriers using shared or tunneled IP addresses may occasionally produce less precise results.
The raw IP address is used only during the geolocation lookup and is not storedin your scan records. Only the resolved country and city are retained, which significantly reduces privacy risk.
Privacy Compliance (GDPR & CCPA)
Lifetime QR Codes is designed with privacy-by-default principles. Here is how the platform handles compliance with major privacy regulations:
- No PII stored without consent: Lifetime QR Codes does not store personally identifiable information (PII) such as names, email addresses, or raw IP addresses in scan records unless users explicitly provide them (e.g., via a Form QR code). Country and city data derived from IP geolocation is considered non-PII under most regulatory frameworks.
- GPS data and consent: GPS coordinates can identify individuals indirectly (e.g., if scans occur at a home address). Under GDPR, explicit user consent is required before collecting precise location. The browser's native permission prompt satisfies this requirement, but you should also disclose GPS collection in your privacy policy.
- Third-party pixels and GDPR: If you operate in the EU or UK and use GA4 or Meta Pixel integrations, you may need to include these trackers in your cookie consent mechanism. Lifetime QR Codes does not deploy a consent banner on its redirect pages by default. You are responsible for ensuring your integrations comply with applicable law.
- CCPA: California residents have the right to know what data is collected about them. Since Lifetime QR Codes scan records do not contain PII (only device type, OS, browser, country, and city), most use cases fall below CCPA's personal information threshold. If you collect form data through QR codes, review that data separately.
- Data deletion: You can delete any QR code's scan history at any time from the dashboard, or submit a data deletion request for your entire account by contacting support. Deletion is permanent and irreversible.
If you have specific compliance questions for your jurisdiction, we recommend consulting a qualified privacy attorney. Lifetime QR Codes's privacy policy is available at lifetime-qr-codes.com/privacy.