"Clicks" in the analytics page is a slightly squishy word. It covers more than just somebody opening your profile. Knowing what counts (and what doesn't) helps you interpret the numbers.
The click types we record
- Profile. Someone opens your public card URL. This is the most common click type.
- vCard. Someone taps "Save to Contacts" and downloads your vCard file.
- Weblink. Someone taps one of the website buttons on your card.
- Social. Someone taps one of your social profile icons.
- Contact. Someone taps a phone number, email, or address (anything that lets them reach you directly).
- JSON. A programmatic request to your card data (used by integrations and embeds).
On the analytics page, "total clicks" is the sum of all of these. If you want to know specifically how many people are saving your vCard versus just viewing your profile, you'd look at the breakdown per type rather than the total.
What we don't track
- We don't track who the visitor is. There are no cookies set on the visitor's browser for analytics purposes.
- We don't track their behavior across other sites.
- We don't record IP addresses past the geolocation lookup.
Geographic data
When we record a click, we look up the approximate country and city from the visitor's IP address using a standard geo-IP database. The result is country and city only, accurate to maybe a hundred kilometers in most cases. We do not capture exact coordinates, addresses, or anything beyond city level.
The IP itself is not stored. Only the resulting country and city are kept with the click record.
Turning geo tracking off
If you'd rather not collect any location data at all (for privacy or regulatory reasons), a team owner can disable it.
- Open Settings → Team Settings.
- Find the Geolocation tracking toggle.
- Turn it off.
- Save.
With geo tracking off, clicks are still counted and click types still recorded, but no country or city is attached to them. Past clicks keep whatever data was recorded when they came in.
Bots and prefetch
Some clicks come from bots or browser prefetchers rather than humans. We filter the most common ones out before they get recorded, but a small fraction of total clicks may not represent a real visit. For most cards this is a rounding error; for very low-traffic cards it can skew the numbers a little.