What Is Meta Sync? Turn QR Code Scanners Into a Facebook & Instagram Ad Audience

Meta Sync (Pro plan and above) takes the leads sitting in your Lead Hub who specifically consented to ad targeting, and keeps a Meta Custom Audience — inside your own Meta Ads account, not SMLLR's — in sync with them, so you can run Facebook and Instagram ads at the actual people who scanned your QR codes. Connect your ad account once; from then on, whenever you click 'Sync Now,' SMLLR finds who's newly eligible and who's dropped off since the last run and pushes only that difference to Meta.

On its own, a QR scan is a one-time event — someone points a camera at a code on a menu, a poster, or packaging, lands on a page, and unless something captures them, that's the entire relationship. SMLLR's Lead Capture Gate already solves the first half of this by turning a scan into a stored contact in Lead Hub. Meta Sync solves the second half for a specific channel: instead of that contact sitting in a dashboard until you email them, Meta Sync makes them addressable inside Facebook and Instagram's ad platform too — so the person who scanned your table tent or packaging QR code can also see your ad the next time they open Instagram.

The mechanism is genuinely simple once you see the three steps. Segment: only leads who've granted the specific ad-targeting consent purpose in Lead Hub are eligible — not every captured lead automatically qualifies. Hash: SMLLR converts each eligible lead's phone number and email into a SHA-256 hash on its own servers before anything leaves — Meta never receives a raw phone number or email address, only irreversible hashes. Sync: those hashes are uploaded to a Custom Audience object that lives inside your own connected Meta ad account, where Meta matches them against its own user base to find the actual accounts. Nothing about this requires you to hand your Meta login to SMLLR or vice versa — see how the connection itself works for that part.

Worth being precise about, since it changes how you should use it: Meta Sync does not run on a schedule or refresh itself in the background. Every sync is a deliberate click on 'Sync Now' in the Audience tab. That's not a limitation to work around so much as a design choice that keeps a sync's cost predictable — each run only charges for the contacts actually added or removed since last time, and a sync where nothing changed costs nothing at all. In practice, most businesses fold a sync into an existing weekly or monthly routine — right after a batch of new leads comes in from a campaign, for instance — rather than needing it to happen invisibly on its own.

Meta Sync's job stops at keeping one Custom Audience accurate and current. Building a Lookalike Audience — where Meta finds new people who statistically resemble the people in your synced audience — happens natively inside Meta Ads Manager, using SMLLR's synced Custom Audience as the seed. This matters because it's genuinely the bigger opportunity: retargeting alone caps out at the size of your existing scanner base, while a lookalike built from real, consented scanners can reach people who've never touched one of your QR codes at all. See the full breakdown of retargeting vs lookalikes if that's the angle you're most interested in.

Ad targeting is tracked as its own distinct consent purpose in Lead Hub, separate from email marketing or WhatsApp consent. A lead who checked the box agreeing to receive marketing emails is not automatically eligible for Meta Sync — SMLLR's fixed consent checkbox names all three purposes explicitly ("I agree to receive WhatsApp messages, emails, and personalized ads from this business based on my activity"), and only a lead who actually checked it becomes eligible for any of the three, ad targeting included. If someone later opts out or is suppressed, the very next sync detects that and actively removes them from the Custom Audience rather than just excluding them from future adds. See what the consent requirement actually means in practice for the DPDP and Meta-policy side of this.

The pattern repeats across a handful of physical placements: a D2C brand's packaging QR code captures a warranty registration, and every buyer who consents becomes part of a retargeting audience for the next product launch. An event or trade-show booth code captures attendee leads, synced into an audience for post-event remarketing while the memory of the booth is still fresh. A retail counter or shelf-edge code feeds an audience that sees ads for exactly the product line it sat next to. In each case, the QR code is doing double duty — it was already capturing the lead for Lead Hub and Email Marketing, and Meta Sync turns that same consented lead into ad reach without asking the customer for anything a second time.

Meta Sync requires the Pro plan (₹4,999/month) or Premium (₹14,999/month), and draws from the same credit wallet Email Marketing uses — 1 credit covers 20 contacts touched in a single sync, added and removed both counting. Pro includes 100 credits a month, Premium includes 300. See the full credit math with worked examples for what that looks like at real list sizes.

Meta Sync is the third stop in a loop that starts at the QR code itself: a scan captures a lead through the Lead Capture Gate, a landing page, or CSV import; Email Marketing reaches whoever consented to email; and Meta Sync builds a Custom Audience from whoever consented to ad targeting — all reading from the same underlying Lead Hub record, with nothing re-captured or re-exported between channels. Start by creating a QR code with the Lead Capture Gate turned on, or head straight to Meta Sync's setup guide if you already have consented leads waiting.