More in Product analytics
- Autocapture and the AI event inbox
- Build a funnel that explains drop-off
- Identify users across web, app and mini-programs
- What is autocapture, and how does it work?
- How do I review and accept events in the inbox?
- What are unplanned events, and how do I manage them?
- When should I use a funnel instead of a goal or path?
- How do I build a funnel?
- How do I read where a funnel drops off?
- What is identified mode, and should I turn it on?
- How do I call login to identify a user?
- How is one person merged across devices?
- How does identity work on apps and mini-programs?
- How do I track clicks on outbound links?
- How do I track file downloads?
- How do I track form submissions?
- How do I track custom events?
- How do I track button clicks?
- How do I create a heatmap?
- How do I track scroll depth?
- How do I track ecommerce purchases and revenue?
- How do I set up goals and track conversions?
- How do I query my data with SQL?
- How do I create a custom metric?
- How do I analyze accounts with groups?
- How do I connect AI agents with MCP?
- How do I ask the AI assistant about my data?
- How do I create user segments?
- How do I run an RFM analysis?
- How do I record and watch session replays?
- How do I analyze user paths?
- How do I build a retention report?
- How do I analyze how an event is distributed?
- How do I create a tracking plan?
- How do I read the lifecycle report (new, returning, resurrecting, dormant)?
- How do I compare attribution models for a conversion?
- All guides in this category
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usShort answer
Open All-platform analytics › Users › People and click a row to open that person's profile. The left side shows identity links (login IDs and devices), segments, tags and accounts; the right side is a day-by-day timeline of pageviews, events, errors and frustration across web, app and mini program. People appear here only after they are identified, with tapcub.login(), a zero-code identity source or a server-side bind.
Requirements
- Identified mode must be on for the project. The console has no switch for it yet; contact support to turn it on. It is available on Pro and above, not on the Free plan.
- Identify users when they sign in: call
tapcub.login()(or the SDK equivalent) with your user ID and, if you have it, a display name. See Identify users. - Role: owners, admins and analysts can view the list and mark test users.
Without identification the list stays empty. Anonymous visitors are still counted in the visitor reports; they just have no profile.
Find a person
- Search by the beginning of a display name or by login ID. Email and phone must be typed in full; TapCub hashes them before matching.
- Narrow the list with a segment or rules (the same conditions as segments), and sort by Last active, Newest or Events (30d).
- Switch identity between person, device and visitor; the list dedupes on the identity you choose.
- Test users are hidden by default; turn on Include test users to see them.
- From a segment or an analysis, View users opens this list with the same filter in the URL.
Read a profile
Left side:
- Identity links: the login IDs and devices joined to this person. Several devices mean they shared a login ID.
- Segments, tags and accounts the person belongs to.
- Properties such as name, plan or membership level written at login or from the server.
Timeline: a day-by-day record merging all bound devices. Filter it by pageview, event, error, frustration or identity. Activity from before the person was identified is labeled as an anonymous segment. Check the platform field to see whether an action happened on the web, in the app or in a mini program. If an event carries a replay URL, the timeline links to the session replay.
The Events, 30 days column counts every event in the last 30 days for the person, including server-side events.
Common uses
- Support: look up the customer who opened a ticket and see what they did before the error.
- Debugging tracking: check that a test user's events arrive with the right properties and on the right platform.
- Understanding segments: open a few members of a churn-risk segment to see what their recent activity looks like.
- Marking test users: mark internal accounts as test users on the profile, so they drop out of analysis by default.
Privacy
Email and phone are shown only as a domain or the last four digits and follow property masking rules; the stricter of the property rule and the member policy applies. Keep personal data out of event properties and send it only through identity and profile fields. See What roles see of personal data.
FAQ
Why is a visitor in the visitor report but not here? They have not been identified. Anonymous traffic is counted, not profiled.
Why does one person have several devices? Those devices shared a login ID, so the timeline merges them. To detach a device, use identity mapping; see Cross-device merge.
Can I delete a person? Use a data subject request to delete their data: Handle data subject requests.
Related
Did this answer your question?
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.