User tag in User&Session menu

[RobertoMaia]

I've set up frontend User Tags via CSS selectors and Request Attributes. They work in the classic view, but in the New RUM experience (Session & User Overview), all users appear as anonymous. Does the new experience require a different tagging setup? Any guidance would be appreciated.

[t_pawlak]

Hi,

This doesn’t require a different setup in the new RUM.

Most likely you’re seeing a property/request attribute in Classic, not an actual User tag.

Make sure it’s configured as a User tag rule:
Web app → Capturing → User tags (CSS, JS, cookie, request attribute).

Also note:

• server-side attributes may not be captured for every session (Adaptive Traffic Management)
• new view shows only closed sessions (~1h delay)

[RobertoMaia]

"I am experiencing an issue where User Tags are not being reflected in the New RUM Experience. They are properly configured via CSS selectors and Request Attributes and work as expected in the classic view, but all users are listed as anonymous in the new 'Session & User Overview'. Could you please advise if a new configuration is necessary?"
maybe something like this identifyUser | RUM JavaScript API - 1.333.0

[Aaron_Schultz]

Hello,

To answer your question: yes, the new RUM experience (Session & User overview) needs its own explicit user identification, separate from the classic "User tag" rules (CSS selector / cookie / request attribute).

To get real user identities showing up in the new experience, you have two options:

1. identifyUser() JavaScript API (the one you linked): This is the most direct way to tell RUM who the current user is, and it's what drives the "User" field in the new overview.
2. Capture properties as session/user properties, per this doc: Event and session properties, Capture properties. This lets you capture the same CSS/cookie/JS values you're already using for tagging, but as properties that surface in the new experience.

So in short: keep your existing User tag config for classic if you still need it, but add either identifyUser() or an equivalent capture property to get non-anonymous users in the new Session & User overview.

Hope that helps!