QR Code Retargeting: How Every Scan Becomes a Meta Ads Audience (2026 Playbook)

QR code retargeting is the practice of firing a Meta pixel event when someone scans a dynamic QR code, so the scanner joins a custom audience you can advertise to later. It works only when the scan passes through a page you control. The funnel is: scan, named pixel event, custom audience, lookalike audience, campaign.

Why does the redirect page matter?

A pixel can only fire on a page you control, and a dynamic QR code's redirect is that page. A static code encodes the destination directly, so there is no owned surface to measure.

If the code points straight at a Google review page, an Instagram profile or an Amazon listing, you cannot add your pixel there. With a dynamic code, the event fires during the redirect and the scanner carries on to the destination. For review codes, do not use tracking data to show the link only to happy customers: Google's Maps content policy prohibits selectively soliciting positive reviews.

How do you set it up?

You need a Meta Pixel ID and a Pro or Business plan, since retargeting pixels are not part of Starter or the trial.

1. Create a code in the dynamic QR generator and set its destination.
2. Paste the Pixel ID into the code's tracking settings.
3. Pick the event fired on scan. QRScan is the default; Lead, Schedule and Purchase are options. A standard event can be an optimization goal directly; a custom one like QRScan first needs a custom conversion.
4. Name the code deliberately. The name travels as content_name, so "Spring-Menu-Table-Tents" filters better than "QR #7".
5. Scan it and watch Events Manager, Test Events. A typo in a pixel ID fails silently.
6. In Ads Manager, build a Website custom audience from the event, start at a 30-day window, and filter by content_name.

Which audiences should you build?

Four are worth the effort. Each uses the same scan events, sliced differently.

According to Meta's documentation, a lookalike needs a Custom Audience of at least 100 people. Matching is lossy, so plan for more scans. Add the pixel to every code you print, even if the campaign is a quarter away; an untracked print run cannot be backfilled.

Illustrative setup, not a customer result: a salon runs a window decal (Schedule, "Window-Book"), mirror stickers (QRScan, "Mirror-Review") and reminder cards (Schedule, "Rebook-Card"). It retargets "Window-Book" scanners with a first-visit offer and excludes the other two from acquisition ads, because they are already clients. See the salon guide and product packaging.

Does iOS signal loss break QR retargeting?

It weakens browser-side events. Since iOS 14.5, Apple's App Tracking Transparency requires apps to get permission before tracking, and QR traffic is almost entirely mobile.

Add a Conversions API token beside the pixel ID. Each scan is then also sent server to server, deduplicated against the browser event by a shared event ID. Our Conversions API guide covers it, and the scan analytics guide covers GA4 and UTMs.