User Context and Session Data
You'll learn how to enrich error reports with user and session information so you can prioritize bugs that affect real users most.
Why User Context Matters
When an error occurs in your application, knowing who experienced it transforms debugging from guesswork into targeted problem-solving. Imagine two errors: one affecting an anonymous visitor who landed on your homepage once, another hitting a paying customer during checkout. Without context, they look identical. With user data attached, you know which to fix first.
What to Capture
Associate errors with identifying information:
- User ID: Permanent identifier from your database
- Email: Human-readable contact (hash if privacy-sensitive)
- Username or Display Name: Helps recognize patterns
- Subscription/Account Type: Free vs. paid users
- Session Data: Login timestamp, referrer, feature flags enabled
This isn't about surveillance—it's about understanding impact.
Practical Implementation
With Sentry (building on lesson 2810's setup), attach user context:
Sentry.setUser({
id: "12345",
email: "user@example.com",
username: "johndoe",
subscription: "premium"
});
Add custom session metadata:
Sentry.setContext("session", {
loginTime: new Date().toISOString(),
featureFlags: ["new-checkout", "beta-ui"],
lastAction: "clicked-submit-order"
});
Now when errors occur, they're tagged with this context automatically. You can filter, search, and prioritize: "Show me all checkout errors for premium users in the last hour."
The Impact
User context turns your error dashboard from a noise stream into an actionable queue. You'll spot patterns like "this bug only affects users with feature flag X" or "all errors come from users on accounts created before migration."
Key Takeaway: Attaching user IDs, emails, and session metadata to error reports lets you prioritize fixes by real-world impact, not just error frequency.