QR Code Retargeting: Turn Scans Into Ad Audiences

QR code retargeting means showing ads later to people who scanned your poster, flyer, or packaging, and counting those scans as conversions in your ad platforms. QRelix does it in two layers: automatic UTM tags on every scan (on every plan, including Free), and scan events sent to Google Analytics 4, Meta, TikTok, LinkedIn, and Google Ads (on Pro and Team). Here is how each piece works, what it sends, and how to turn your print into an audience.

Why QR code scans vanish from your ad platforms

When someone clicks an online ad, the ad platform sees the click. When someone scans a printed QR code, nothing like that happens. The phone's camera opens a link, and unless that link carries labels, Google Analytics files the visit as direct traffic and your ad tools never hear about it.

That causes three problems for a small business:

• You cannot tell which poster, mailer, or table tent drove a sale.
• Your ad platform cannot count a scan as a conversion, so it cannot optimize for it.
• The people who showed interest by scanning are not in any audience you can reach again.

QRelix already shows who scanned, where, and when in its own analytics. UTM & Pixels carries that into the tools you already use.

Automatic UTM tracking on every QR code scan

UTM tags are the utm_source, utm_medium, and utm_campaign parameters Google Analytics uses to label where a visit came from. Adding them by hand to every link is tedious and easy to get wrong. QRelix adds them to your destination the moment someone scans, so your saved links stay clean and one template works for all your codes.

A template can use placeholders that QRelix fills in per scan:

• {code_name}: the QR code's name, such as spring-menu
• {code_id}: the QR code's ID
• {category}: its category
• {domain}: the scan link domain
• {route_rule}: the Smart Routing rule that matched
• {variant}: the A/B variant that was picked
• {device}: iOS, Android, desktop, or other
• {country}: the scanner's country
• {date}: the scan date

Values are lower-cased and made link-safe, so "Spring Menu (Patio)" becomes spring-menu-patio in your reports. If a destination already has a utm_ tag, QRelix keeps yours and only adds the missing ones, and anchors like #menu stay at the end of the link.

UTM tags are included on every plan. For the Google Analytics side of this, see our guide to QR code tracking in Google Analytics.

QR code Facebook pixel, TikTok, and GA4: server-side events

On Pro and Team, you can connect your ad and analytics tools under UTM & Pixels, then Pixels. Every scan of every QR code is sent to them, and you can turn any connection off for a single code on its Configure page.

Three tools can receive scans straight from QRelix's servers, right after the scan is recorded:

• Google Analytics 4, through the Measurement Protocol
• Meta (Facebook and Instagram), through the Conversions API
• TikTok, through the Events API

Server-side is the recommended setup because:

• There is no delay for scanners. The event is sent after the redirect, so scans are just as fast.
• It is not blocked by ad blockers or browser privacy settings.
• There are no cookies or scripts on your scan pages, so it works worldwide, including Europe.
• It is private by design. QRelix sends the QR code, device type, and country. Never IP addresses, fingerprints, or contact details.

Each tool needs an ID and a secret, and QRelix stores the secret part encrypted. GA4 needs a Measurement ID and a Measurement Protocol API secret. Meta needs a Pixel ID and a Conversions API access token. TikTok needs a Pixel ID and an Events API access token.

Browser pixels for audiences

Browser pixels load on the scan page just before the redirect, for at most about a second. QRelix supports the LinkedIn Insight Tag, Google Ads conversions, and browser versions of GA4, Meta, and TikTok.

Browser pixels are skipped for scanners in the European Economic Area, the UK, and Switzerland, where a scan page cannot collect cookie consent, and for scans whose country is unknown. When you use the server-side and browser versions of the same tool, events share an ID so each scan is counted once.

The LinkedIn Insight Tag builds retargeting audiences from scans. To also count each scan as a LinkedIn conversion, add a Conversion ID when you connect LinkedIn.

How privacy and consent are handled

The short version: server-side events carry no personal data, and browser pixels never run where consent is required.

• Server-side events send the QR code, device type, and country. No IP addresses, fingerprints, or contact details.
• Server-side events add no cookies or scripts to the scan page.
• Browser pixels are skipped in the European Economic Area, the UK, and Switzerland.
• Secrets such as access tokens are stored encrypted.

That privacy has a practical consequence for retargeting. Because server-side events do not identify the person, they are best for counting scans as conversions and seeing which codes perform. Adding a scanner to an ad audience depends on the browser pixels, so audiences only grow from scans outside the European Economic Area, the UK, and Switzerland.

How to set up QR code retargeting

