QR code scan tracking and card analytics that show what gets used

QR code scan tracking works through a redirect. A dynamic QR code holds a short link; when a phone scans it, the request passes through CardDeck, which counts the scan and forwards the visitor to your destination in a fraction of a second.

What happens on each scan

1. The phone camera reads the code and opens the short link.
2. CardDeck records the scan: date and time, device type and approximate region.
3. The visitor lands on your card, profile or any URL you chose.

Because the counting happens on the redirect, nothing changes for the person scanning. They don't need an app and don't see an extra page.

Why static QR codes can't be tracked

A static QR code stores its content directly in the pattern, such as a URL or Wi-Fi details. When it is scanned, the phone goes straight to that content without passing through any service, so there is nothing to count. If you need numbers, use a dynamic QR code. The guide to static vs dynamic QR codes explains when each is the right choice.

Card views count too

Your digital business card is a web page, so CardDeck also counts views whether people arrive from a QR scan, a link in a message, your email signature or an NFC tap.

You can measure how many times each card is viewed and each dynamic code is scanned, when it happened, which channel people used, their device type and their approximate region. Contact exchange adds how many visitors shared their details back.

Metrics available

• Views: how many times a card or profile was opened
• Scans: how many times each dynamic QR code was scanned
• Trend: daily, weekly and monthly counts so you can spot peaks after events or mailings
• Channel: QR code, link, email signature, NFC, social bio
• Device type: for example phone, tablet or desktop
• Approximate region: a broad area, never a precise location

Metrics worth watching

• Scans per placement, to compare two flyers or two sign locations
• Views in the week after an event, to judge follow-up timing
• The share of views that become captured contacts, from contact management
• Channel mix, to see whether your email signature or printed code does more work

What analytics can't tell you

Analytics count activity; they don't identify people. You will see that a card was opened 14 times from one region on Tuesday, not who opened it. Names arrive only when a visitor chooses to share them.

Give each placement its own dynamic QR code, then compare scan counts side by side. The placement with more scans is the one doing the work.

Setting up a fair test

1. Create one dynamic code per placement, such as "Flyer A – cafe", "Flyer B – gym", "Sign – Elm St listing".
2. Point them at the same destination so only the placement differs.
3. Print each code at a size that suits its scan distance, roughly one-tenth of the distance.
4. Run them over the same period and compare scans per day.

Examples

• A real estate agent puts a different code on each yard sign and sees which properties draw street interest.
• An event team gives the booth banner and the badge back different codes to see which one attendees use.
• A shop compares the counter code with the packaging code for review requests.

Adding web analytics

If the destination is your own website, add UTM parameters to the destination URL. Your web analytics tool will then show what visitors did after the scan, while CardDeck shows the scan itself.

Changing the destination

Because the code is dynamic, you can point it somewhere new without reprinting. Scan history stays with the code, so you can see before-and-after counts.

Team analytics show card views, scans and captured contacts across every member and department in one dashboard. Managers see which cards get opened after meetings and where follow-ups come from.

For sales managers

• See which reps' cards are opened after meetings and demos
• Compare regions or territories by views and captured contacts
• Spot cards with no activity, often a sign the rep isn't sharing it
• Check that departed reps' cards were redirected

Combined with contact capture, this shows both reach and resulting conversations. See how sales teams use CardDeck for the full workflow.

For event teams

• Compare scans across booths, badges and session slides
• See view spikes during the event and in the follow-up week
• Count sponsor leads by booth from badge scans

For organizations with many cards

Schools, colleges and membership bodies use the same views to see whether digital IDs and member cards are actually being opened, for example after a term-start email to families or a renewal reminder. A low view count is a prompt to resend the link, not a reason to print more cards.

Where it lives

Team analytics sit in the admin dashboard alongside member status and card types, part of team business cards on Team and Business. Business adds advanced analytics and export for reporting across workspaces and brands.

Scan tracking and card analytics start on Pro. Pro includes basic analytics with CSV export and 50 dynamic QR codes; Team adds team analytics, the admin dashboard and 200 dynamic codes; Business adds advanced analytics with export and unlimited dynamic codes.

Plan by plan

• Free: 1 card, 2 dynamic QR codes you can edit, and unlimited static codes. Analytics are not included.
• Pro ($8 a month, or $6 a month billed yearly): basic views and scans for your 5 cards and 50 dynamic codes, with CSV export.
• Team ($6 per seat a month, or $5 billed yearly, minimum 3 seats): everything in Pro plus team analytics across members and departments, and 200 dynamic codes.
• Business (from $199 a month, or $149 billed yearly): advanced analytics with export, unlimited dynamic codes, multiple workspaces, SSO and API access.

See the pricing page for INR prices and the full comparison.

How many dynamic codes do you need?

Count every placement you want to measure separately. An agent with 20 active listings and a card needs about 21 codes. A small shop with counter, window and packaging codes for two locations needs six. An event with 30 sponsor booths and a code per session can run past 50 quickly, which is where Team or Business fits.

Before you print

Decide on tracking before the print run. A static code already on 5,000 flyers can't be converted. Create dynamic codes first, test-scan a proof, then print.

Yes, when it is built on aggregated counts. CardDeck analytics record counts, dates, channel, device type and approximate region, and do not use third-party advertising trackers on cards. Personal data is stored only if a visitor chooses to share it through contact exchange.

What is not collected

• No names, emails or phone numbers from a scan
• No precise location
• No cross-site advertising tracking

Good practice for your codes

• Be clear about where a code leads. A label such as "Scan to save my contact" sets expectations.
• If you add UTM parameters for your own website, your site's privacy notice covers what happens next.
• Keep exported reports to people who need them.

Cards include a short privacy notice so visitors know what is counted. For more on how card and contact data is protected, see CardDeck security.

Where the law comes in

Aggregated counts are designed to avoid identifying anyone. Once a visitor submits your contact form, though, you hold personal data, and rules such as the EU and UK GDPR may apply to how you store and use it. The exchange form records consent and a timestamp, and you can delete a contact on request. This is general information, not legal advice.