The short answer
A QR code campaign puts a scannable code on a real-world surface — a menu, a poster, product packaging, an event ticket — so a phone camera turns a physical touchpoint into a digital action. The mechanic is simple: print the code, the audience scans it, and they land on the destination you chose. The craft is in choosing the right campaign type, sizing the code for the scan distance, testing it before the print run, and (if you pay for it) tracking the scans so you can iterate. The same code that worked on a table tent works on a billboard, only the size changes.
The one decision that shapes the whole campaign is static versus dynamic. A static QR code bakes the destination into the printed pattern — it is free, private, and scans forever, but you cannot change where it goes once it is printed. A dynamic QR code stores a short redirect link on a server you control, so every scan passes through that server before it lands — which means you can edit the destination without reprinting, and the server can count every scan. For a one-off print run a static code is the safe free default; for a campaign you want to track, A/B test, or repoint later, dynamic is the whole point. Our static vs dynamic QR guide and our qr code redirect guide cover the trade-off in detail.
Where QR codes fit a marketing campaign
A QR code is a physical-to-digital bridge, so it earns its place at the moment a customer is looking at something physical and you want them to do something digital: open a menu, watch a video, leave a review, claim an offer, install an app, RSVP to an event. That is the campaign in one sentence — a printed prompt that collapses a typed URL into a scan. The audience already has the scanner in their pocket (every modern phone camera reads QR natively), so the only friction left is putting the code where they are already looking and making it big enough to scan from where they stand.
Where QR codes do not help is anything that is already digital. A code on a website or in an email is wasted — the user is already online and a plain link is faster. QR codes win on physical surfaces, where the alternative is the customer typing a long URL by hand, which almost no one does. So the campaign planning question is always: which physical touchpoint has the most eyes on it, and what is the single highest-value digital action we want those eyes to take? Our what can a QR code do guide walks through the full set of actions a QR can trigger.
Campaign types that work well with QR codes
The campaign types that convert are the ones where the physical surface and the digital action are a natural pair. A restaurant menu printed on a table tent that opens the live menu page; product packaging that opens a how-to video or a authenticity check; a poster or flyer that opens a landing page or an offer code; an event ticket or wristband that opens a schedule or a check-in page; a receipt or a counter card that opens a review prompt; a social profile or a business card that opens a follow or a vCard save. The common thread is that the scan removes a step the customer would otherwise skip — and skipping it is exactly what kills conversion.
Each type has a size and placement implication. A table tent is scanned from about 30 cm, so a 3–4 cm code is plenty; a poster is scanned from 1–2 m, so the code needs to be roughly 10–20 cm; a billboard is scanned from across a room or a street, so the code can be a metre or more. The rule of thumb is the 1/10 scan-distance rule — the code width is about one tenth of the scan distance — and our qr code size guide has the full table. Match the campaign type to the surface, and the size to the distance.
Static vs dynamic QR codes for campaigns
This is the decision that determines whether you can track and repoint the campaign. A static QR code encodes the destination URL directly into the printed pattern, so the phone reads it and goes straight to the destination — no middleman, no server, nothing to count. It is free, it never expires, and it cannot be repointed: once the ink is dry the destination is fixed. If the landing page moves or the offer ends, every printed copy silently breaks. Static is the right default for a one-shot print where the destination is permanent, and for self-contained payloads like WiFi, vCard, or event codes that never touch the internet at all.
A dynamic QR code instead encodes a short redirect link (for example r.yourdomain.com/abc) that lives on a server you control. The phone scans the short link, the browser requests it, the server replies with a 301/302 redirect to the real destination, and the phone follows automatically — invisible to the scanner. Because every scan passes through that one server, two things become possible that a static code can never do: you can edit the destination later without reprinting (fix a typo, swap a lunch menu for dinner, rotate an A/B landing page), and the server logs every scan so you get campaign analytics. The trade-off is that a dynamic code is a dependency — if the redirect server goes down or the subscription lapses, every printed copy breaks at once — so point dynamic codes at a domain you own. Our qr code redirect guide explains the redirect mechanic, and our static vs dynamic QR guide lays out the full comparison.
The QR code campaign checklist
A campaign that scans is built from a short, repeatable checklist — skip a step and the usual suspects are what break it. First, set the goal: name the single digital action you want the scan to trigger (open a menu, claim an offer, leave a review), because that goal drives the destination, the copy, and the metric you will measure. Second, design for the channel: a table tent and a billboard are not the same code at the same size, and the surrounding copy has to tell the scanner what they get for scanning — a bare unlabelled code is scanned far less than one with a one-line prompt like "Scan for the menu".
Third, size the code for the scan distance using the 1/10 rule and our qr code size guide, and keep the quiet zone clear — nothing, not a border, not a caption, not a background photo, may touch the four modules of margin around the code. Fourth, test the printed proof before the full run: print one at final size on the final stock, place it where it will live, and scan it from the real distance on more than one phone, then run it through the validation pass in our qr code validation guide. Fifth, track the scans if the campaign warrants it (dynamic tier), and sixth, iterate — read the metrics, change one variable (the prompt, the placement, the destination), reprint or repoint, and measure again. Our qr best practices guide covers the scannability rules the checklist rests on.
Five campaign ideas at a glance
The table below gives five concrete campaign shapes you can copy, each with the surface it lives on, the action it triggers, and the one thing most likely to break it. Use it as a starting point and adapt the destination and the copy to your brand.
| Campaign | Surface → action | Watch out for |
|---|---|---|
| Restaurant menu | Table tent → live menu page (swap lunch for dinner via dynamic redirect) | Code too small to scan from across the table, or a static menu URL that goes stale |
| Product packaging | Box label → how-to video or authenticity check | Glossy laminate throwing a glare band; code printed below the 1/10 size for the shelf distance |
| Poster or flyer | Poster → offer landing page or discount code | No quiet zone because a caption or graphic touches the code; unlabelled code scanned less |
| Event ticket | Ticket or wristband → schedule, map, or check-in page | Code obscured by a perforation or fold; static link to a schedule that changes on the day |
| Review prompt | Receipt or counter card → review form (Google, Trustpilot, etc.) | Long review URL that makes a dense code; a destination that needs login the scanner will abandon |
The metrics that matter
If the campaign runs on dynamic QR codes, the redirect server logs every scan and you get the standard set of QR campaign analytics: total scans, approximate scans-per-day over the campaign window, unique scanners (a coarse, privacy-safe count not a person), approximate location (country and city, derived from the request, never a full IP), device and operating system, time of day, and referrer where available. The headline number is total scans — it tells you the code is being seen and used. The next-most-useful is the trend over time, which tells you whether the campaign is still alive or has gone stale.
The number that closes the loop is not a QR metric at all — it is the conversion on the destination page, measured in that page’s own web analytics. A scan is a leading indicator of interest, not proof of outcome: someone scanned, but did they buy, RSVP, review? Append a campaign parameter to the destination URL (for example ?utm_source=qr&utm_campaign=menu-spring) so the destination analytics can attribute the conversions back to the QR campaign, and compare scans to conversions to learn which surfaces and prompts actually pay. Our qr code tracking guide covers exactly what dynamic tracking can and cannot measure, and the privacy guardrails (minimise, aggregate, short retention).
How QRForge supports a campaign (and what to do next)
QRForge’s free generator builds the static code that anchors any campaign: pick the content type (a URL for most campaigns, or a vCard for business cards, or WiFi/event/SMS/email where the action is offline), style it to match the brand with colours, gradients, per-eye and per-module shapes, a centered logo with error-correction level H, and a frame with a caption prompt, then export SVG or EPS for print and PNG for screens. The generator renders the code live in the browser so you can scan-test the design before you commit it to a print run, and the free decode helper confirms the exported image round-trips to the exact payload.
For campaigns you want to track, repoint, or A/B test, the planned dynamic tier replaces the static destination with a short redirect link on a server you control, so every scan is logged and the destination stays editable without reprinting — the mechanic our qr code redirect and qr code tracking guides describe, and the one the paid tier is built around. Start with the static generator for the proof-of-concept print, decide whether the campaign needs tracking or repointing, and upgrade to dynamic only when that is the lever that moves the result. For the full design picture — contrast, logo, frame, and how they fit the print — see our qr code design guide and our qr code printing guide.
Frequently asked questions
What is a QR code campaign?
A marketing campaign that puts a scannable QR code on a physical surface — a menu, a poster, packaging, a ticket — so a phone camera turns that touchpoint into a digital action like opening a page, claiming an offer, or leaving a review. The craft is choosing the right campaign type, sizing the code for the scan distance, testing the proof, and tracking the scans if the campaign warrants it.
Should I use a static or dynamic QR code for a campaign?
Static for a one-shot print where the destination is permanent (free, scans forever, cannot be changed). Dynamic for a campaign you want to track, A/B test, or repoint later — the short redirect link is editable without reprinting and every scan is logged. Dynamic is a dependency (the redirect server must stay up), so point dynamic codes at a domain you own and keep static as the default for self-contained payloads like WiFi or vCard.
How do I track QR code campaign scans?
Only dynamic QR codes can be tracked, because every scan passes through the redirect server that logs it. The standard metrics are total scans, unique scanners, approximate location, device and OS, time of day, and referrer. To close the loop on outcomes, append a campaign parameter to the destination URL and read the conversions in the destination page’s own web analytics — a scan is a leading indicator, the conversion is the result.
How big should a campaign QR code be?
Big enough to scan from the distance your audience stands at — the rule of thumb is the 1/10 rule, where the code width is about one tenth of the scan distance. A table tent scanned from 30 cm needs a 3–4 cm code; a poster scanned from 1–2 m needs 10–20 cm; a billboard can be a metre or more. Keep at least a 4-module quiet zone clear around the code and scan-test the printed proof before the full run.