For most links, on most platforms, you cannot get a name. A click arrives as a request from an IP address with a user agent attached, and that is the whole of the raw material. Everything past it is either inference or something the person told you at some earlier point.
Plenty of products imply otherwise. Some are running a data broker lookup in the background. Others are counting clicks and letting the page title do the heavy lifting. Knowing which one you are looking at is most of the work here.
What a click actually carries
The information in a click is thinner than people expect and more useful than they assume:
- Device, operating system and browser, read off the user agent string.
- Country and city, from an IP lookup. City level is approximate and degrades badly on mobile, where the address often belongs to a carrier gateway rather than a neighbourhood.
- The referring page, when the browser bothers to send it. Apps strip this constantly, which is why so much social traffic lands in your analytics as direct.
- UTM parameters, if you put them there.
- Whether this visitor has turned up before.
That last one does more work than the rest combined, and it needs no identity at all. A returning visitor who clicked three times this week is a stronger signal than a name attached to somebody who never came back.
UTM parameters deserve a mention on their own, because they are the only field on that list you control completely. Everything else is reported to you by a browser that may be lying, stripping, or simply out of date. The tag you added yourself is the one piece of the record that cannot be taken away by a privacy setting.
When a name is genuinely possible
You can attach a name to a click when the person already handed you their details, on your own links, earlier.
Someone submits an email through a form or a qualifier flow. Their contact record gets stamped against a hash of the IP address they were on at that moment. Later, anonymous traffic from the same hash matches back to them.
The limits are worth stating plainly, because this is the part every vendor in the category is vague about. It never touches anyone who has not already been in contact with you. It covers only the window where that IP address stays stable, which on a home connection might be months and on a phone might be minutes. There is no device fingerprinting involved and no third-party identity graph lookup, which is also why it will never produce the coverage a data broker claims.
Confidence is the part that matters
An IP address is not a person. It is usually a household. Sometimes it is an office of forty people, and on a mobile network it can be several thousand strangers sharing one gateway.
So the match on its own is close to meaningless without a confidence rating saying how much to trust it. Raydar rates a match high only for a clean residential address with no VPN, proxy, datacenter, Tor or relay flag against it. Mobile, VPN, datacenter and unknown connections all come back low, and the interface tells you which one you are reading rather than averaging the uncertainty into a single confident-looking figure.
Any tool showing you a confident name on every click has not solved this. It has stopped mentioning it.
Linktree, Instagram, and the platforms that cannot tell you
On a link-in-bio page you get whatever the platform chose to record. Usually that is a click count per link, sometimes device or country on a paid tier. No name, because the platform does not have one either.
Instagram gives you aggregate profile visits and link taps inside its own insights and nothing per person. No setting reveals more. Anything claiming to show you who clicked or who viewed your profile is guessing, and the apps in that category have a long history of being worse than guessing.
Instagram also opens links in its in-app browser, which means the referrer often arrives empty even on a completely legitimate click. If you want to know which post drove which click, tag the link yourself. Waiting for the platform to volunteer it has never worked.
Better questions to ask
When someone asks who clicked, they usually want one of three quite different things, and only one of them is about identity.
If you want to know which post is working, tag your links with the free UTM builder and read the data. That sits entirely under your control and does not depend on anyone's identity resolution holding up.
If you want actual leads rather than a list of strangers, put something in front of the link that asks. A short qualifier flow turns an anonymous click into a named contact who agreed to it, which beats any inference on accuracy and avoids the whole argument about whether you should have been de-anonymising people in the first place.
And if you want to know whether a specific person came back, returning visitor detection answers that without a name attached. It is the least glamorous number in the logbook. It is also usually the one that changes what you do next.