12 User-Identity Tracking Decisions That Affect Product Analytics Accuracy

Decide what counts as a user, which ID represents them before and after sign-in, when to link anonymous activity to an account, what happens at logout and on shared devices, how to handle several devices and platforms, how to group users into company accounts, how to send server-side events with the same ID, and how consent affects identity. These choices change user counts, funnels, retention and attribution more than most dashboards reveal.

This list is for product managers, analysts and developers setting up product analytics for SaaS products, apps and ecommerce accounts. Google Analytics' User-ID rules were checked on 28 October 2026; other tools differ, so check yours. For event design and tracking plans, see product analytics implementation.

1. What counts as a user. A device, a browser, a signed-in person, or an account? Write the definition down. Reports of "users" mean different things in different tools.

2. The anonymous ID. Before sign-in, tools assign a device or cookie ID. Know its lifetime, and that clearing cookies, private browsing and consent choices reset it.

3. The user ID. After sign-in, use a stable internal account ID. Google's GA4 rules say the ID must not contain information a third party could use to identify the person, so not an email address or phone number.

4. When to identify. Set the user ID at sign-up and sign-in, and on app start for already signed-in users. Missing the app-start case is a common cause of anonymous events from logged-in users.

5. Linking pre-login activity. Decide whether activity before sign-in (such as a pricing page visit) should join the user's history. Some tools merge it automatically; others need an explicit call. Note that GA4 does not reprocess data collected before you implemented User-ID.

6. Logout. Clear the user ID on logout. Google's guidance is to set it to null rather than an empty string or placeholder; otherwise the next person on the device inherits the previous user's identity.

7. Shared devices. Family tablets, shop counters and office computers mean one device, many people. Reset identity on logout and avoid merging anonymous activity on devices you know are shared.

8. Multiple devices and platforms. Use the same user ID on web, iOS and Android so one person is not counted three times. In GA4, cross-device reporting depends on a reporting identity that includes User-ID (Blended or Observed).

9. Company accounts in B2B products. Track both the person and the organisation they belong to, so you can measure account activation, seats used and account-level retention. Decide how to handle people who belong to several organisations.

10. Server-side events. Events from your backend (subscription renewed, invoice paid, record imported) should carry the same user and account IDs as client events, so journeys join up.

11. Identity across tools. If analytics, CRM, support and billing each use different IDs, you cannot join them. Agree on a shared internal ID and map other systems' IDs to it.

12. Consent and identity. Where consent is required, identifiers may not be set until a visitor agrees, and some visitors will never be identified. Expect gaps and document them. See analytics checks for websites with consent requirements.

Product analytics is only as accurate as its identity rules. Define what a user is, use a stable non-identifying user ID, set and clear it at the right moments, handle shared devices and B2B accounts, and use the same IDs on every platform and server-side event. Then test: sign up, log out, switch devices and check the results. For mobile-specific events, see mobile app analytics.

Google Analytics Help, measure activity across platforms with User-ID (ID rules, logout, reporting identity, no reprocessing). Accessed 28 October 2026.