Tracking and pixels
Add UTM tags to dynamic code destinations automatically and fire your ad platform pixels when people scan.
EZQR analytics tell you how often a code is scanned. Tracking settings connect those scans to the tools you already use. Automatic UTM tagging lets Google Analytics and similar tools attribute QR traffic correctly. Retargeting pixels let you build ad audiences from people who scanned.
Both settings apply to every dynamic code in your workspace. Static codes don't pass through EZQR, so they can't be tagged or tracked.
Open tracking settings
Go to Settings and find the Tracking and pixels card. Only workspace owners and admins can change these settings. Make your changes and click Save tracking settings.
Automatic UTM tagging
Turn on Add UTM tags automatically. EZQR then adds UTM parameters to the destination of every dynamic code when it's scanned:
| Parameter | Value |
|---|---|
utm_source | Your utm_source value. Defaults to qr. |
utm_medium | Your utm_medium value. Defaults to qr_code. |
utm_campaign | The code's name, lowercased with spaces and symbols replaced by underscores. A code named "Spring Menu" becomes spring_menu. |
Values can use letters, numbers, dots, dashes and underscores, up to 60 characters.
EZQR never overwrites UTMs you've set yourself:
- If a destination already has
utm_source, it's left unchanged. - If it has
utm_mediumorutm_campaignbut noutm_source, those existing values are kept and only the missing ones are added.
To set UTMs for a single code, open it, click Edit and use UTM Parameters. UTMs added to the scanned link are passed through to the destination as well.
Automatic UTM tagging is available on every plan.
Retargeting pixels
Turn on Retargeting pixels and enter the IDs for the platforms you use. When someone scans a dynamic code, they see a brief loading page while your pixels fire, and are then sent to the destination.
| Platform | Field | ID format | Event sent on scan |
|---|---|---|---|
| Google Analytics 4 | Google Analytics 4 | G-XXXXXXXXXX | qr_scan |
| Google Tag Manager | Google Tag Manager | GTM-XXXXXXX | qr_scan pushed to the data layer |
| Meta | Meta pixel | 8 to 20 digits | PageView and custom QRScan |
| LinkedIn Insight Tag | Partner ID, 4 to 12 digits | Insight Tag page view | |
| TikTok | TikTok pixel | 10 to 30 letters and numbers | Page view and ClickButton with content_name: qr_scan |
Use these events to build audiences or conversions in each platform, for example a Meta custom audience of everyone who triggered QRScan.
The loading page redirects in under a second. If scripts are blocked, it continues to the destination automatically, and shows a Continue link.
Retargeting pixels are available on Pro and Max.
Privacy behaviour
Pixels only fire for real people who haven't opted out. EZQR skips the loading page and redirects straight to the destination when:
- The scan is classified as a bot, crawler or link preview. See Human vs bot scans.
- The visitor's browser sends Do Not Track (
DNT: 1) or Global Privacy Control (Sec-GPC: 1). - The code is gated behind a lead form.
Skipped visitors still reach your destination. Scans from visitors with Do Not Track or Global Privacy Control are still counted in EZQR analytics, and bot scans are recorded separately from human scans. Automatic UTM tagging doesn't depend on pixels, so it still applies to these scans.
Pixels set cookies and send data to third parties. Make sure your privacy policy and consent practices cover QR scans in the regions where your codes are used.
Plan requirements
| Free | Lite | Pro | Max | |
|---|---|---|---|---|
| Automatic UTM tagging | Yes | Yes | Yes | Yes |
| Retargeting pixels | No | No | Yes | Yes |