A/B Testing Your Print Marketing with QR Codes

Setting up the split

1. Build both landing pages first, fully, before touching the QR code. Variant A is just your link's normal destination; Variant B is a second, separate URL. Both need to actually be live and finished — testing against a placeholder page defeats the point.
2. Set the Variant B URL and a split percentage on the dynamic link's edit screen. The split percentage is the share of scans sent to Variant B — leave it at 50 for a straight even test, or skew it if you want to send most traffic to a favorite while still collecting some comparison data.
3. Change nothing else about the two pages except the one thing you're actually testing. A headline test where the two pages also have different images and different calls-to-action isn't a clean test of the headline — it's a test of everything at once, and you won't be able to say which change moved the number.
4. Print, distribute, and let it run. The split is enforced per scan on the server, so it holds up over real, uneven traffic — you don't need to do anything to keep it balanced.

Reading the results without fooling yourself

The tool gives you scan counts per variant, and that's genuinely useful for telling whether people scanned this code at all — but scan count alone doesn't tell you which variant performed better after the scan, since the platform doesn't do conversion tracking (see the honest breakdown on the analytics page). If the thing you actually care about is which variant converted better — more sign-ups, more purchases — that comparison has to happen on your own landing pages, with your own analytics on each one.

What this setup is genuinely good for: confirming the split itself is real and working as configured, and giving you a scan-volume baseline per variant to sanity-check against whatever your landing-page analytics report separately. Don't call a test decisive on a handful of scans either — a 6-4 split out of 10 scans is noise, not a result.

Frequently asked questions