QR Code in an Email: When It Works Better Than a Button and How to Add It
Your email already has a button, and for most campaigns, that is all you need. A QR code helps when someone reads the email on one device but would rather take action on another. It also helps when the email gets printed and continues to be used on paper. If neither situation applies to your campaigns, a code in the email is just decoration.
This article explains when a code in an email actually helps, where it should lead, how to make it visible in any email client, and how to distinguish scans from clicks in your reports. We will also cover the reverse direction: using QR codes on printed materials to attract newsletter subscribers.
We will use one example throughout. An online store selling seeds and seedlings sends subscribers a weekly newsletter from February through May. The March email includes a seed-starting calendar that many readers print and hang on their balconies, along with a video tutorial on pricking out seedlings. In February, the store invites readers to install its app for seed-starting reminders. In April, it takes preorders for seedlings with delivery. And every package includes a card inviting customers to subscribe to the newsletter.
Contents
- When a QR Code in an Email Works Better Than a Button
- Where the Code in Your Email Should Lead
- A Button and a QR Code in the Same Email
- How to Make the Code Visible and Scannable
- Static or Dynamic Code for Your Newsletter
- How to Measure the Results of a Code in an Email
- QR Code for Newsletter Signups
- Checks Before Sending
- Start With One Email
When a QR Code in an Email Works Better Than a Button
A button opens the link on the same device where the email is open. Most of the time, that is exactly what you want. Sometimes, though, it is the wrong device for the task.
The email is read on a computer, but the action is easier on a phone. Installing an app, saving a contact to a phone, opening a page to show at checkout later, or watching a video somewhere without a computer. Clicking a button opens all of this in the computer browser, leaving the reader to figure out how to transfer the link to their phone. A code reduces that process to a single scan.
The email gets printed. Reference sheets, instructions, calendars, invitations, and event programs often end up on paper. Once printed, a button becomes a colored rectangle, while a QR code still works.
The email is shown to someone else. A colleague opens an invitation on their monitor, but the person sitting next to them needs to register. Scanning the code from someone else's screen is easier than asking them to forward the email.
Now consider the opposite case, which happens very often: the email is opened on a phone. Scanning a code from your own screen is awkward, so the reader will tap the button or do nothing. That is why a code in an email complements the button for people who read email on a computer or print it, rather than replacing it.
In our example: the seed store adds a QR code to only two out of four emails. The February email invites readers to install the app: they often open the email on a work computer, but need the app on their phone. The March email places a video tutorial next to the seed-starting calendar: readers print the calendar and watch the video on their phones right beside the seedling trays. The April email about seedling preorders has no code: placing an order is equally convenient on a computer or a phone, so a button is enough.
Where the Code in Your Email Should Lead
The code should lead to wherever the reader needs to continue on their phone. Different actions call for different types of codes:
- web page — an offer, catalog, form, or customer account. Use a Link QR Code; add UTM parameters to the web address (more on those in the measurement section);
- app — a page with app store buttons. Scanning opens a page with buttons for the App Store, Google Play, and other stores. With automatic redirects enabled, the reader goes straight to the store for their device. This type of code is only available as a dynamic code;
- video — a YouTube QR Code for a specific video, playlist, or channel;
- document — instructions, a reference sheet, or a price list shared through a PDF QR Code. You can update the file, and the new version will open through the same code;
- contact — a digital business card that readers can save straight to their phones: an account manager, support team, or courier service.
It is also worth understanding what a single QR code in a newsletter cannot do. Thousands of people receive the email, and the code is the same for everyone. One shared code cannot contain a different personal discount code, named ticket, individually priced invoice, or account login link for each customer. Codes like these are generated for each recipient by the system that knows who they are: the email platform, ticketing system, payment system, or business management software. Another point: an Email QR Code is unnecessary inside the email itself, since the reader already has a Reply button. That type of code belongs on printed materials, which we will discuss below.
In our example: the February code leads to the app page with App Store and Google Play buttons, while the March code leads to the video tutorial on YouTube. The store sends personal seedling discounts through its email platform, which inserts a separate discount code into each recipient's email.
A Button and a QR Code in the Same Email
The simplest approach is to place the button and code side by side, both leading to the same page. Readers on phones tap the button; readers at computers choose whichever option is easier. The button and code can have different destinations, but the email needs to explain the difference. For example: “Open the lessons on our website” next to the button and “Install the app on your phone” below the code. If the button and code lead to different places without explanation, readers will not know which to choose.
The caption below the code should explain what happens after scanning, rather than just repeating “Scan the QR code.” “Open the video tutorial on your phone” or “Install the app — we will remind you when to sow” immediately explains why someone should pick up their phone. We cover general guidelines for captions and destination pages in our article on mistakes when using QR codes.
One useful detail: make the code image itself clickable. Readers who open the email on a phone and tap the code out of habit will still reach the page. However, that tap should link directly to the destination page, not to the dynamic code's short URL. Otherwise, every click on the image will count as a scan in the statistics, even though no one used a camera.
How to Make the Code Visible and Scannable
A QR code in an email is an ordinary image. But email images can have problems that do not occur on paper.
Images may be blocked. Some email clients do not display images until the reader explicitly allows them. Instead of the code, they will see an empty rectangle. Give the code alt text that explains the action (“QR code: video tutorial on pricking out seedlings”), and include a button or text link next to it. A screen reader will read the same alt text aloud, so it also helps people who cannot see images. The email should still make sense without images.
Dark mode can make the code unreadable. Email clients handle email colors differently in dark mode. A code with a transparent background may end up with dark modules on a dark background, leaving the camera unable to read it. A solid light background is more reliable than a transparent one. A colored code can work too, but be sure to test it in dark mode after adding it to the email layout.
Use PNG. It keeps module edges sharp and is supported by all email clients. JPG compression can blur small modules, while many email clients do not display SVG — that format is for print, not email. You can download a PNG directly from the generator on the website; other formats are available in the dashboard.
Check the size on screen. The code should scan from a laptop at a normal distance, without holding the phone right up to the screen. Also check the email in mobile view: some templates shrink images, making the code too small. If readers might print the email, make a test print on an office printer.
The general scanning rules — contrast, quiet zone, and code density — are the same as for print. We have collected them in our article on mistakes when creating QR codes. For advice on using brand colors without making the code harder to scan, read “Branded QR Codes”.
In our example: the store places the code in a white block next to a still from the video tutorial. Below the code is the caption “Open the video tutorial on your phone,” with a “Watch the tutorial” button alongside it. The white block stays white in dark mode, and the button still works when images are blocked.
Static or Dynamic Code for Your Newsletter
The main difference between an email and a flyer is that you cannot “reprint” an email once it has been sent. It stays in inboxes and printouts, and people may still open it months later.
A static code is enough if it points to a permanent address that will not change: an app listing, a section landing page, or a permanent set of instructions. You can create a static code on the website without registering, but it will not have scan statistics. Visits through links with UTM parameters will still appear in your website analytics.
A dynamic code contains a short link, and you can change its destination in the dashboard. For newsletters, this matters in three situations:
- The page is temporary. The promotion has ended, but people are still opening the email. You can redirect the code to a current page so readers do not get a “Page not found” error. Remember, though: changing the destination does not change the email text. If the caption says “Discount through March 31,” the new page needs to explain that the promotion has ended and what is available instead;
- The material will be updated. A new version of the instructions, a newly recorded video, or a corrected address — without sending another email;
- You need scan statistics. How often and when the code was opened, from which countries, and on which devices. Learn more on the QR code analytics page.
Changing the destination affects only the code itself. The button, text link, and clickable image in an email that has already been sent still lead to the address entered before sending. So if the button and code originally led to the same page and you later redirect the code elsewhere, make sure the old page still has useful content too.
Dynamic codes also support access restrictions: availability schedules, scan limits, and passwords. Some are available only on certain plans; see the pricing page for details. For newsletters, however, these are rarely needed: everyone with the email has the same password, so it cannot protect personal data. One more thing to consider: scans of all dynamic codes in an account count toward a shared monthly limit, and the statistics retention period depends on the plan. For a code sent to a large mailing list, plan for this in advance, and remember that test scans also count toward the limit.
In our example: the store makes both codes dynamic. For the app, there is no other option: the page with app store buttons is only available as a dynamic code. For the video tutorial, it is a deliberate choice: the calendar with this code will hang on balconies until the end of the season, and the store plans to record a new tutorial in winter. The new video will open through the same code, with no need to send anything again.
How to Measure the Results of a Code in an Email
Your email platform counts email opens and link clicks. A code scan does not appear in that report: the reader does not click inside the email but opens the address on another device. If you assess the email solely by clicks, the code's contribution will go unnoticed.
To see the full picture, use different UTM parameters for the button and the code. Both links lead to the same page, but with different parameter values:
- button:
https://example.com/video/pikiruvannya?utm_source=email&utm_medium=email&utm_campaign=march_sowing&utm_content=button - QR code:
https://example.com/video/pikiruvannya?utm_source=email&utm_medium=qr&utm_campaign=march_sowing&utm_content=video_block - clickable code image:
https://example.com/video/pikiruvannya?utm_source=email&utm_medium=email&utm_campaign=march_sowing&utm_content=qr_image_click
Many email platforms add UTM parameters to links automatically, but the address inside the QR code is part of an image, so the platform does not change it. You need to add the code's parameters yourself.
Each system shows a different part of the journey, so it helps to know in advance where to look:
| What you want to know | Where to look |
|---|---|
| How often the button or image in the email was clicked | In your email platform's reports |
| How often the dynamic code was opened | In the code's scan statistics in the dashboard |
| How many visits reached the page and what visitors did there | In your website analytics, using UTM parameters |
| How many orders the email campaign generated | In your order management system or CRM |
Your website analytics will show visits from the code and the button in separate rows.
Visits with utm_medium=email
are assigned to the Email channel in GA4, while utm_medium=qr is not covered by the default channel grouping rules and ends up under “Unassigned.”
Look for QR visits using the “Session source / medium” dimension.
For a detailed explanation of how to set this up and pass the source through to your CRM, see our
article “QR Codes With Analytics: UTM, GA4, and CRM”.
If the code is dynamic, its statistics add information that website analytics cannot show: scans even when the page did not finish loading, a breakdown by day and hour, and the devices used. To distinguish emails and variations, you need separate codes: one code used across all emails shows only the total. You can give codes clear internal names and organize them into folders in the dashboard.
What the code's statistics will not show: which subscriber scanned it, whether they bought anything, or what they did on the website. Unique scans are counted by device, not by person. Purchases and inquiries appear in your website analytics and order management system, not in the code's scan statistics.
In our example: suppose the email platform reports few clicks on the “Watch the tutorial” button after the March email, while the code's statistics show scans continuing for several weeks after sending, mostly on weekends. This suggests that readers really did print the calendar and use it beside their seedlings. The same approach is worth repeating next season.
QR Code for Newsletter Signups
Email marketing starts with a mailing list, before the first email is sent. Here, a QR code works in the opposite direction: from printed material to your newsletter. A flyer in a package, a sign by the register, a sticker on the packaging, or a card included with an order — readers scan the code and reach the signup page.
For that page to work, keep it short: an email field, one or two checkboxes for newsletter topics, and a clear promise of what readers will receive and how often. We do not offer a form builder. The signup form lives on your website or is provided by your email platform; the code simply opens it with the right UTM parameters. A separate code for each placement will show where new subscribers come from.
Another option is an Email QR Code. It does not subscribe anyone to a newsletter. Instead, it opens an email draft with the recipient address and subject already filled in: “Question about my order” or “I would like a consultation.” This type of code works well on packaging, in a brochure, or on a display stand — wherever someone wants to write to you rather than subscribe.
We cover the specifics of individual printed materials — flyers, posters, and receipts — in our article “QR Codes in Offline Advertising,” while codes on packaging are covered in “QR Code on Packaging”.
In our example: the store includes a card in every package that says “Get a seed-starting calendar by email every month.”
The code leads to the signup page with utm_source=parcel_card.
The card is included even when there are no promotions, so the store makes the code dynamic: if the newsletter format changes, it can redirect the code to a new page rather than reprint the whole batch.
Checks Before Sending
Before sending, email yourself a test and go through the steps your subscribers will take:
- Open the email on a computer and scan the code with a phone — test iPhone and Android, using different cameras;
- Make sure the code leads to the right page and that the page is easy to use on a phone;
- Test the email in several email clients, in both light and dark mode;
- Turn off images: is it still clear what to do without the code?
- Open the email on a phone: is there a button or link, and does tapping the code open the page?
- If readers might print the email, make a test print;
- Check the UTM parameters in the code's address: use Latin characters, lowercase, and the same naming conventions as in your other campaigns. Open the page after scanning and confirm that the parameters remain in the address after all redirects;
- Compare the email text with the destination page: dates, terms, and prices should not contradict each other;
- For a dynamic code, remember that test scans count toward both the statistics and the monthly limit.
Start With One Email
You do not need a code in every campaign. Choose one email where readers really need to switch from a computer to a phone or where the email is printed: an app installation, video tutorial, reference sheet, or invitation. Keep a button alongside the code, add a caption describing the action, test the email in dark mode and without images, and use different UTM parameters for the code and the button.
For a web page, use a Link QR Code; for an app, a code with an app store page; for instructions, a PDF QR Code. You can create static codes on the website without registering, and dynamic codes with scan statistics in the FbFast dashboard. For code and scan allowances, see the pricing page.