QR Code with UTM

Builds a URL with UTM parameters (source, medium, campaign, term, content) and encodes it as a QR code. The QR encoding follows ISO/IEC 18004 with configurable error-correction level (L, M, Q, H).

Higher error correction tolerates more visual damage but produces denser codes. Level M (~15% damage tolerance) is a common balance.

QR codes were developed by Denso Wave in 1994 for tracking automotive parts and standardized internationally as ISO/IEC 18004 in 2000. The format encodes data using a 2D matrix of black and white modules, with positioning markers in three corners and timing patterns ensuring scanners can orient the code regardless of rotation. Reed-Solomon error correction at one of four levels (L = 7%, M = 15%, Q = 25%, H = 30%) allows the code to remain scannable even when partially damaged or obscured. The matrix size (called 'version' in the spec, ranging from 1 at 21×21 modules to 40 at 177×177) scales automatically based on payload length and error correction level.

A worked example: a campaign URL like 'https://example.com/landing?utm_source=newsletter&utm_medium=email&utm_campaign=spring2026&utm_content=banner' is 113 characters long. At error correction M, this fits in QR version 5 (37×37 modules). Adding a logo overlay typically requires upgrading to error correction Q or H, which increases code density to version 6-7 (41-45 modules per side). The corresponding printed code at 1.2 inches square renders at about 25 modules per inch, comfortably scannable by any modern smartphone camera.

UTM parameters are convention-based metadata appended as URL query strings, originally introduced by Urchin Software (acquired by Google in 2005, becoming Google Analytics). The five standard UTM fields cover source (the originating site or platform), medium (channel type), campaign (specific initiative), term (paid search keyword), and content (creative variant for A/B testing). Google Analytics, Adobe Analytics, and most other web analytics platforms recognize UTM parameters automatically and use them to populate traffic source reports.

Limitations are about scan reliability and parameter hygiene. Long URLs produce dense QR codes that scan less reliably from a distance or at angles; URL shorteners (Bitly, Rebrandly, custom short domains) trade off direct readability for reliable scanning. Logo embedding requires error correction Q or H; the logo should not exceed 30% of the code's area, with 20% being safer. UTM parameter values are case-sensitive in Google Analytics: 'Newsletter' and 'newsletter' become separate sources, fragmenting reports. Establishing a naming convention upfront (lowercase only, hyphens not underscores) and sticking to it prevents this fragmentation. Parameter validation, character escaping, and length limits are handled by the URL-encoding step before QR generation.

For printed campaigns, testing the QR code at the intended print size and viewing distance before mass production is essential; what looks crisp on a designer's monitor may not scan reliably at billboard scale or business-card size.