Measuring QR code ROI
Connect physical touchpoints to analytics so you know which placements and creatives earn their cost.
Dynamic vs static
To count scans over time and compare placements, you generally want dynamic QR codes. The printed pattern points at a short link you control; the redirect can log the scan before sending people to your final URL. Static codes embed the destination directly, which is fine for simple use cases but gives you no server-side scan log on qrqr.fyi.
1. Use UTM parameters
Add UTM (or your analytics tool's equivalent) query parameters to the final destination URL. Example shape:
https://example.com/summer-sale?utm_source=print&utm_medium=poster&utm_campaign=summer26&utm_content=downtown
That way, traffic from scans shows up with clear attribution in Google Analytics or similar tools, and you can follow post-scan behavior such as time on site and conversions.
2. Define conversion goals first
Decide what success means before you celebrate scan counts. Examples:
- Leads: form fills, demo requests, newsletter signups
- Revenue: purchases, coupon redemptions
- Engagement: app installs, video plays, follows
A simple ROI formula
Example: $500 in print spend and $1,500 in sales attributed to those codes gives (($1,500 - $500) / $500) × 100 = 200% ROI. Use numbers your finance team agrees count as "from scans."
3. Compare placements
Use separate dynamic codes (or separate UTM content values) per placement: one poster route, one transit stop, one product line. Scan counts and downstream conversion then show which locations justify more budget. Location signals from analytics are often approximate (for example derived from IP), so treat them as directional, not exact GPS.
4. Scan-to-conversion rate
High scans with weak conversions usually point to the landing experience, not the QR itself. Mobile-first layout, fast load, and a message that matches what the user expected from the poster usually beat chasing more scans alone.