QR Code Campaign Naming: A Convention That Keeps Reports Clean

15 November 2026QR Code Campaign Naming: A Convention That Keeps Reports Clean

QR Code Campaign Naming: A Convention That Keeps Reports Clean

Sketches framing a QR campaign naming title

A QR code campaign name is the label that tells you, months after printing, which code produced which scans. Use one fixed format, built from the same few fields every time: year, channel, campaign, placement and version. Keep it in a shared sheet, and attach it to dynamic codes so every scan lands in your reports under a name your whole team recognises. In QRlytics you can set that name on each code and change the destination later without reprinting.

Qrlytics
qrlytics.app
Keep QR Campaign Reports Clear
Create branded dynamic QR codes, update their destinations later, and use real-time analytics to understand campaign performance.
Visit

TL;DR

  • Name each code with a fixed pattern: year, channel, campaign, placement, version. Lowercase, hyphens, no spaces.
  • Give the code name and the UTM campaign value the same root so scan data and website data line up.
  • Keep a single naming sheet with an owner. A name that is not in the sheet does not get printed.
  • Never rename a printed code’s meaning. Change the destination of a dynamic code and bump the version instead.
  • Add placement detail (store, table, poster position) to the name so you can see which physical spot works.

Table of Contents

  • Why campaign names matter more for QR codes than for links
  • Campaign name, UTM value and attribution: three different jobs
  • What a QR code campaign name should contain
  • Worked examples for print, packaging, retail, hospitality and events
  • Build the naming sheet before you build the codes
  • Connecting names to reports and teams
  • Common naming mistakes and how to avoid them
  • Where QRlytics fits
  • Our view on naming
  • FAQ
  • Sources

Why campaign names matter more for QR codes than for links

A digital ad can be edited tomorrow. A QR code on 20,000 flyers, a shelf talker in 40 stores or a banner at a trade show cannot. Whatever you call the code on the day you create it is the label you will read in every report for as long as the print is in circulation.

That is where untidy naming does its damage. Picture a spring promotion where one person called a code Spring Sale Flyer, another spring_flyer_v2 and a third SPRING FLYER NEW. A quarter later your report shows three campaigns when you ran one, and nobody can say which version of the flyer drove the scans.

A good convention gives you three things:

  1. Comparable results. Codes with the same structure can be sorted, filtered and grouped.
  2. Handover that works. A colleague, or an agency picking up the account, reads the name and knows what it is.
  3. No duplicates. Before creating a code you check the sheet, so you reuse the existing name rather than invent a new one.

If you want the wider picture of what to measure once names are in place, our QR code tracking guide for marketers covers the metrics, and the campaign sheet and analytics walkthrough covers reporting.

Campaign name, UTM value and attribution: three different jobs

The most common confusion is treating the campaign name as if it were the attribution data. They are related but not the same.

  • The QR code name is your internal label in the QR platform. It identifies the physical item: this poster, this box, this menu.
  • The UTM parameters are tags added to the destination URL so your web analytics can say where a visit came from. Google Analytics lists utm_source, utm_medium and utm_campaign as the parameters to always use, and treats utm_content and others as optional extras.
  • Scan analytics are what the QR platform records when the code is scanned: time, location, device and so on.

The naming convention is what ties the three together. If the code is called 2027-print-springsale-flyer-a and the UTM campaign is springsale, you can move between the QR report and the web report without guessing.

A useful division of labour for the UTM fields:

UTM field What it holds for a QR code Example
utm_source Where the code physically lives flyer, shelf-talker, table-tent
utm_medium A stable channel bucket qr or print-qr
utm_campaign The business initiative springsale
utm_content Placement or variant window-a, v2

Keep utm_medium the same for every code so all QR traffic groups together in your reports. Our guide to avoiding unattributed direct traffic with UTMs on QR codes walks through the four moves to set this up.

One rule saves hours: Google Analytics states that parameter values are case sensitive, so Flyer and flyer are counted as two different sources. Write everything in lowercase and the problem disappears.

What a QR code campaign name should contain

Resist the urge to cram in everything. Five fields are enough for most teams, and each one answers a question someone will ask later.

