How to Get More Google Reviews with a QR Code — and Build an Ad Audience While You're At It

Asking for a Google review face-to-face works. Asking someone to "search for us on Google and leave a review" does not. The customer says "sure!", walks out the door, and never types your business name into a search box.

A QR code closes that gap. Point a phone camera, land directly on the "Rate and review" box, done in under a minute. That part is table stakes, and a dozen tools can print you a review QR.

What most businesses miss: the person scanning that code is a verified, real-world customer standing in your business. That's the highest-quality audience signal you will ever get, and most businesses throw it away. Route the scan through a page you control, fire a Meta pixel event, and every review ask also builds a retargeting audience and a lookalike seed. Same sticker, two jobs.

How the Google review link actually works

Google gives every business profile a direct review link. It looks like this:

Grab yours from your Google Business Profile: Google's instructions are to select "Read reviews", then "Get more reviews", and copy the short g.page/r/... link. You can also paste your Place ID from Google's Place ID Finder into the URL format above. The same screen offers a ready-made QR code on a computer browser; it is a static code that points straight at Google, with the limits described in the next section.

When a customer opens that link on their phone, Google pops the review dialog directly: star selector, text box, submit. There is no searching and no scrolling past competitors. For anyone signed into a Google account, it takes well under a minute.

One important constraint: you cannot put a tracking pixel on Google's review page. It's Google's property. If your QR code encodes the raw review link, the scan is invisible to you: you get no scan count and no audience. That constraint is why the routing setup below matters.

Static link vs. routed dynamic QR: what you give up with the "free" version

If you only want reviews, a static code works. But you're printing physical materials either way, and making every scan measurable and monetizable costs a few dollars a month. (More on the static vs. dynamic trade-off here.)

Where to place review QR codes (and what converts)

Placement is most of the game. The pattern that holds across restaurants, retail, gyms, and service businesses: catch people at the moment of completed satisfaction, not mid-experience.

The workhorses:

• Receipts. Printed at the bottom with one line: "Happy with us? Scan to leave a review." Cheap, automatic, reaches every paying customer. Lower conversion than a verbal ask, but unbeatable volume.
• Table tents and check presenters. For restaurants, the check presenter is prime real estate: meal done, phone already out. A table tent competes with the menu QR; the check wins.
• Counter cards at checkout. A small standing card next to the card reader, so staff can point at it while asking. Verbal ask plus zero-effort scan is the highest-converting combo.
• Appointment cards and follow-up packets. Salons, clinics, real estate, contractors: hand the card over at the end of a good appointment. For services with a delayed payoff, the card travels home and gets scanned when the result is felt.
• Packaging inserts. A thank-you card in the box (packaging QRs get scanned at the unboxing high point).
• Post-service email or SMS. Not a QR use case (just link it), but reuse the same routed landing page so every channel feeds one set of analytics and one audience.

Use a separate dynamic QR per placement: same destination, different codes. Within a month your dashboard shows whether the receipt or the counter card is doing the work. That's basic scan tracking discipline.

The audience layer: one scan, two outcomes

Instead of encoding the Google link directly, your dynamic QR points to a lightweight landing page you control: "Thanks for visiting! A 30-second Google review helps us a lot." One big button: Leave a review on Google.

On QRCodeStack, that scan fires a named Meta pixel event automatically. The default is QRScan, but for a review ask you'd set it to the standard Lead event. The event carries the QR's name, ID, and type as parameters (content_name, content_ids, content_category), so "Counter card, Main St" and "Receipt footer" show up as distinct signals in Meta Events Manager. Add a Conversions API token and the same scan is also sent server-side, deduplicated with the browser event, recovering the signal that ad blockers and iOS privacy settings would otherwise eat.

What that gives you in Meta Ads Manager:

1. A retargeting audience of verified customers. Build a custom audience from people who fired Lead from your review QRs. These aren't cold site visitors; every one of them physically stood in your business. Run loyalty offers, new-menu announcements, or referral pushes at them for pennies. Full strategy in our QR code retargeting guide.
2. A lookalike seeded from real customers. A lookalike built from scanners is modeled on people who actually bought, not people who bounced off your homepage in 4 seconds. Seed quality is everything, and this is about the best seed a local business can produce.
3. An exclusion audience. Suppress existing customers from acquisition campaigns and stop paying cold-traffic CPMs to reach people who already know you.

