Can a Business Card Tell You Who Opened It? NFC and QR
Analytics, honestly

Can a business card tell you who opened it? NFC, QR and link tracking explained

Some card sellers make it sound as if the card reports back on everyone who taps it. None does. Here is exactly what a chip, a QR code and the page behind them can record, and the one way you do learn who someone is.

Written by , Managing PartnerPublished Updated How we research our guides

No card can tell you who opened it. An NFC chip only hands over a link, and a QR code is that link printed. What the page behind it can count is visits: roughly where, on what kind of device, when, and which buttons were pressed. A person is named only when they choose to share their details, for example by saving your contact, sending an enquiry or booking.

Profile from ₹199/year · works with no card · add the NFC card for ₹1,699 whenever you want one

Beeps profileFrom ₹199 a year, no card needed
See the profile
Three layers

What the chip, the QR code and the page each know about a visitor

The chip and the QR code know nothing about who reads them: each gives the phone a link and stops there. The page that link opens is where anything is recorded, and even there a visit is counted, not named. A name only arrives when the visitor types it into something.

Part of our guides to leads and bookings.

Chip or QR codeHands over a link. Knows nobody.The profile pageCounts the visit: place, device, time, clicks.What the visitor chooses to shareSaved contact, enquiry or booking:the only layer with a name in it.
What each layer of a digital business card can record, drawn by Beeps Card.

The chip. A business card chip has no battery; the phone's field powers it while it is held close, and it answers with the link stored on it. NXP's NTAG 213/215/216, a common card chip, can keep an "automatic NFC counter triggered at a reading command" - a count of reads, with no record of who read it.

The QR code. A printed pattern. It can't record anything at all; whatever is counted is counted by the page it opens.

The page. A web page can see what any website sees: a visit, the rough area, the device and browser. It does not see the visitor's name or number. Google, for one, forbids sites from sending such details to its analytics: its help page says "Google policies mandate that no data be passed to Google" that it could use to identify a person.

Action by action

What you can see when a visitor does each thing

Pick what a visitor does on your Beeps profile. The panel shows what reaches you, what doesn't, and the plan it is on. Counting and analytics are on Pro; the actions that carry a name - saving your contact, an enquiry, a booking - work on every plan, because the visitor chose to share.

The visitor
You seeThat someone opened your profile: roughly where (city or region), on what kind of device, and when. On Pro, in your analytics.
You don't seeWho they are. The chip and the QR only hand over a link.
PlanAnalytics on Pro

From the Beeps product documentation and our privacy policy: tap analytics log the approximate location (city or region), device type, time and links clicked, and Pro analytics show a weekly chart with breakdowns by country, device, operating system, browser and language. Plans are on our pricing page.

Leads, the honest way

How names do reach you: three things a visitor chooses to do

A card owner gets a name and number in three ways: the visitor saves the owner's contact, sends an enquiry, or books. Each is a choice the visitor makes, which is also what makes the lead worth calling. Counting visits tells you whether the card is being used; these tell you who to call.

Save to contacts

Everyone who saves your contact is listed for you with the name, email and phone they gave, exportable to PDF or Excel. On every plan.

An enquiry

Name, email, phone, message and any attached file, in your dashboard's Inquiries. On every plan.

A booking

The slot and the details given for it, in a list or a calendar view, from Basic up.

Each of those is personal data you now hold, with duties under India's data protection law from May 2027: the DPDP Act for small businesses. Whether the chip itself is safe to carry is in are NFC business cards safe?

FAQ

Tracking and analytics: questions

Can I see who scanned my QR code or tapped my NFC card?

No. A QR code and an NFC chip only give the phone a link. The page behind it can count visits and see roughly where and on what device, but not the person. You learn who someone is only when they choose to tell you: by saving your contact, sending an enquiry or booking.

Can an NFC business card be tracked?

No. A business card chip has no battery and no power of its own; it only answers a phone held within a few centimetres - the NFC Forum gives a typical range of up to 2 cm. It cannot report where it is, and it does not know who held the phone.

Sources: NFC Forum, NXP Semiconductors

Does Beeps show me who viewed my profile?

No. Beeps analytics, on Pro, show the approximate location, device type and time of each tap or scan and which links were clicked, as a weekly chart with breakdowns by country, device, operating system, browser and language. The people you can see by name are the ones who saved your contact, sent an enquiry or booked.

Why don't analytics tools show visitors' names?

Because they are not allowed to collect them. Google, for example, says its policies mandate that no data be passed to Google Analytics that Google could use to identify a person, such as email addresses or personal mobile numbers.

Sources: Google

Can I collect visitors' phone numbers from my card?

Only when they choose to give them, and then you hold personal data under India's DPDP Act. Use it for what they gave it for. Our guide to the DPDP Act for small businesses has the rules and a notice you can use.

Sources

Facts about other companies and the wider market come from the pages below, as published by them. Each was read on the date shown. Beeps Card prices come from our own pricing page.

  1. NXP Semiconductors, NTAG 213/215/216: NFC Forum Type 2 Tag compliant IC with 144/504/888 bytes user memory. Checked .
  2. NFC Forum, NFC Technology - Technical Overview. Checked .
  3. Google, Best practices to avoid sending Personally Identifiable Information (PII) - Analytics Help. Checked .
Questions? Chat with us