Field Question it answers Example values
Year (and quarter if useful) When did this run? 2027, 2027q1
Channel What kind of material is it? flyer, poster, packaging, menu, badge
Campaign What business goal does it serve? springsale, loyalty, launch-x
Placement Where exactly is it? store-014, table, window, back-cover
Version Which creative or destination variant? a, b, v2

Join them in that order with hyphens: 2027q1-poster-springsale-window-a.

Why this order

Put the field you will filter by most first. Year first keeps old campaigns together when you archive. Channel second lets you compare all posters against all flyers. Campaign third groups the work. Placement and version come last because they change most often.

Format rules worth writing down

  • Lowercase only.
  • Hyphens between fields, no spaces, no underscores mixed with hyphens.
  • No special characters or accents, because they get encoded in URLs and show up as odd strings in reports.
  • Fixed abbreviations from a short list, not free choice. If store is st in one name and shop in another, filters fail.
  • Keep it short enough to read in a report column, around 40 characters at most.

A small point that pays off: do not put prices, discount amounts or dates of offers in the name. Offers end, but the printed code may stay in circulation. springsale is still true in July; 20off-until-march is not.

Worked examples for print, packaging, retail, hospitality and events

Names only prove their worth when you apply them to real situations. Each of these uses the same five fields.

Print and direct mail

A publisher puts a code on the back cover of a catalogue and another inside on the order page.

  • 2027-catalogue-autumn-backcover-a
  • 2027-catalogue-autumn-orderpage-a

The campaign and channel are identical, so you see them together. The placement tells you which spot earns the scans, and that decides where the code goes in next year’s edition.

Packaging

A product code is printed on thousands of boxes before it is shipped, which makes this the hardest place to fix a mistake.

  • 2027-packaging-registration-box-v1

Here the version field is the useful one. If you later point the code to a new registration page, you keep the same printed code and record the change in your sheet. Dynamic codes let you update the destination without touching the print, which is the reason packaging should never carry a static code for anything you may want to change.

Retail

A retailer runs a shelf-talker in 40 stores and wants store-level results.

  • 2027q2-shelftalker-summerrange-store014-a
  • 2027q2-shelftalker-summerrange-store022-a

One code per store lets you compare locations directly. If the same code appears everywhere you can still see scan locations on a map, but separate codes give you clean, countable totals per store.

Hospitality

A restaurant group puts codes on tables, takeaway bags and the front window.

  • 2027-menu-brunch-table-a
  • 2027-bag-loyalty-takeaway-a
  • 2027-window-reservations-frontdoor-a

Three different goals, three different campaigns, one readable pattern. A manager who has never opened the sheet can tell what each code does.

Events

An organiser prints badges, signage and a programme for a conference.

  • 2027-badge-summitregistration-attendee-a
  • 2027-signage-summitfeedback-exit-a
  • 2027-programme-summitagenda-insidecover-a

For a recurring event, put the edition in the campaign field (summit27) so next year’s codes do not collide with this year’s.

Build the naming sheet before you build the codes

A convention that lives in one person’s head fails when that person is on holiday. Write it down in a single sheet with two tabs.

Tab 1: the rules. The five fields, the allowed values for channel and placement, the format rules and the name of the person who approves new values.

Tab 2: the register. One row per code:

Column Purpose
Code name The exact name in the QR platform
Owner Who answers questions about it
Destination URL Where it currently points
UTM campaign value The tag used in analytics
Print run and date Quantity and when it went out
Status Planned, live, retired
Notes Changes to the destination and why

The register is the part that most teams skip, and it is the part that answers the question you will get in six months: why does this code send people to that page?

Who owns it

Give one person the keys. They do not need to create every code, but nothing is printed until its name is in the register. That one rule prevents most naming drift.

Updating without breaking history

Names are labels for reporting, so keep them stable once the code is printed. If a campaign changes direction, do not rename the code to match. Point the dynamic code to the new destination, record the change in the Notes column and, if the change is large enough to need separate reporting, increase the version. Because the code itself does not change, the printed material keeps working.

You can pair the sheet with the lifecycle of each code. Retire codes when a campaign finishes by marking them in the register, so nobody reuses an old name by accident.

