How many rounds can I track for free?

3 dynamic codes are free across the whole account. A fourth round, or a fourth code anywhere else on the account, needs Pro.

Should I compare raw scan counts between rounds?

No. Divide scans by leaflets delivered per round (scans per thousand) since round sizes rarely match, and a bigger round will always out-scan a smaller one on raw numbers alone.

Can I tell if a distributor actually delivered a round?

Not from scan data alone. A quiet round can mean under-delivery rather than disinterest. Ask for delivery proof before writing off a round that underperforms badly.

What if I run the same round again next month?

Give the repeat its own code and utm_content, for example round-sw-repeat, so this month's numbers don't blend into last month's.

QR Codes for Leaflet Drops: Which Round Actually Pulled

Create a QR code

QR codes on leaflet drops, one code per round or postcode batch

Ten thousand leaflets go out across six postcode rounds, delivered on different days by different distributors, and the print run itself tells you nothing about which round worked, only that ten thousand leaflets exist somewhere. A single QR code on the leaflet gives you one blended scan count for the whole drop. Split the print by round or postcode batch instead, give each its own dynamic code, and the same leaflet starts answering a real question: which rounds are worth repeating, and which distributor's drop is actually landing.

There's no tool that plans the drop for you

What works today is generating one dynamic code per round or postcode batch in the bulk generator, each with its own UTM-tagged destination, and printing that round's number onto that batch's print file. It's a manual split you set up once per campaign, described below, not an automated planner.

The split here is the round, not the creative

The same leaflet, same headline, same offer, goes out everywhere. What differs between codes is which postcode round or delivery day it landed in, so the tag that varies is a round identifier, not a creative name. That's a narrower job than comparing two designs against each other: it isolates geography and delivery quality as the variable, not the artwork.

By postcode sector, so round 1 covering one set of streets can be compared with round 2 covering another
By delivery day, when one distributor delivers a large drop over several days
By distributor, when more than one agency is used and you want to compare delivery quality
By repeat drop, so a rerun to the same postcodes next month doesn't get blended into this month's numbers

Building the UTM and code set for a multi-round drop

Keep utm_source, utm_medium and utm_campaign identical across every round, and vary only utm_content to identify the round. A five-round drop looks like this in the destination URLs:

Round 1 (SW): https://example.com/offer?utm_source=leaflet&utm_medium=door-drop&utm_campaign=spring-drop&utm_content=round-sw
Round 2 (SE): https://example.com/offer?utm_source=leaflet&utm_medium=door-drop&utm_campaign=spring-drop&utm_content=round-se

Round	Area	utm_content	Label
1	SW postcodes	round-sw	Leaflet - SW
2	SE postcodes	round-se	Leaflet - SE
3	SW repeat (month 2)	round-sw-repeat	Leaflet - SW repeat
4	Distributor B, SW	round-sw-distb	Leaflet - SW (Distributor B)

Printing the split without a different design per round

The artwork stays identical across rounds; only the code image and its destination differ, so order print in per-round batches matching the actual door count on that round rather than splitting a total evenly. Paste the labelled list of destination URLs into the bulk generator, generate the batch as dynamic codes, and keep them together in one folder in the dashboard so the drop stays legible as a single campaign.

Read scans per thousand delivered, not raw scans

A round of 4,000 doors will out-scan a round of 1,500 doors even if the smaller round actually converts better. Get the door count per round from the distributor, then divide scans by leaflets delivered (per thousand) before comparing rounds. Comparing raw counts across rounds of different sizes is the single most common way this test gets misread.

Running a split leaflet drop

1
Get the door count per round
From your distributor, before you order print, so you can normalise scans later.
2
Tag one destination URL per round
Same landing page and utm_campaign, a different utm_content identifying the round.
3
Generate one dynamic code per round
In the bulk generator, labelled by round so the print file and the dashboard match up.
4
Order print in matching per-round batches
So each round's leaflets carry that round's code, not a shared one.
5
Compare scans per thousand doors, not raw counts
Once every round has had the same number of days to land.
6
Keep the round codes in one folder
So the drop stays together in the dashboard rather than scattered through everything else you've printed.

What a scan does and doesn't tell you about a round

A scan means someone in that round picked up the leaflet and scanned it. It says nothing about people who read the offer and typed the web address instead, or searched for you rather than scanning, both of which are invisible here. A quiet round could also mean the distributor under-delivered it rather than the area being uninterested, so before writing off a round's postcodes, ask for delivery proof if the gap against other rounds is large.

Comparing rounds over time, and what plan that needs

Because each round is its own code, Free's headline count, daily series and country breakdown over a 7-day window apply per round, which is enough for a small drop. Free includes 3 dynamic codes in total across your whole account, not per drop, so a drop split into more than three rounds needs Pro (£9/month) from the outset. Pro also adds device, referrer, region and town/city detail, useful for checking whether scans genuinely cluster in the round's own postcodes.

No, only a different destination behind the code. Keep one artwork file and swap the code image per round's print file.

Part of Campaign & print attribution