Put a QR code in an ad when someone can safely pause, scan it and get something useful immediately. A poster beside a workshop entrance might offer the schedule. A flyer could open a booking page. A code on an ad watched from a moving car asks for the wrong action at the wrong moment.
The useful question is whether the code helps the person who sees this particular ad. Decide that before choosing colors, a generator or a scan target.
What September's QR stories actually tell us
On September 16, 2026, Campaign Middle East reported on GymNation's “Break Glass” activation. Street-level installations offered a three-day gym trial through a QR code. The report described more than 2,678 scans in the first 48 hours and a 67% increase in new membership leads compared with the same period a year earlier. It also described press coverage, social distribution and CRM follow-up.
Those are reported campaign figures, not independently audited results or a controlled test of adding a QR code. The useful detail for a smaller campaign is the clear next action: claim a trial. A scan, a lead and a paid membership were different stages; the article does not establish that the code alone caused the reported lead increase.
There is a wider context, too. Bitly's September 10 QR Code Trends Report says it analyzed 1.9 million codes created across Bitly and QRCG by Bitly in the first half of 2026. It reports 6.2% year-over-year growth in scan volume and substantial variation across industries. These are observations from that provider's population, not a universal scan-rate target or evidence that every placement works.
Together, the stories suggest a useful planning question: what job should this code do, and what evidence would show that it did it? The checklist below is our editorial guidance, checked against those sources on September 22, 2026. It is not a 302.sh advertising experiment.
Choose the placement before the code
Scroll the table horizontally to compare placements and next steps.
| Where the ad appears | Decision to make | A useful next step |
|---|---|---|
| Counter, waiting area or event stand | Can someone stop without blocking a queue or walkway? | Open the menu, session schedule or a specific offer. |
| Take-home flyer or direct mail | Will the promise still be available when the reader opens it later? | Show booking availability or the advertised information, with a readable web address as an alternative. |
| Street poster | Is there a safe viewing position, readable distance and enough light? | Test from that position before printing a large batch. |
| Television or presentation screen | Can viewers read the message and use a second device before it disappears? | Keep a memorable web address available and rehearse the timing on the actual screen. |
| Ad on the viewer's phone | Does the placement support a tappable link or button? | Prefer that direct route; do not assume everyone can scan the screen they are using. |
| Roadside ad aimed at drivers | Would the action invite phone use while driving? | Do not ask drivers to scan. Design for later recall instead. |
These are starting decisions, not measured rankings. A code that reads reliably at a desk can fail behind reflective glass, on a curved surface or at the distance where the audience actually stands.
Write the promise next to it
“Scan me” explains the mechanism. “See today's workshop times” explains the benefit. Use a specific, accurate promise that the destination fulfills without making the visitor search again.
- For a trial: show who qualifies, what is included, any expiry and what happens after the trial.
- For a download: say what the file contains and disclose a required sign-up before the visitor starts.
- For a booking: open the relevant location or event, with current availability and terms.
- For information: make the answer readable on a phone without requiring an unrelated account.
Keep the brand and a readable address near the code. Offer another route when scanning is difficult or inaccessible. A branded domain can make the address easier to recognize, but branding alone is not proof that a destination is safe.
Decide who will maintain the destination
If you already control a stable page and need no separate entry report, its direct URL may be enough. A managed short link is useful when you need to update a printed destination later or keep placement-level entry reports. Name an owner and decide what visitors should see after the offer ends.
In 302.sh, an account-owned short link gives you a maintained entry address. See our existing destination-change test for the edit workflow and what can make a QR code stop working for its dependencies. Check the original printed code again after an edit. This article does not include a new physical scan test.
Choose what would justify keeping the code
Before launch, write one success statement, such as “help people book this workshop.” Identify the system that can confirm bookings. A redirect report shows recorded requests; the booking system establishes completed bookings. Neither count alone establishes that the ad caused an additional sale.
If comparing placements, use separate entry URLs and the same reporting window. Printing the same QR everywhere combines those entries. The UTM guide covers destination tags, and our QR visits versus GA4 sessions guide explains why the resulting reports count different things.
More scans do not automatically make one placement better. A counter visited all week and a flyer handed out for one afternoon have different opportunities to be seen. If you do not have a credible exposure count, report requests and confirmed outcomes without inventing a scan-through percentage. Copies printed are not people who saw the ad.
For a small pilot, keep the offer and destination stable and document differences in audience, distribution and staff test activity. That comparison is still observational. A claim that adding a QR code increased outcomes requires a suitable comparison group and an experiment designed around that question. If the ad's goal is later brand recall, immediate scan counts alone cannot tell you whether it succeeded.
Make a go, revise or remove decision
Use this short review before committing to a print run or approving a screen placement. A passing scan test is necessary for a scannable ad, but it cannot establish campaign effectiveness.
- Check the moment. Describe where the viewer is and what they are doing. If the action would be unsafe or impractical, remove the scan instruction or move the placement.
- Test the final output. Use a print proof or the actual display at its real size, viewing distance, angle and lighting. Try representative phones. If it cannot be read reliably, revise the artwork or placement before approval.
- Follow the full path. Open the code using the connection available there and, where appropriate, without the owner's signed-in session. Check the final page, offer, location and expiry. Decoding alone is not a completed visit.
- Try the alternative route. Confirm that the readable address or supported tappable link works too. If scanning is the only route, decide how people who cannot use it will get the information.
- Assign an owner and a review date. Record who will maintain the destination and where completed actions will be counted. Leave untested stages explicitly marked “not tested.”
Copy this decision record for each proposed placement:
Placement and audience:
Viewer's safe stopping point:
Promise printed next to the code:
Final destination and alternative route:
Actual-size scan/open check: pass / fail / not tested
Completed action and reporting source:
Destination owner and next review date:
Decision: include / revise / remove
Reason:For example, a workshop poster in a waiting area might pass the stopping-point check and offer a relevant booking action, but still need revision if the page requires the organizer's login. A phone-feed ad with a supported booking button may need only that button. These are planning examples, not measured campaign results.
A QR code earns its place when it gives an interested person a useful route forward. Start with that route, make it accessible in the real placement, and judge the result against the action you intended.
What is included in 302.sh?
Free allows 5 new links per UTC month and up to 50 owned links, with 5 custom slugs per month of at least 6 characters. Deleting a link does not refund its monthly creation allowance.
Free includes 2,000 analytics events per month and 90-day retention. Reaching that analytics allowance stops additional tracking, not redirects. Link deletion, owner-set limits and safety enforcement can still stop redirects. Branded domains require a paid plan and completed domain setup. See current plans and limits.
Try the workflow
Explore the dashboard demo, or create a short link using a destination you own or are authorized to share. Verify the destination before distributing it.