1. Open UTM & Pixels in the dashboard and choose Create your first template. QRelix fills in the values most teams use.
2. Adjust the values, clicking placeholder chips to insert them. Turn on Default template, and Turn on for new QR codes if you want every new link code tagged automatically.
3. On an existing link code's Configure page, open UTM & Pixels, switch on Add UTM tags, pick a template, and check the example link before you save.
4. Under Pixels, connect GA4, Meta, or TikTok in server-side mode with the ID and secret from each tool.
5. Add browser pixels for the tools you want audiences in, such as Meta, TikTok, the LinkedIn Insight Tag, or Google Ads.
6. Click Test to send a test event. GA4 tests are validated without landing in your reports. For Meta and TikTok, paste the test event code from Events Manager to watch the event arrive under Test events.
7. Check the Activity tab. It lists the last 50 server-side events with their status. A send that fails retries for up to 10 hours, and the error from the provider (for example an expired access token) is shown in plain words.
8. In your ad platform, build an audience from the scan event, then target it with your next campaign.

The full reference is in the UTM & Pixels docs.

Worked example: a gym's flyer campaign

A local gym drops 5,000 flyers in nearby neighborhoods with a QR code that opens a free class sign-up page. The owner wants to know which neighborhood responds best, and wants to show Instagram ads to people who scanned.

The setup:

• One QR code per neighborhood, named north-side, riverside, and downtown.
• A UTM template with source qr, medium flyer, campaign spring-trial, and content set to {code_name}.
• Meta connected server-side with the Conversions API, plus the Meta browser pixel.

When someone scans the riverside flyer, they land on the sign-up page with utm_content=riverside in the link, so Google Analytics shows sign-ups by neighborhood. Meta receives the scan event from QRelix's servers, so the owner can count scans as conversions. Because the browser pixel also fired, Meta can add that scanner to an audience, and the owner runs a short Instagram campaign to people who scanned.

If the gym also uses Smart Routing to A/B test two sign-up pages, adding {variant} to the template makes every visit say which version sent it. For more campaign structure ideas, read QR campaign tracking.

Limits and when not to rely on it

• Scanners in the European Economic Area, the UK, and Switzerland are not added to audiences, because browser pixels are skipped there. Server-side events still count them.
• Audiences need volume. A handful of scans will not be enough for most ad platforms to run a campaign to.
• UTM tags apply to link codes. Templates are set on link QR codes from the Configure page.
• Secrets expire. If a provider token expires, the Activity tab shows the error in plain words, and you update the connection.

What QR code retargeting costs

See all plans on the pricing page.

• Free plan (no credit card): UTM tags on every scan, full scan analytics with CSV export, editable destinations, and the whole security suite. Each free code works for its first 50 scans, then pauses until you upgrade, and free scans show a brief QRelix screen before forwarding. Pixels and conversion events are not included.
• Pro, $5.99 a month or $59.99 a year: conversion pixels and server-side events, unlimited scans, no QRelix screen, Smart Routing, a Brand Kit, unlimited hosted pages, and priority support.
• Team, $19 a month with 3 seats: everything in Pro plus a shared workspace with roles, custom domains, bulk creation from CSV, and the developer API. Owners, admins, and editors can create templates and connect tools, and viewers can see them.

QR code retargeting FAQ

Can I add a Facebook pixel to a QR code?

Yes, on Pro and Team. Connect Meta under UTM & Pixels. You can send scans server-side through the Conversions API, load the Meta pixel in the browser, or both. Shared event IDs keep each scan counted once.

Are UTM tags added automatically?

Yes. Set a default template and turn on Turn on for new QR codes, and every new link code is tagged at the moment of each scan. This works on every plan, including Free.

Does server-side tracking slow down the scan?

No. The event is sent after the redirect, so scans are just as fast.

Is QR code retargeting GDPR friendly?

Server-side events use no cookies or scripts on the scan page and send no IP addresses, fingerprints, or contact details. Browser pixels are skipped for scanners in the European Economic Area, the UK, and Switzerland.

Which ad platforms are supported?

Google Analytics 4, Meta, and TikTok server-side, plus the LinkedIn Insight Tag, Google Ads conversions, and browser versions of GA4, Meta, and TikTok.

How do I know events are arriving?

Use Test on each connection, then check the Activity tab for the last 50 server-side events and their status.

Start retargeting your QR code scans

Create a UTM template on any plan today, then connect your ad tools on Pro or Team. Create a QR code, read the UTM & Pixels docs, or see how QR code tracking works end to end.