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 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 view a user’s profile and activity?
- 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
The first login on a device backfills that device’s anonymous history onto the person, so the full first-visit-to-sign-up funnel is complete. A later login with a different account does not move rows that already belong to someone — the device just points at the new person from then on.
What merges, and what does not
The first login on a device backfills that device’s anonymous history onto the person, so the funnel from first visit to sign-up is complete. A later login with a different account on the same device does not move rows that already belong to someone: the device is pointed at the new person, a new analytics session starts, and only new events go to the new person.
Devices per person
Each person can have up to 50 devices by default. Devices beyond that are still counted, just not merged onto the person. That is far more than a real user needs and mostly matters for shared or kiosk devices.
Because merge only moves anonymous rows forward once, a shared computer does not leak one customer’s history into the next — logout() starts a clean session.
See also: Device ID, View user profiles.
Update history1
- UpdateContent updated
- First published
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.