QR Code Retargeting: Fire Meta Pixel, Google Ads & GA4 on Every Scan

Tracking Pixels (Pro plan and above) let you attach your own Meta Pixel, Google Ads Conversion ID, GA4 Measurement ID, LinkedIn Insight Tag, and/or Microsoft Ads UET Tag to a QR code, so every scan fires a standard page-view/conversion event on that platform automatically — the same way a website visit would. Set the IDs once as an account-wide default, or override any subset per individual QR code, from the Pro plan upward.

Meta, Google, and LinkedIn's ad platforms build retargeting audiences and measure conversions from events fired on pages they can see — normally a website with their pixel installed. A physical QR code scan happens outside a website entirely; without something firing the equivalent event, that scan is invisible to every ad platform's own optimization and retargeting logic, no matter how many people actually scanned. Tracking Pixels closes that gap by firing the event on SMLLR's own redirect page, the moment between the scan and the destination, using IDs you already have from your existing ad accounts.

When a tracking pixel ID is configured for a QR code, SMLLR's redirect page loads the corresponding platform script and fires its standard page-view-equivalent event before continuing to the actual target URL: Meta Pixel fires PageView, Google Ads and GA4 share one gtag.js loader (Google unifies both under the same script, so loading it twice would double-count), LinkedIn's Insight Tag fires its automatic page-view event, and Microsoft's UET tag fires pageLoad. All of this happens automatically on every scan — there's no separate "fire pixel" step to configure per campaign once the ID is set.

Most businesses only run one Meta Pixel, one GA4 property, and so on — so Tracking Pixels supports setting each platform's ID once as an account-wide default in Settings, and every QR code inherits it automatically. When a specific campaign needs a different pixel — a franchise location with its own ad account, or a product line tracked separately — any individual QR code can override any subset of the defaults without touching the account-wide setting. Both the account defaults and the per-QR overrides are available from the Pro plan upward — there's no separate, higher tier required just to override a default on one QR code.

It's easy to conflate Tracking Pixels with Meta Sync, since both feed Meta's ad platform from a QR scan — but they're solving different problems. Tracking Pixels fires a standard PageView event on every scan, with no lead capture involved and no consent gate required, feeding Meta's own pixel-based tracking and any retargeting audiences built from pixel events inside Ads Manager. Meta Sync is narrower and more deliberate: it only syncs Lead Hub contacts who explicitly consented to ad targeting into a Meta Custom Audience, as a manual 'Sync Now' action. In short, Tracking Pixels is the passive, always-on signal; Meta Sync is the active, consent-gated one. Many businesses use both — Tracking Pixels for baseline platform-side retargeting signals, Meta Sync for a precise, consented audience list.

A retail QR code on packaging or a shelf display fires a Meta Pixel PageView on every scan, feeding a standard Meta retargeting audience of "people who scanned this product" without any lead-capture step in between. An event or trade-show booth QR code fires Google Ads and GA4 events, letting a team measure booth-driven traffic inside the same Google Ads dashboard they already use for paid campaigns. A B2B company running LinkedIn ads attaches its Insight Tag to a QR code on a printed brochure or a booth banner, so scans contribute to the same LinkedIn conversion tracking their digital campaigns already report against.

Tracking Pixels, including per-QR overrides, are available on SMLLR's Pro plan (₹4,999/month) and above — the same plan that includes Webhooks, Meta Sync, and Email Marketing. No per-platform add-on charge; configure as many of the five platforms as apply to your business.