What Tracking Settings does
Tracking Settings — labelled Retarget in the dashboard — lets you connect a single QR code to your own marketing and analytics tools. You add up to three optional IDs: a Google Tag Manager container, a Meta (Facebook) Pixel, and a Google Analytics property. From then on, those tags belong to that QR code.
The result is that a scan of your printed or on-screen QR code is no longer invisible to your existing stack. The same Pixel that tracks your website visitors, and the same Analytics property that measures your traffic, also see the people who arrive by scanning your code — without you touching the code's artwork or reprinting anything.
Why retarget from a scan
A QR code usually bridges the offline world (a poster, a flyer, packaging, a business card) and your website. Retargeting tags let you treat that bridge like any other traffic source:
- Build audiences from offline touchpoints — someone who scans your packaging can later be shown ads through Meta, the same way a website visitor would be.
- Measure offline-to-online conversion — see in Google Analytics how scan-driven visitors behave compared with your other channels.
- Layer additional tags — a Google Tag Manager container lets you fire whatever else you have configured (other analytics, conversion tags, and so on) without adding each one separately.
This is different from QRKIT's own built-in scan analytics, which you get in your dashboard regardless. Retargeting feeds your tools, under your accounts.
Plans and access
Retargeting is a Plus, Pro, Ultra, and Agency feature. On the Free and Starter plans the Retarget option is locked and prompts you to upgrade.
Access is tied to the plan of the active workspace, not to you personally. If you're working inside a workspace on Plus or above, you can set retargeting tags on that workspace's codes — even if your own personal workspace is on a lower plan.
Opening Tracking Settings
Find the QR code in your dashboard list. Retargeting is reached through the Retargetcontrol — a small target icon — available both as a button on the code and inside the code's options menu. Selecting it opens the Tracking Settings dialog.
When a code already has at least one tag set, the target icon turns blue, so you can tell at a glance which codes are wired up to your tools and which aren't.
How the tags fire
Retargeting works with dynamicQR codes, which send each scan through QRKIT before forwarding the visitor to your destination. As part of that hand-off, the tags you've attached load — so your Pixel registers the visit, your Analytics property records the session, and any tags in your Tag Manager container run.
Because the tags live in the redirect rather than in the QR image itself, the printed code never changes. You can add, swap, or remove tags at any time and every existing code in the wild picks up the new configuration on its next scan — no reprint required.
Finding each ID
You bring the IDs from the tools you already use. Here's where each one lives:
- Google Tag Manager — open your container; the
GTM-ID is shown at the top of the workspace, next to the container name. - Meta Pixel — in Meta Events Manager, your data source lists its Pixel ID (a long number). Copy that number into the Pixel field.
- Google Analytics — in GA4, your measurement ID (
G-) is under Admin → Data streams → your web stream. Universal Analytics IDs (UA-) are still accepted for older properties.
Paste, click Update, and the code is connected. To confirm everything fires, scan the code yourself and check the realtime view in Meta or Google Analytics.
Editing or removing tags
Reopen Tracking Settings on the same code at any time to change an ID. Updating overwrites the previous values.
To switch retargeting off entirely, clear all three fields and click Update. Saving an empty form removes the tags from the code — the target icon returns to its neutral colour, and future scans no longer load any of your tags.
Privacy and consent
The tags you add here are yourtags, running under your own Google and Meta accounts. That means the responsibility for how they're used — consent banners, privacy policy disclosures, and regional rules such as GDPR — sits with you, exactly as it does on your website.
If your site already manages consent for the same Pixel or Analytics property, treat scan traffic the same way: you are responsible for obtaining consent where the law requires it — for example under GDPR and ePrivacy rules — before these tags run, and for disclosing QR scan tracking in your privacy policy alongside your other analytics and advertising tools.
Frequently asked questions
Does adding tags change my QR code or require a reprint?
No. The tags live in the dynamic redirect, not in the QR image. The printed or published code stays exactly the same, and any tag changes take effect on the next scan.
Whose account do the scans get attributed to?
Yours. You enter your own Google Tag Manager, Meta Pixel, and Google Analytics IDs, so the data flows into your accounts — not into a shared or QRKIT-owned property.
Can I use all three tags at once?
Yes. Each field is independent and optional. Add one, two, or all three in any combination, and only the ones you fill in will fire.
Does this work on every QR code type?
Retargeting tags can only run when a scan opens a web page, so they're most useful on dynamic codes that redirect to a URL. A code that doesn't open a web page when scanned — for example a Wi-Fi code that joins a network directly — gives the tags nowhere to load.
Will adding a Pixel slow down the scan?
The tags load as the visitor is forwarded to your destination, the same way they would on any landing page. Scanners still arrive at your content as normal.
Which plans include retargeting, and how do I turn it off?
Retargeting is available on Plus, Pro, Ultra, and Agency. To turn it off for a code, open Tracking Settings, clear the fields, and click Update.
Ready to retarget your offline audience?
Connect your own tags to a dynamic QR code and turn every scan into a measurable, retargetable touchpoint.