Quick answer
A user profile is the record of what you know about one person who uses a product or site: attributes (who), behavior (what they did) and derived labels such as segments. It only works if the same person is recognised across visits and devices, usually through a stable login id.
What is a user profile?
A user profile is the record that holds what you know about one person who uses your product or website: who they are (attributes), what they have done (behavior) and what you have worked out from both (derived labels such as a segment or a "top category"). It is useful because it puts the answers to different questions in one place, so a support agent, an analyst and a marketer all look at the same person instead of three partial copies.
The idea carries one condition that is easy to miss: a profile only helps if the same person is recognised across visits and devices. A person who browses on a laptop at lunch, opens the app on a phone in the evening and logs in on neither until later leaves three trails. If nothing connects them, you have three thin records instead of one useful one. This is why identity resolution sits underneath every profile; this entry covers what goes in a profile and what should stay out, and the identity mechanics are on that page.
Outside analytics the word means other things too: an account page where someone edits their name and photo, a set of settings applied to a computer login, a public page on a social network. This entry is about the analytics and product sense, the record built by tracking and login.
What goes into a profile
A working profile has three layers. They come from different places and age differently, which is why they should not be mixed into one field.
| Layer | What goes in | Example | Where it comes from |
|---|---|---|---|
| Attributes (who) | Facts about the person that change slowly | Display name, login id, country, signup date | Login, forms, your own server |
| Behavior (what) | Things the person did, with time and place | Viewed pricing, exported a report, placed an order | Tracking events, server events |
| Derived (what it means) | Labels computed from the other two | In segment "bought 2+ times in 90 days", top category = running shoes | Rules, tags, calculations |
Two practical consequences follow from the layers.
Attributes describe a person; event properties describe one moment. "Plan: annual" is an attribute and stays until it changes. "Coupon used: SPRING" belongs to a single order event. Putting event details on the profile overwrites yesterday's value with today's and loses history; keeping attributes inside every event wastes space and goes stale.
Derived labels should be recomputed, not typed. A tag such as "top category in 30 days" goes out of date the day after you write it by hand. Define the rule once and let it refresh, so the label is right whenever someone reads it. The related idea of grouping many profiles by a rule is covered in audience segmentation.
How an anonymous visitor becomes a profile
Most visitors never log in, and most analytics counts them without profiling them. A profile starts when something ties activity to an identifier you control, usually a login id. In order:
- Anonymous visit. The browser or device gets an anonymous identifier. Activity is counted, but nobody is named. This is enough for traffic and conversion reports.
- Identification. The person logs in, and your code tells the analytics tool who they are, for example with a call such as
identifyorlogin. See identify for the call itself and user ID for what makes a good identifier. - Backfill. The earlier anonymous activity on that device is attached to the new profile, so the history does not start at the moment of login.
- Merge across devices. A later login on a phone with the same id lands on the same profile, so the laptop and phone histories become one timeline.
- Account switch. If someone else logs in on the same device, history already attached to the first person stays with the first person, and new activity goes to the second.
The common failure is step 2 never happening, or happening with an unstable identifier such as a value that changes on every login. Then every device keeps its own profile and counts such as "users" and "sessions per user" are inflated. A quick check is to compare the number of devices with the number of people: if they are almost equal for a logged-in product, identification is probably not working.
An example profile
Sample data: one profile for a person with the login id u_1042, as it might look after 30 days.
| Section | Field | Value |
|---|---|---|
| Attributes | Display name | Maya R. |
| Signup date | Oct 6 | |
| shown as the domain only (example.com) | ||
| Behavior, last 30 days | Sessions | 14 (9 on laptop, 5 on phone) |
| Orders | 3 (order values $62, $48, $76) | |
| Last order | 9 days ago | |
| Derived | Average order value | $62.00 |
| Segment | Bought 2 or more times in 90 days | |
| Top category | Running shoes |
The numbers can be checked: three orders worth $62 + $48 + $76 = $186, and $186 ÷ 3 = $62.00 average. The 14 sessions split 9 + 5, so the phone accounts for 5 ÷ 14 = 35.7% of sessions. Without identification, those 14 sessions would show up as two separate visitors, one with 9 sessions and one with 5, and neither would have an order history or a segment.
Notice what is not in the profile: no date of birth, no home address, no free-text notes about the person. Nothing in the analysis above needed them. The next section explains why that restraint matters.
What to keep out of a profile
A profile is personal data as soon as it can single out a person. NIST describes personally identifiable information as information that can distinguish or trace an individual's identity, alone or combined with other information linked to them. Under the EU General Data Protection Regulation, collecting personal data is limited by the purpose and by retention:
- Data minimisation (Article 5(1)(c)). Personal data must be adequate, relevant and limited to what is necessary for the purpose. For a profile, that is a field-by-field test: name the decision each field supports, and drop the field if there is none.
- Storage limitation (Article 5(1)(e)). Data in identifiable form should not be kept longer than necessary. A profile that is never trimmed is a liability; set a retention period and a deletion routine.
- Special categories (Article 9). Data revealing racial or ethnic origin, political opinions, religious beliefs, health and similar categories has stricter conditions. Do not infer or store them in analytics profiles.
- Profiling (Article 4(4)). Automated processing of personal data to evaluate aspects of a person, such as their behavior or interests, has its own definition and obligations. Check whether your derived labels fall under it.
A practical rule: keep identifiers (a login id, not an email in plain text), keep behavior at the level of events, and keep derived labels about product use. Leave out anything you would not be comfortable explaining to the person it describes. This is a design guide, not legal advice; have your privacy lead or counsel decide what applies to you. The PII glossary entry lists which fields count.
Common mistakes with user profiles
- Treating a visitor ID as a profile. An anonymous visitor ID is a counter, not a person. It can be reset by clearing cookies or changing browsers, and it cannot hold a name or an order history.
- Using an unstable identifier. A session token, or an email that people change, splits one person into several profiles. Use a stable internal id.
- Overwriting instead of recording. Storing only "last plan" loses the fact that the person upgraded in March. Keep the event, and show the latest value on the profile.
- Collecting fields "just in case". Each extra field adds privacy risk and cleanup work. If no report or decision uses it, do not store it.
- Believing the profile is complete. It only contains what was tracked. Offline purchases, conversations in another tool and visits before login are gaps; label them as gaps.
- Confusing a profile with a persona. A profile is a real person's record; a persona is a fictional composite used in design. They answer different questions.
How to look at a user profile in TapCub
TapCub builds a profile only for identified people, so the first step is on your side: once the project is in identified mode, call tapcub.login() after a successful login.
- Identify at login. Pass a stable id and, if you have it, a display name. The first login on a device attaches that device's earlier anonymous history to the person. Email and phone are encrypted or dropped according to the profile setting; the People list shows them as a domain or the last four digits.
- Find the person. In All-platform analytics › Users › People, search by display name prefix or login id. Email and phone must be entered in full. Narrow the list with a segment, and sort by Last active, Newest or Events (30d).
- Read the profile. The left side shows identity links, segments, tags and accounts; the right side is a day-by-day timeline that merges the person's bound devices. Filter the timeline by pageview, event, error, frustration or identity, and use the platform field to see whether an action happened on web, App or mini program. Activity from before identification is labelled as an anonymous segment.
- Manage what sits on it. User properties and tags are managed in All-platform analytics › Data › Property dictionary and All-platform analytics › Users › Segments & tags. The dictionary classes each field as a direct identifier, an indirect identifier or non-personal, and masks direct identifiers in lists and exports by default.
- Know the limits. Visitors who never log in stay in the aggregate reports and do not get a profile. TapCub shows the timeline and the labels; it does not decide which fields you may keep, and it is not a CRM.
Sources
- NIST Computer Security Resource Center. Personally identifiable information (PII) — glossary definition. Verified 2026-11-18.
- European Union. Regulation (EU) 2016/679 (General Data Protection Regulation) — Articles 4(4), 5(1)(c), 5(1)(e) and 9. Verified 2026-11-18.
- Wikipedia. User profile — the several meanings of the term. Verified 2026-11-18.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Experience Specialist
Writes about product experience, practical workflows, and growth, turning complex processes into clear steps for everyday decisions.