CRM With QR Codes: How to Send Scans and Leads to Your CRM
A CRM with QR codes works like this: a person scans a printed code, lands on a mobile form or page, and their details arrive in your CRM as a contact, already tagged with where they came from. You can build that in an afternoon. The hard parts are choosing the right connection method, keeping the code working after it is printed, and collecting consent properly.
This guide covers the three ways to connect scans to a CRM, the form fields worth asking for, the US consent rules, the automations that follow, and how to attribute results to each code.
TL;DR
- The simplest setup is a QR code that points to your CRM’s own form. Fewer steps means fewer things that can break.
- Use a dynamic QR code, so you can change the destination after printing without reprinting.
- Ask for little: a name, an email or mobile number, one qualifying question and a clear consent checkbox. Capture event and campaign details automatically from the link.
- Put UTM parameters on every code’s destination so your CRM and analytics tools attribute leads to the right placement.
- Test the printed code on several phones before the print run.
Table of Contents
- What a CRM with QR codes actually does
- Three ways to connect QR scans to a CRM
- Setting it up, step by step
- Where QR codes capture leads
- What the form should ask, and what consent it needs
- Automating follow-up after a scan
- Tracking scans and attributing results
- Test before you print
- Start with a code that stays working
- FAQ
- Sources
What a CRM with QR codes actually does
A CRM stores contacts and tracks what happens to them. A QR code is a bridge between something physical (a flyer, a shelf, a badge) and that record. Two kinds of data can cross the bridge:
- Lead data: the person fills in a form after scanning, and a contact is created or updated in the CRM.
- Scan data: the scan itself (time, approximate location, device type) is recorded by the QR platform and passed to your reporting or CRM.
The second kind is where dynamic codes matter. A dynamic QR code contains a short redirect URL rather than your final destination. Lob explains that this redirect can be updated after printing and captures scan time, location and device type, and that once a person converts, the data can flow into CRMs such as Salesforce, HubSpot and Marketo, so teams can tag leads with campaign identifiers and report on revenue.
A static code cannot do this. It hard-codes the destination, so you cannot change it or see scans. For anything connected to a CRM, use a dynamic code. You can create one with the dynamic QR code generator.
Three ways to connect QR scans to a CRM
There are three common routes, from simplest to most flexible, according to WeCanIT’s guide to sending QR leads into a CRM.
| Method | How it works | Best when |
|---|---|---|
| CRM’s own form | The QR code points straight to a form hosted by your CRM. Submissions become contacts. | You want the fastest, most dependable setup. |
| Native integration | A landing page or form tool connects to your CRM through a built-in integration. | You need a branded landing page with more content than a form. |
| Webhook or automation tool | Form data is passed to the CRM by a webhook or an automation service. | The form tool and the CRM do not connect directly. |
WeCanIT recommends the CRM’s own form for most teams, because it removes a step that can break. Most CRMs, including HubSpot and GoHighLevel, offer built-in forms you can point a code to.
If you need more control, you can also use an API. Our guide to QR API integration shows how to create and manage codes programmatically and track campaigns without reprinting. For scan-level data, sending scan data to your CRM walks through the options in more detail.
Setting it up, step by step
- Build the destination first. Create the form or landing page in your CRM. Keep it short and make sure it loads quickly on a phone.
- Create a dynamic QR code that redirects to that page. Add your branding, but keep strong contrast between code and background.
- Add UTM parameters to the destination URL (more on this below), one set per placement.
- Connect the data path. If you are using the CRM’s own form, there is nothing to connect. If not, set up the native integration or webhook, then submit a test entry and confirm it appears as a contact with the right properties.
- Build the follow-up automation (see below) before launch, not after the first leads arrive.
- Test the printed code on real phones, then print.
A HubSpot example
If your QR platform pushes data into HubSpot, the setup in WeCanIT’s guide is to create a Private App with contacts read/write and timeline scopes, paste its access token into the QR platform’s settings, and map the form fields and metadata to HubSpot contact properties. Check HubSpot’s current documentation for the exact scope names in your account, as these screens change.
Once mapped, send yourself a test lead. Confirm that the name, contact details, source and campaign fields land in the right properties. Mismatched mapping is the most common reason leads arrive without a source.
Where QR codes capture leads
Any printed or physical surface can host a code. VistaPrint’s guide to event QR codes lists placements including business cards, flyers and brochures, posters and banners, table tents, booth signage, product packaging, event badges, and receipts or takeaway materials. It advises offering clear value, keeping the destination mobile-friendly and prompting action in the moment.
In practice, give each placement its own code. A code on a brochure and a code on a booth banner should be two codes pointing to two tagged URLs. Then your CRM can tell you which one produced the lead, not just that the event produced leads.
A few examples:
- Retail and hospitality: a table tent offering a loyalty perk in exchange for an email address.
- Events: a badge or booth code that opens a short contact form tagged with the event name.
- Print and direct mail: a unique code per mailer or per segment, so the CRM knows which version worked.
- Packaging: a code that leads to registration or a reorder page, tagged by product line.
For more ideas on turning scans into contacts, read our lead generation with QR codes guide.
What the form should ask, and what consent it needs
Short forms convert better on a phone, and a person standing at a booth will not fill in ten fields. WeCanIT recommends these fields: first name, email or mobile number, one qualifying question with three choices, and a clearly worded consent checkbox for follow-up messages. Everything else, such as event name and location, should come from the QR link itself rather than from the person typing.
Consent for texts and marketing
If you collect mobile numbers to send marketing texts in the US, consent is a legal matter, not a design choice. TermsFeed’s guide explains that the Telephone Consumer Protection Act (TCPA) requires clear and conspicuous language when signing people up for SMS marketing. The language must say that the person is signing up, that signing up is not required, what they will receive (content and frequency) and how to opt out. It cites 47 CFR § 64.1200(f)(9)(i). It also notes that when you use a QR code for sign-ups, you should put the consent and disclosure wording below the code and make clear that a purchase does not depend on scanning.
The practical rules that follow:
- Never pre-tick the checkbox, and never make marketing consent a condition of buying. Omnifox notes that if checkout is impossible without ticking the box, the consent is worthless under TCPA and carrier rules.
- Include message and data rate wording, opt-out instructions (text STOP) and help instructions (text HELP).
- Keep marketing and transactional consent separate. Omnifox points out that a customer who gives you a number for delivery updates has not agreed to promotions, so keep two consent flags on the contact record and never let one imply the other.
These are general US rules, and the right wording depends on your business and the states you sell in. Have your attorney review the final consent text before launch.
Automating follow-up after a scan
Capturing the lead is half the job. The other half is what happens in the next hour. In HubSpot, a workflow can use a QR code scan as its trigger, according to this CRM automation guide for realtors. It describes enrolling contacts in email nurtures, assigning them to reps, sending internal notifications and updating lifecycle stages based on which QR code was scanned.
The same logic works in any CRM that lets you branch on source or campaign fields:
- Trade show code: send a thank-you email the same day and create a task for the rep who staffed the booth.
- Brochure code: enrol the contact in a three-email nurture about the product shown.
- Receipt or packaging code: set the lifecycle stage to customer and send onboarding tips.
If you are deciding how much of this belongs in the CRM and how much in a separate marketing tool, marketing automation versus CRM is a useful framework for working out which jobs go where.
Tracking scans and attributing results
A lead in your CRM is more useful when you know which code produced it and what it was worth.
Tag every destination with UTM parameters
UTM parameters (source, medium, campaign, content and term) are tags added to a URL so analytics tools can group traffic consistently. Pair each dynamic code with its own tagged destination. Without them, scans often show up as unattributed direct traffic. Our guide to UTM for QR codes gives a four-step method.
Pick a few measures that matter
Mobilo Card suggests defining KPIs with precise formulas:
- Scan-through rate: scans divided by estimated impressions at that placement.
- Conversion rate: qualified CRM leads divided by scans.
- Time to CRM: median minutes from scan to lead creation.
It also advises capturing a unique scan identifier at the moment of the scan and carrying it through redirects into form submissions or API calls into the CRM, so each lead can be traced to its scan.
For the mechanics, see our guides on QR scan attribution, QR code analytics metrics and QR code tracking for marketers.
Our view
We built QRlytics around one idea: a printed code is a promise, and it should not depend on your billing status. Many QR tools deactivate codes when a subscription lapses, which turns a printed run of brochures or packaging into waste. With QRlytics, codes created during an active subscription keep working, regardless of billing status.
That matters most for CRM workflows. Your CRM forms, landing pages and campaigns will change over time. A dynamic code lets you update the destination URL without touching the print, so the same code can point to a new form next quarter, and your scan history stays attached to it.
We also think scan data should be useful and respectful. Our analytics are designed to be GDPR-compliant, and we offer real-time scan reporting, global heat maps, CSV export and API access, so scan data can sit alongside your CRM records rather than in a separate silo.
The
Test before you print
The CRM can be perfect and the campaign still fails if the code does not scan. Mobilo Card advises a physical mockup test: tape a printed code at the intended height, then measure successful scans from three approach angles and two distances using at least five phone models. Its point is that poor placement quietly kills conversion.
A short checklist before the print run:
- Scan the printed proof, not the screen version, on both iPhone and Android.
- Confirm the redirect lands on the right form and that the form loads fast on mobile data.
- Submit a test lead and check it in the CRM, including its source and campaign fields.
- Check that the follow-up automation fires.
- Confirm the code’s size and contrast suit where it will hang. Our guide to QR code placement covers testing, sizing and tracking.
Start with a code that stays working
If you want to try this setup, you can create dynamic codes with QRlytics and see scan analytics from the first scan. The Free plan costs $0 per year, with limited codes and analytics, and there is no credit card needed to sign up. The Pro plan unlocks unlimited codes, advanced analytics and API access; see the pricing page for plan details.
When you are ready, create your first trackable code and point it at your CRM form. For campaign-focused teams, our QR codes for marketing page shows how codes fit into wider campaign tracking.
FAQ
Do I need a special CRM to use QR codes?
No. Any CRM that offers a web form, or that connects to a form tool through an integration or webhook, can receive leads from a QR code. The code simply opens the form or landing page. Pick the simplest route your CRM supports.
Should I use a static or dynamic QR code for a CRM form?
Use a dynamic code. It lets you change the destination after printing and records scan data such as time, location and device type. A static code locks in the URL, so if your form link changes you would have to reprint.
How do I know which QR code produced a lead?
Give each placement its own dynamic code and add UTM parameters to its destination URL. Your CRM and analytics tools can then attribute the lead to the source, medium and campaign. Carrying a unique scan identifier into the form makes the link between scan and lead even more exact.
Can I text people who submit my QR form?
Only if they gave clear, unticked-by-default consent to receive marketing texts, with the required disclosures and opt-out instructions. In the US, the TCPA sets these rules, so have an attorney review your wording before you launch.
Sources
- How to Send QR Code Leads Straight into Your CRM (WeCanIT)
- How to Use Event QR Codes (VistaPrint US)
- How to Get Legal Consent for SMS Marketing (TermsFeed)
- How to Collect SMS Opt-In Consent (Omnifox)
- Open House CRM Automation (Lead2Done)
- How to implement dynamic QR code tracking for direct mail (Lob)
- How To Create a Successful QR Code Marketing Strategy (Mobilo Card)
- Marketing Automation vs CRM for Founders (Quincy Samycia)