How to Build a Facebook Custom Audience From In-Store Foot Traffic
A step-by-step guide to turning in-store QR scans into a Meta Custom Audience you can retarget — from placing the code to launching the campaign.
By The QRs.bd Team · June 2, 2026 · 6 min read
A Meta Custom Audience built from real foot traffic is the closest a physical store gets to the retargeting superpower online shops take for granted. Here's exactly how to build one from in-store QR scans, end to end.
Step by step
- Get your Meta Pixel ID: in Meta Events Manager, open your pixel (or create one) and copy its numeric ID. If you'll also use Conversions API, generate an access token while you're there.
- Connect it to your QR workspace: in QRs.bd, add the Pixel ID under your workspace retargeting settings and turn the master switch on. Agencies can set this once and reuse it across the stores they manage.
- Enable retargeting on a code: pick an in-store QR — your menu, Wi-Fi, or daily-special code — and switch retargeting on for it. Leave consent on region-gate to skip EU/EEA/UK visitors by default.
- Place the code where people pause: a counter card by the till, a table tent, a sign for today's special. Scans happen where attention lingers, so position it at the moment of interest.
- Let the audience build: every eligible scan passes through the hand-off page, fires your pixel, and adds that browser to your audience. Give it a week or two of normal traffic to accumulate volume.
- Create the Custom Audience: in Ads Manager, choose Audiences → Create Custom Audience → Website (your pixel), and define it by the scan event or all pixel activity over your chosen window.
- Launch the campaign: run a tight offer to that audience — 'come back this weekend', a loyalty perk, a new-arrivals teaser. Because everyone in it physically visited, your relevance and return are high.
How big does the audience need to be?
Meta needs a minimum audience size before it will serve ads to a Custom Audience (typically around 100 matched people, often more in practice). A busy café or shop clears that in days; a quieter store may need a few weeks. Keep the code in a high-traffic spot and be patient — the audience compounds.
If you're below the threshold, widen the time window of the audience definition (e.g. 180 days instead of 30) so more past scanners are included, and keep the code working across all your locations.
Frequently asked questions
How do I create a Custom Audience from a QR code?
Connect your Meta Pixel to your QR tool, enable retargeting on an in-store code, and let scans fire the pixel. Then in Ads Manager create a Website Custom Audience from that pixel's activity and target it.
How many scans before I can run ads?
Meta generally needs around 100+ matched people in a Custom Audience before it serves ads. A high-traffic location reaches that in days; a quieter one may take a few weeks, so keep the code well placed.
Do I need a Conversions API token too?
It's strongly recommended. The browser pixel alone misses visitors who block tracking; a server-side Conversions API event with a shared event ID captures them and de-duplicates against the browser event.
Can an agency reuse one pixel across clients?
Each store should use its own client's Meta Pixel so the audience builds in the right ad account. Set the pixel per workspace (or per code) so every client's audience stays in their account.
Ready to put this into action?
Set up in-store retargeting →We build QRs.bd — the workspace for branded QR codes, short links and scan analytics. We write about what we learn shipping it and watching how real businesses use codes in the wild.