TL;DR:<\/strong><\/p>\n Before you touch a QR generator, decide what counts as success. A scan is not a booking, so pick the real metric (completed appointment, deposit paid, confirmed slot) and build backwards from there.<\/p>\n Pro Tip:<\/strong> Name your slugs after the physical location, not the campaign date. A code lasts years; a campaign name ages badly.<\/em><\/p>\n Most of the hard thinking happens in steps two and three. Get the UTM structure and the redirect right, and the rest of the workflow more or less takes care of itself.<\/p>\n A static QR code locks in its destination forever. Print a hundred posters with the wrong link, and you\u2019re reprinting a hundred posters. A dynamic QR code, by contrast, encodes a short redirect URL whose destination you can change at any point, which also means you can run A\/B tests on landing pages without touching the printed asset.<\/p>\n A few conventions keep the data usable once scans start coming in:<\/p>\n Resist the urge to encode the full UTM string directly into the QR itself. A complete tagged URL can add 60 to 100 characters, which pushes the code into a higher density version and shrinks the module size on a printed card, according to UseQR\u2019s guidance on UTM parameters. Keep the payload short, keep the tags on the destination behind the redirect, and your code stays scannable even on a small table tent.<\/p>\n A technically perfect QR code still fails if nobody can scan it. Size and distance matter more than design flair.<\/p>\n A code that looks sharp on your laptop can turn muddy under fluorescent reception lighting, so the print proof stage is not optional.<\/p>\n A scan on its own tells you relatively little. The redirector logs a timestamp, an approximate country and a device type, but that\u2019s a top-of-funnel event, not proof of a booking, as laid out in guidance on trackable QR codes for marketers. Closing the loop means tying that click record to what happens next on your booking page.<\/p>\n Pro Tip:<\/strong> Test the printed proof, not just the digital file. A code that scans fine on your phone screen can behave differently once it\u2019s reduced to card stock.<\/em><\/p>\n The mechanics stay the same across sectors; only the placement and the KPI change.<\/p>\n Most of the advice around QR codes focuses on the code itself: size, contrast, error correction. That\u2019s the easy part. The part operators consistently underinvest in is the landing page and the data loop behind it. A beautifully printed code that drops someone onto a slow, cluttered booking form with no visible availability wastes every bit of attention the code earned.<\/p>\n The other mistake is treating QR booking as a one-off print job rather than a measurement system. A code without UTMs and a redirect is a dead end: you\u2019ll never know if the window sticker outperformed the till receipt, and you\u2019ll keep printing on instinct rather than evidence. Dynamic, trackable codes cost the same to print as static ones, although the redirect service behind them may need a paid plan and has to stay active for the code to keep working. For a code you plan to measure, that is usually worth it.<\/p>\n Altegio combines online booking with business management tools for appointment-based businesses, from beauty studios and barbershops to clinics. It covers the booking side of this workflow: an online booking page<\/a> and booking links (including a separate link for a single service or team member), a \u201cBook now\u201d button for Instagram and Facebook<\/a>, deposits through payment policies<\/a> and automatic appointment confirmations. The QR code and any short-link redirect come from the tool of your choice, and you can connect Google Analytics 4 or Google Tag Manager<\/a> to the online booking form to see how many visitors complete an appointment.<\/p>\n A simple way to start:<\/p>\n Full subscription details, including the Altegio pricing plans<\/a>, are there when you\u2019re ready to move past the pilot.<\/p>\n Build your UTM-tagged booking URL first, shorten it through a branded redirect, then generate a dynamic QR code from that short link rather than the raw URL. This keeps the printed code simple and lets you change the destination later without reprinting anything.<\/p>\n The QR code was developed in Japan, where it was created for tracking components in vehicle manufacturing before becoming a general-purpose scanning format.<\/p>\n A dynamic QR code lets you change the destination, run A\/B tests and record scan data such as device type and approximate location without reprinting. A static code locks in its link permanently, so any mistake or update means reprinting every copy.<\/p>\n Set up dynamic booking QR codes, tag each placement, and compare scans with confirmed appointments. Test the full journey on two phone models.<\/p>\n","protected":false},"author":34,"featured_media":50465,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","_members_access_role":[],"_members_access_error":""},"categories":[869,235],"tags":[217,223,286,980,289],"class_list":["post-50492","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-reklama","category-klienty","tag-analitika","tag-servis-onlain-zapisi","tag-online-booking","tag-qr-codes","tag-salon-marketing"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n
\nTable of Contents<\/h2>\n
\n
How to create a QR code for booking in five steps<\/h2>\n
\n
utm_medium=qr<\/code> (or qr-code<\/code>: pick one and keep it), utm_source<\/code> for the placement, utm_campaign<\/code> for the promotion and utm_content<\/code> for the specific asset, the structure most QR code UTM guides use.<\/li>\n\/window<\/code> or \/reception<\/code> so you can audit performance later without guessing which code sat where.<\/li>\n<\/ol>\n![\"QR](\"https:\/\/alteg.io\/blog\/wp-content\/uploads\/2026\/10\/booking-via-qr-code-01.jpeg\")
<\/p>\nWhy dynamic QR codes beat static ones for bookings<\/h2>\n
\n
utm_medium=qr<\/code> on every single booking QR, with no exceptions, so filtering in your analytics tool stays simple.<\/li>\nqr<\/code> as a medium, so these sessions show as Unassigned unless you set up a custom channel group.<\/li>\nutm_source<\/code> for the physical placement (reception, window, flyer) and utm_content<\/code> for the specific creative or batch.<\/li>\nGetting the size, placement and wording right<\/h2>\n
\n
Turning scans into bookings you can measure<\/h2>\n
\n
utm_content<\/code> lets you compare a window sticker against a reception card on equal footing.<\/li>\n<\/ol>\nReal operator setups for QR booking codes<\/h2>\n
\n
What we think most operators get wrong about QR booking<\/h2>\n
Try this with Altegio: a one-week pilot for QR bookings<\/h2>\n
\n
FAQ<\/h2>\n
What is the easiest way to create a QR code for booking?<\/h3>\n
Which country discovered the QR code?<\/h3>\n
Why should I use a dynamic QR code instead of a static one?<\/h3>\n
Read next<\/h2>\n
\n