Campaign tracking

QR Code UTM Tracking

QR code UTM tracking means every scan of a printed code arrives in your analytics already labelled with utm_source, utm_medium and utm_campaign — nobody types those into a poster URL, so the redirect has to add them. On QRCode Suite the UTM parameters live on the dynamic code itself: set them when you create the code, or later — they are editable without reprinting anything — and the redirect engine appends them to the destination URL as the final step of every scan. The append is careful by design. Only utm_-prefixed keys are added, empty values are dropped, and a parameter the destination URL already carries is never overwritten, so a hand-tagged landing page keeps its own values. The result is offline campaigns that show up in GA4, Matomo or any UTM-aware tool with the same discipline as your email and paid channels.

UTM tagging works on every dynamic QR code — including the Free plan’s three; Pro (€9 per month) removes the cap.

Start free →See pricing

Last updated: August 11, 2026

Set once, appended on every scan

The UTM parameters are stored on the code, not baked into the printed image. Each scan resolves the destination first, then appends your tags to the URL — so the same code stays correctly labelled through destination changes.

Your links are never clobbered

If the destination URL already carries a utm_source of its own, the code’s value does not overwrite it. Only utm_-prefixed parameters are ever added, and empty values are skipped — the append can extend a URL, never corrupt one.

Applied last, whatever branch wins

A/B variant, iOS or Android override, a geo or language rule — whichever destination the redirect engine picks, the UTM append is the final step. Every path out of the code lands tagged the same way.

Edit tags without reprinting

UTM values on a dynamic code are editable at any time. Rename the campaign for the spring run and the stickers, packaging and table tents already in the field start reporting under the new label on their next scan.

Bulk import with UTM columns

The CSV import for bulk generation (Business plan) accepts utm_source, utm_medium and utm_campaign columns per row, so a hundred per-location codes arrive with a hundred distinct labels instead of one shared one.

Know the limits

UTM parameters are appended to redirect destinations — codes that encode data instead of opening a URL, like a Wi-Fi code, have nowhere to put them. Only keys starting with utm_ are accepted, and the tags are only as useful as the analytics reading them: the destination site still needs GA4 or an equivalent installed.

Frequently asked questions

What analytics does QRCode Suite track?

QRCode Suite tracks scan count, unique scanners, device type, operating system, browser, country, city, referrer, and UTM parameters. Bot traffic is detected and excluded, and IP addresses are hashed before any event is written.

How long is analytics data retained?

Retention is set by your plan and enforced automatically: 30 days on Free, 12 months on Pro, 24 months on Business, and 36 months on Agency. Events older than the window are purged.

Does QRCode Suite integrate with Google Analytics?

Yes. GA4 integration is available on Pro and above. QR code scans are sent as GA4 events, enabling full funnel tracking from scan to conversion.

Does QRCode Suite support Meta Pixel?

Yes. Meta Pixel events are fired on scan for Pro and above plans, enabling retargeting audiences based on QR code interactions.

Where is my scan data stored?

Scan events are stored in QRCode Suite's own database, where they stay first-party: we never sell them, never share them with an ad network, and never enrich them with a third-party tracker. Nothing is forwarded to GA4, Meta Pixel or any other external platform unless you connect that integration yourself.

Tag the scan, not the guesswork

Set UTM parameters once on the code and every redirect carries them.

Start free See pricing