How to Add UTM Tracking to QR Code Campaign Links

Problem

Without campaign parameters, different placements can appear as one direct source. Typos, inconsistent case, or personal data in a URL can split reports and create privacy risks.

Who should use this

Useful for marketing, events, campus notices, retail packaging, and creators who need placement comparisons without maintaining many duplicate landing pages.

Formula and concept

Decide what you are comparing: source can represent a platform or print channel, medium a QR or poster, campaign the event, and content the placement. Google Analytics documents how `utm_source`, `utm_medium`, and `utm_campaign` populate manual campaign dimensions, so consistency matters more than adding every parameter (https://developers.google.com/analytics/devguides/collection/ga4/reference/config).

Use a naming sheet with lowercase, readable values and one separator, such as `campus_fair` and `poster_a3`. Never put names, phone numbers, or emails in parameters; placement tracking does not need personal identifiers.

Append parameters to the real destination without deleting existing query strings or fragments. Use `&` when a `?` already exists, and confirm redirects do not strip the parameters.

Before generating the QR Code, open the full URL on a phone and check HTTPS, language, login requirements, and the first-screen task. Tracking parameters should not change what the visitor needs to do.

Use different `utm_content` values for placements when the comparison answers a real question, such as whether entrance A or counter B drives more completions. Avoid a naming scheme no one can maintain.

Record the scanning device, landing URL, post-redirect URL, and source seen in GA4. Google describes events as interaction data; campaign parameters should be accepted only after the data appears in reports (https://developers.google.com/analytics/devguides/collection/ga4/events).

Keep a version and retirement plan after printing. If the event page expires, decide how the destination shows an update or fallback instead of leaving a dead link merely because it was trackable.

Step by step

1. Write down the placements, source, medium, campaign, and content fields you need to compare.
2. Create a lowercase naming sheet and exclude personal data, spaces, and unnecessary special characters.
3. Append UTM parameters to the real destination while preserving existing queries and fragments.
4. Open the URL on a phone and test HTTPS, language, redirects, and the first-screen task.
5. Generate with the QR Code tool, scan it, and record the actual URL and device result.
6. Confirm in GA4 that source, medium, campaign, and completion events group by the naming plan.
7. Save the placement manifest, QR artwork, destination version, and post-campaign retirement plan.

Worked example

A community talk uses the same registration page on an entrance poster and desk card. The team uses source community, medium qr, campaign autumn_talk, and content entrance or desk. A scan test catches a missing ampersand on the desk URL before printing.

Common mistakes

• Inventing parameter names independently and mixing case or separators.
• Putting names, phone numbers, or emails into UTM values.
• Adding another question mark to a destination that already has a query string.
• Checking that a page opens but not redirects or GA4 attribution.
• Creating an unmaintainable naming value for every tiny poster.
• Leaving the QR destination dead after the event without a fallback or update.

Related guides

Related workflows