Skip to main content
This guide shows you how to add user properties (user ID, email, plan, etc.) to your traces.

Quick Start

Use enrich_session() to add user context to the entire trace, or enrich_span() to add it to a specific operation.

On the Session

Add user properties that apply to the entire user interaction:

On a Span

Add user properties to a specific function or operation:

Concepts

What are User Properties?

User properties are attributes that identify or describe the user making a request. They’re stored in a dedicated user_properties namespace, displayed separately from other metadata in the dashboard. Common user properties:
  • Identifiers: user ID, email, account ID
  • Attributes: subscription plan, role, region
  • Flags: is_beta, is_internal, is_premium

User Properties vs Metadata

Both user_properties and metadata store key-value data. The difference is organizational: Use user_properties when the data describes the user. Use metadata for everything else (feature flags, request IDs, environment info).

Data Types


Learn More

Enriching Traces

Full guide to trace enrichment

Schema Reference

All namespaces and data types

SDK Reference