Connecting names to reports and teams

Once naming is consistent, reporting becomes a filter rather than a clean-up job. Filter by year to see a season, by channel to compare flyers with posters, by placement to see which spot works.

Three filters for organizing QR campaign reports

If your team also measures earned coverage and PR, the same discipline applies there, and a practical earned media tracking setup shows how a shared naming scheme keeps results comparable across teams. For broader reporting habits, the same logic of one shared vocabulary underlies marketing analytics that improve return.

In Google Analytics the campaign value you tag appears as the manual campaign name dimension, and Google recommends that if you set one UTM parameter you set all the relevant ones, especially source, medium and campaign. That is another reason to keep the UTM campaign in the same family as the QR code name.

Common naming mistakes and how to avoid them

  • Mixing cases and separators. Spring_Flyer and spring-flyer become separate rows. Fix: one format rule, lowercase and hyphens.
  • Naming after the creative. blue-poster means nothing next year. Name the purpose, not the look.
  • Reusing a name for a new purpose. The report then merges two unrelated results. Fix: a new version or a new campaign value.
  • Putting the date of an offer in the name. The code outlives the offer.
  • Too many fields. Ten-part names get abbreviated differently by each person. Stay at five.
  • One code for everything. If the same code goes on a flyer, a poster and a bag, you cannot tell which drove the scan. Use one code per placement when the answer matters.

When you scale to many codes, a spreadsheet gets heavy to maintain by hand. Our article on scaling QR code campaigns without reprints and the one on QR API integration cover creating and naming codes in bulk from the same list you already keep.

Where QRlytics fits

Where QRlytics fits

A naming convention only helps if the codes behind it stay alive and editable. QRlytics creates dynamic QR codes whose destination you can update after printing, with real-time scan analytics, CSV export of that data and an API for developers. Codes created during an active subscription keep working, so the name you gave a printed code remains meaningful for as long as the print is out in the world.

You can start on the Free plan, which has limited codes and analytics, and no credit card is needed to sign up. Paid plans (Pro) unlock unlimited codes, advanced analytics and API access; see the pricing page for the details. To try the naming format on your first code, open the dynamic QR code generator.

Qrlytics

If you already have printed codes with inconsistent names, start by listing them in the register and apply the convention from the next print run onward.

Our view on naming

We think a QR code name is a promise to your future self. When you print a code, you are committing to a piece of paper that cannot be edited, so everything that can be edited should be tidy and documented.

That is why we build around permanence and control. A code created during an active subscription keeps working, and a dynamic code lets you change where it points. With the destination flexible and the name stable, the only thing left to get right is the label, and a five-field convention is enough to get it right.

Our advice to marketing teams is simple: decide the format once, write it down, and give one person ownership. Pair each name with a UTM campaign value, and your scan data and your web data tell the same story.

*The

FAQ

What is a good name for a QR code campaign?

One that tells a stranger what the code is without opening it. A pattern such as 2027q1-poster-springsale-window-a gives the year, channel, campaign, placement and version in lowercase with hyphens. It sorts well, reads well and survives handover.

Should the QR code name match the UTM campaign?

They should share a root, not be identical. The code name carries the placement and version, while the UTM campaign holds the business initiative, such as springsale. Sharing that root lets you move between the QR report and your web analytics without guessing.

Can I rename a QR code after printing?

The label in your dashboard can be changed, but it is better not to. Reports are easier to read when a name keeps one meaning. If the purpose changes, update the destination of the dynamic code, note it in your register and raise the version number.

Do I need a separate code for every placement?

When you want to know which placement works, yes. A separate code per store, table or poster gives you clean totals per spot. If you only need the campaign total, one code is enough, and scan location data still shows where people scanned.

Sources

  • URL builders: Collect campaign data with custom URLs, Analytics Help
  • Traffic-source dimensions, manual tagging, and auto-tagging, Analytics Help

Recommended

  • Track Scan to Conversion: QR Analytics & Campaign Sheet for Marketers
  • How to Archive QR Campaigns So Printed Codes Keep Working
  • QR code reporting for operations: analytics & tracking
  • QR API Integration: Track Campaigns Without Reprinting Codes