Yes, but only indirectly. NFC business card tracking happens on the web page the card opens, not on the chip, so you can count how many taps turned into a visit to your profile. You can’t count taps that never opened the page, and you won’t see names unless people choose to share them.
Why the NFC chip can’t count taps for you
An NFC business card chip can’t report taps because it has no power source and no connection to anything. NXP’s datasheet for the common NTAG213/215/216 chips describes “contactless transmission of data and supply energy”: the phone’s field powers the chip for the moment it is being read.
The chip is closer to a sticker than a gadget. It stores a small amount of data (144, 504 or 888 bytes, depending on the model) and hands it to the phone. Usually that data is a single web link. What the phone does with that link decides whether anyone can count anything.
How NFC business card tracking actually works
Tracking works because the link on the chip points to a page you control. When someone taps your card, their phone reads the link and opens it in the browser. The server behind that page logs the visit, the same way any website logs a page view.
That’s why a card that stores a link to a hosted profile can be tracked, and a card that stores a contact file directly on the chip can’t. With a contact file, the phone reads everything locally and never asks a server for anything.
A typical card dashboard shows, per visit:
- Views: how many times the profile page opened.
- Time and date: useful for matching a spike to an event.
- Device and rough location: country and often city, worked out from the visit.
- Traffic source: whether a visit came from a tap, a QR scan or a shared link, where the tool can tell them apart.
- Saves: whether the visitor added you to their phone contacts.
QRCard works this way. It gives you an NFC-ready URL that you write to any compatible tag yourself (it doesn’t sell physical cards), and its dashboard reports views, saves, traffic sources, geographic data and leads. If you haven’t programmed a tag before, start with how to write a URL to an NFC tag.
The chip’s own tap counter, and why it isn’t your tap count
The NTAG21x chips do have a built-in counter. According to NXP’s datasheet, the chip can automatically increase a 24 bit counter on the first valid read after it is powered by a phone’s field. The counter stops changing once it reaches its maximum value of FF FF FF hex, and it has to be switched on with a configuration bit.
The better feature is the ASCII mirror. The chip can write its 7 byte serial number (UID), its 3 byte counter value, or both straight into the stored link as text. So each tap could send a URL that ends with something like the card’s ID and its current count. That lets a server tell individual cards apart, which matters if a team shares one profile.
It still isn’t a clean tap count:
- Many phones read a tag more than once in quick succession, and the counter only knows about reads, not people.
- The counter value only reaches your dashboard if the phone actually opens the link.
- Most card platforms write a plain link and ignore the mirror.
If you want to choose a chip with enough room for a long tagged link, the comparison of NTAG213 vs NTAG215 vs NTAG216 covers the memory differences.
Not every tap becomes a visit
A tap only shows up in your stats if the phone opens the page, and phones are getting more cautious about that. Google’s Android NFC developer guide says that on Android 16 and later, a tag holding a web link triggers the phone’s normal open-link action. On Android 17 and later, the phone first shows an “open link” notification and the person has to tap it.
That extra step costs you visits. Picture a trade show booth: you tap your card on a visitor’s new Android phone, a notification appears, and they’re already turning to the next person. Your dashboard records nothing, even though the tap worked.
Other taps get lost before that point. NFC might be switched off, the phone case might be too thick, or the tag sits in a spot the phone’s antenna doesn’t reach. The guide to NFC business cards not working on Android goes through those causes.
Taps, views and leads are different numbers
The number you see is visits from taps, and that is a different thing from people who are interested in you. A view means a page opened. A save means someone kept your contact. A lead means someone sent you their details.
For the bigger picture, including what a view can and can’t tell you about the person behind it, read how to track who viewed your digital business card. If your real question is whether the cards pay off, measuring whether your business cards bring in clients walks through linking visits to actual work.
My take, and the limit to accept
Treat the tap count as a floor, not a total. It tells you roughly how often your card leads to a page visit, which is the part that matters for follow-up. Don’t chase an exact tap number. The chip’s count and your dashboard’s count will never match.
The limit to accept: you will undercount, and the gap will grow as phones ask for more confirmation before opening links. If you need a firmer number at events, also put a QR code on the card. A QR scan opens the same tracked page and gives people a second way in when the tap fails.
FAQ
Does the NFC chip in my card send data anywhere when someone taps it?
No. The chip has no battery and no internet connection. It is powered by the phone’s field for a moment, hands over the stored link, and that is all. Any tracking happens on the web page the phone then opens.
Can I see who tapped my NFC business card?
Not by name. A tap that opens your profile page gives anonymous data such as time, device and rough location. You only learn a name if the person chooses to share their details with you, for example through a contact form on the card page.
Why does my dashboard show fewer views than the number of people I tapped?
Some taps never become a page load. The phone may have NFC turned off, the person may dismiss the open-link prompt, or the page may not load without signal. Your count is the number of visits, not the number of taps.
Can a card with my contact saved directly on the chip be tracked?
No. If the chip holds a contact file instead of a web link, the phone reads it locally and never contacts a server, so there is nothing to count.