Honest caveat on audience sizes: Meta's documentation says a custom audience needs at least 100 people before you can build a lookalike from it, and a bigger seed gives the model more to work with. A single-location business won't get there in week one. That's the argument for starting now: the audience grows with every scan while you're busy collecting reviews.

(Pixel and CAPI tracking are on QRCodeStack's Pro plan and up, $19/mo. And scan pages never carry ads: the customer sees your page, not ours.)

Realistic math: what to expect

Illustrative numbers for a business doing ~2,500 transactions a month:

• Receipt QR reaches all 2,500. Passive placements convert weakly; assume 1–2% scan → 25–50 scans.
• Counter card with a verbal ask hits maybe 600 of those customers with ~10% scanning → 60 scans.
• Of ~100 total monthly scanners, 30–50% complete the review once they've landed on the Google dialog → 30–50 new reviews a month.

These are planning assumptions, so replace them with your own scan data after the first month. If you collect four reviews a month today, 30 a month changes your review count and recency within a quarter.

On the audience side, ~100 pixel events a month means the audience passes Meta's 100-person minimum for a lookalike seed in the first month or two and keeps growing after that, faster with multiple locations. None of those events cost anything in media spend.

Don't gate reviews (Google will eventually notice)

The tempting move: show a "How was your experience?" star widget first, send 4–5 stars to Google and 1–3 stars to a private feedback form. This is review gating, and it violates Google's review policies. Google's policy on user-contributed content tells businesses not to "discourage or prohibit negative reviews, or selectively solicit positive reviews from customers", and says Google will remove content that breaks it.

The compliant version: everyone gets the same Google review link. You can still ask "How did we do?" for your own analytics, and you can offer a private feedback channel alongside the review link, as long as the Google option is presented to everyone equally. Track ratings, fix the bad experiences operationally, but don't fork the destination based on sentiment.

Skip incentives too ("scan for 10% off and leave a review"). The same Google policy bars offering "payment, discounts, free goods and/or services" in exchange for reviews, and in the US the FTC's 2024 rule on reviews prohibits compensation conditioned on a review expressing a particular sentiment. The QR removes friction; that's the whole legitimate trick.

Setup playbook: 30 minutes end to end

1. Get your review link from Google Business Profile ("Read reviews" → "Get more reviews" → copy link).
2. Build the landing page: logo, one line of thanks, one prominent review button. Under 5 seconds of reading.
3. Create a dynamic QR in the QRCodeStack generator pointing at that page, one QR per placement, named clearly ("Review: receipts", "Review: counter").
4. Attach the pixel: set the Meta event to Lead (a standard event, so campaigns can optimize against it directly). Add your CAPI token if you have one, and save it as a reusable tracking profile for other locations.
5. Print and place: receipts, counter card, check presenters, appointment cards.
6. Brief the staff on one sentence: "If you enjoyed it, there's a 30-second review link on your receipt."
7. In Meta Ads Manager, build a custom audience from the Lead event, an exclusion audience for acquisition campaigns, and, once the seed is big enough, a lookalike.
8. Check the dashboard monthly: kill weak placements, print more winners, watch review velocity climb.

FAQ

Can I point a QR code directly at the Google review page?

Yes. A QR can encode the g.page/r/... link directly. But you can't measure or pixel anything on Google's page, so you get zero scan data and no audience. Routing through a page you control costs one extra tap and gives you both.

Is it against Google's rules to ask for reviews with a QR code?

No. Asking for reviews is explicitly allowed and encouraged. What's prohibited is review gating (steering only happy customers to Google) and offering incentives in exchange for reviews. Show everyone the same link and you're compliant.

How many scans do I need before the ad audience is useful?

Meta requires a custom audience of at least 100 people before you can build a lookalike from it, and larger seeds give it more to model. At around 100 scans a month you pass that minimum in the first month or two. Start collecting before you need it.

Do review QR codes work better than email requests?

They work differently. Email reaches only customers whose address you have; a physical QR catches everyone at the emotional peak of the visit, with a staff member able to point at it. Run both, and point both at the same routed landing page so all the data lands in one place.