Skip to main content
QR Code Marketing

QR Code Marketing: From Print to Measurable Visits

6 min read Last updated 2026-11-17

A QR code turns any surface a person can hold or stand next to into a clickable moment. The mechanics are simple - the code encodes a URL and the camera opens a browser - so campaign success depends on the three things around the code: the offer, the placement and the destination page.

This guide walks through planning a QR campaign from first concept to print: choosing destinations that convert, writing calls to action, placing codes where scanning is physically comfortable, and testing everything before you commit budget to a print run.

Start with the destination, not the code

The code is a door; the room behind it matters more. A generic homepage wastes the scan, because the visitor has to find their own way to whatever the poster promised. The destination should match the context of the scan: a poster about one product should open a page about that product, and a menu code should open the menu. Since every scan happens on a phone, the page must load fast on a mobile network and render on a small screen.

Printed codes are permanent, so point them at URLs you control indefinitely. A stable path on your own domain - which you can update, redirect or redesign behind the scenes - gives you the editability that dynamic-code services sell, without putting a third party between your customers and your page. Choose a domain you intend to keep for years, because the printed artifact outlives almost every redesign.

Placement: make scanning physically easy

Scan distance dictates size. The working rule is that the code's width should be about one tenth of the distance from which it will be scanned, so a flyer read at arm's length needs only a few centimeters, while a poster meant to be scanned from three meters needs a code around thirty centimeters wide. Undersized codes are the most common printed-campaign failure, and they fail silently.

Place codes where people have a free hand and idle seconds: queues, tables, product shelves, receipts, packaging, waiting areas. Avoid surfaces behind reflective glass, walls in dark corridors, and anything a person would have to scan while walking or driving. Eye level or hand level beats floor level and ceiling level for obvious reasons.

Write calls to action that earn the scan

A bare code asks people to spend effort on a promise they cannot see. A short frame label with a specific benefit - 'Scan for the full menu', 'Scan to get your receipt', 'Scan for the size guide' - answers the only question that matters: what do I get? Specific beats clever, and short beats long, because the label is read at a glance.

The promise must match the destination exactly. A label that overpromises gets one scan and teaches the audience to distrust every code you print afterward. Consistency between the call to action and the landing page is the cheapest trust you will ever buy.

Matching code types to campaign goals

Different payloads serve different goals, and the payload should be chosen after the goal is clear. One code per surface and one job per code keeps both analytics and troubleshooting simple. The common pairings are straightforward:

The payload decides what happens after the scan, so choose it from the customer's next step rather than from whatever is easiest to print. Someone holding a menu needs the menu; someone opening a box needs the manual; someone walking past a window needs a reason to come in. When the payload matches that next step, the campaign works without any cleverness.

  • URL code: posters, flyers and ads, anywhere a landing page answers the scan
  • App store code: packaging and onboarding material that should end in an install
  • Social profile code: storefront windows and event banners chasing follows
  • WhatsApp or SMS code: service businesses where a conversation closes the sale
  • Calendar or location code: events, openings and pop-ups that need attendance
  • WiFi code: cafes and waiting rooms where guests appreciate instant internet

Test, print, then iterate on the page

Before printing, run a short checklist. Scan the code at final size and distance on both major phone platforms, under the lighting the surface will actually have. Check that the destination loads quickly on a mobile network rather than office WiFi, and print a proof on the final stock to catch ink spread and glare. Ten minutes of testing prevents a season of dead posters.

After launch, treat the code as fixed infrastructure and the landing page as the iteration surface. Give each printed surface its own path - for example /poster, /receipt, /flyer - and compare visits per path in your analytics to see which placements earn their ink. That is measurement without dynamic-code dependencies: the printed artifact never changes, while the content behind it improves continuously.

Key takeaways

  • The destination page matters more than the code: match it to the scan context and make it fast on mobile
  • Point printed codes at permanent URLs you control, then iterate on the page rather than the print
  • Size codes to scanning distance - roughly one tenth of the distance - and place them where hands are free
  • A specific call to action beats a bare code: tell people exactly what the scan gives them
  • Give each surface its own path and compare visits in analytics to measure placements without changing print

Put it into practice

Frequently asked questions