Dashboard listing identified logged-in users with sessions and activity

How to Identify and View Logged-In Users in statpx

Anonymous analytics tells you a site had 3,000 sessions this week. It can't tell you that your highest-paying customer only visited twice, or that a user who churned last month had five failed checkout attempts before giving up. The statpx Users page closes that gap by letting you identify visitors who log in to your product, then browse each known person's full history — sessions, pageviews, events, and purchases — in one place. This guide covers wiring up identification and reading the resulting profiles.

Identifying a User with One Tracker Call

By default, every visitor is anonymous — statpx tracks sessions and pageviews without knowing who's behind them. To attach a real identity, call the identify action from your tracker snippet the moment you know who a visitor is, typically right after login or on every authenticated page load:

// Minimal — just a stable user ID _st('identify', 'user_1029'); // Recommended — ID plus traits for richer profiles _st('identify', 'user_1029', { name: 'Jane Cooper', email: '[email protected]', plan: 'pro' });

The first argument is a stable, unique identifier for that person — your internal user ID or database primary key works well. It should never change for the same person, since it's the key statpx uses to merge all of that visitor's future sessions into one profile. The second argument is optional but valuable: any traits you pass (name, email, plan, or anything else relevant to your product) are stored alongside the identity and shown directly on their profile page.

Call it consistently, not just once. Firing identify on every page load for a logged-in user (not just at the moment of login) ensures sessions are correctly attributed even if a visitor's session starts before the identify call would otherwise fire, such as a direct deep link to an authenticated page.

Browsing the Users List

Open user_profiles.php from the sidebar of any site to see every identified visitor, sorted by most recently active. Each row shows the user's traits (name and plan, if supplied), first-seen and last-seen dates, total session count, and total pageview count — enough to spot your most active users, or notice someone who used to visit daily and has gone quiet, at a glance.

Viewing a Single User's Full History

Click into any user to open their detail view, which brings together everything statpx knows about that one person: their recent sessions (with country, browser, OS, device, and duration for each), the events they've triggered, and — if you track ecommerce — their purchase history. This is the view to check whenever a specific customer contacts support with a problem, or when you want to understand exactly how your highest-value users actually behave differently from everyone else, session by session.

Because identification merges every session under one profile regardless of device or browser, a user who logs in from their phone and later from a laptop shows up as a single, continuous history — not two disconnected anonymous visitors. Combine this with user journey data to trace not just what a user did, but the exact path they took to get there.

Start identifying your users today

statpx merges sessions into full user profiles the moment you call one tracker function. Privacy-friendly, free to start.

Start for free →

The Bottom Line

Session-level analytics is enough to answer "what happened on the site." User identification answers the more valuable question: "what happened to this specific person, across every visit they ever made." Add one _st('identify', ...) call at login, pass along the traits that matter to your product, and the Users page turns anonymous traffic numbers into real customer histories you can act on — whether that's spotting an at-risk power user before they churn or understanding what your best customers actually do differently. Pair identified user data with a full customer lifetime value analysis to connect behavior directly to revenue.

Continue reading

Technical
How to Identify and Block Referrer Spam in Website Analytics
Metrics
How to Track and Reduce Shopping Cart Abandonment with Analytics
Privacy
Google Consent Mode v2 Explained: What It Means for Your Analytics
Analytics by statpx