https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/ta-p/303682 <P><LI-TOC indent="15" liststyle="disc" maxheadinglevel="2"></LI-TOC></P> <DIV class="lia-message-template-content-zone"> <H2 class="code-line" dir="auto" data-line="2">&nbsp;</H2> <H2 id="summary" class="code-line" dir="auto" data-line="2">Summary</H2> <P class="code-line" data-line="4">By default, user sessions in the new RUM Experience (Experience Vitals) are identified by a generated ID rather than a meaningful user name. This article explains how to capture a user name from the page using a CSS selector, verify the capture, and then use OpenPipeline® processing rules to map that value to the user identifier field so it appears in the User and sessions view.</P> <P class="code-line" data-line="4"><EM><STRONG style="font-family: inherit;">Note:</STRONG><SPAN>&nbsp;</SPAN><SPAN>This configuration applies only to newly ingested data. Existing sessions are not retroactively updated.</SPAN></EM></P> <H2 class="code-line" dir="auto" data-line="8">&nbsp;</H2> <H2 id="prerequisites" class="code-line" dir="auto" data-line="8">Prerequisites</H2> <UL class="code-line" dir="auto" data-line="10"> <LI class="code-line" dir="auto" data-line="10">You have a Dynatrace SaaS environment with the new RUM Experience (Experience Vitals) turned on.</LI> <LI class="code-line" dir="auto" data-line="11">You have the<SPAN>&nbsp;</SPAN><STRONG>Modify RUM settings</STRONG><SPAN>&nbsp;</SPAN>and<SPAN>&nbsp;</SPAN><STRONG>Modify environment configuration</STRONG><SPAN>&nbsp;</SPAN>permissions.</LI> <LI class="code-line" dir="auto" data-line="12">You know the CSS selector that targets the DOM element containing the user name on your page.</LI> <LI class="code-line" dir="auto" data-line="13">OpenPipeline is available in your environment.</LI> </UL> <H2 class="code-line" dir="auto" data-line="15">&nbsp;</H2> <H2 id="part-1-capture-the-user-name-as-an-event-property" class="code-line" dir="auto" data-line="15">Part 1: Capture the user name as an event property</H2> <P class="code-line" data-line="17">In this part, you configure the application in Experience Vitals to read the user name from the page using a CSS selector and store it as an event property.</P> <OL class="code-line" dir="auto" data-line="19"> <LI class="code-line" dir="auto" data-line="19">In Dynatrace, go to<SPAN>&nbsp;</SPAN><STRONG>Experience Vitals</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>Overview</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>Web</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="20">Select the application you want to configure.</LI> <LI class="code-line" dir="auto" data-line="21">Select the<SPAN>&nbsp;</SPAN><STRONG>Settings</STRONG><SPAN>&nbsp;</SPAN>tab.</LI> <LI class="code-line" dir="auto" data-line="22">Select<SPAN>&nbsp;</SPAN><STRONG>Capture properties</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="23">Select<SPAN>&nbsp;</SPAN><STRONG>+ New property</STRONG>. The<SPAN>&nbsp;</SPAN><STRONG>Edit event property</STRONG><SPAN>&nbsp;</SPAN>dialog opens.</LI> <LI class="code-line" dir="auto" data-line="24">Under<SPAN>&nbsp;</SPAN><STRONG>Define event property key</STRONG>, set the<SPAN>&nbsp;</SPAN><STRONG>Property key</STRONG><SPAN>&nbsp;</SPAN>to a name you will reference later, for example<SPAN>&nbsp;</SPAN><CODE>username</CODE>.</LI> <LI class="code-line" dir="auto" data-line="25">Under<SPAN>&nbsp;</SPAN><STRONG>Define source</STRONG>, configure the two capture rows: <OL class="code-line" dir="auto" data-line="26"> <LI class="code-line" dir="auto" data-line="26">In the first row, set<SPAN>&nbsp;</SPAN><STRONG>Capture type</STRONG><SPAN>&nbsp;</SPAN>to<SPAN>&nbsp;</SPAN><STRONG>CSS Selector</STRONG><SPAN>&nbsp;</SPAN>and enter your CSS selector in the<SPAN>&nbsp;</SPAN><STRONG>Identifier</STRONG><SPAN>&nbsp;</SPAN>field, for example<SPAN>&nbsp;</SPAN><CODE>#root &gt; div &gt; header &gt; div &gt; p</CODE>. This tells Dynatrace which DOM element to read.</LI> <LI class="code-line" dir="auto" data-line="27">Select<SPAN>&nbsp;</SPAN><STRONG>+ Add a processing step</STRONG>. A second row appears.</LI> <LI class="code-line" dir="auto" data-line="28">In the second row, set<SPAN>&nbsp;</SPAN><STRONG>Capture type</STRONG><SPAN>&nbsp;</SPAN>to<SPAN>&nbsp;</SPAN><STRONG>Access property</STRONG><SPAN>&nbsp;</SPAN>and set the<SPAN>&nbsp;</SPAN><STRONG>Identifier</STRONG><SPAN>&nbsp;</SPAN>to<SPAN>&nbsp;</SPAN><CODE>innerText</CODE>. This extracts the visible text content of the matched element.<span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Aaron_Schultz_1-1787507722826.png"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/34113iD55F86A4AD94AF7C/image-size/large?v=v2&amp;px=999" alt="Aaron_Schultz_1-1787507722826.png" title="Aaron_Schultz_1-1787507722826.png" /></span></LI> </OL> </LI> <LI class="code-line" dir="auto" data-line="29">Select<SPAN>&nbsp;</SPAN><STRONG>Save</STRONG>.</LI> </OL> <P><EM><STRONG style="font-family: inherit;">Tip:</STRONG><SPAN>&nbsp;</SPAN><SPAN>To verify the selector before saving, open your browser's developer tools, go to the</SPAN><SPAN>&nbsp;</SPAN><STRONG style="font-family: inherit;">Console</STRONG><SPAN>&nbsp;</SPAN><SPAN>tab, and run</SPAN><SPAN>&nbsp;</SPAN><CODE>document.querySelector('YOUR_SELECTOR').innerText</CODE><SPAN>. If the correct user name appears, the selector is valid.</SPAN></EM></P> <H2 class="code-line" dir="auto" data-line="35">&nbsp;</H2> <H2 id="part-2-confirm-the-property-is-being-captured" class="code-line" dir="auto" data-line="35">Part 2: Confirm the property is being captured</H2> <P class="code-line" data-line="37">Before setting up OpenPipeline, confirm that the event property arrives in Dynatrace by querying for it in a Notebook.</P> <OL class="code-line" dir="auto" data-line="39"> <LI class="code-line" dir="auto" data-line="39"> <P class="code-line" data-line="39">In Dynatrace, go to<SPAN>&nbsp;</SPAN><STRONG>Notebooks</STRONG><SPAN>&nbsp;</SPAN>and open a new notebook.</P> </LI> <LI class="code-line" dir="auto" data-line="40"> <P class="code-line" data-line="40">Add a DQL tile and run the following query, replacing<SPAN>&nbsp;</SPAN><CODE>username</CODE><SPAN>&nbsp;</SPAN>with the property key you configured in Part 1:</P> <PRE>fetch user.events<BR />| filter isNotNull(event_properties.username)<BR />| fieldsAdd event_properties.username</PRE> </LI> <LI class="code-line" dir="auto" data-line="48"> <P class="code-line" data-line="48">Confirm that the<SPAN>&nbsp;</SPAN><CODE>event_properties.username</CODE><SPAN>&nbsp;</SPAN>column is populated with the expected user names.<span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Aaron_Schultz_2-1787507951836.png"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/34114i76EDC88F7F37D24E/image-size/large?v=v2&amp;px=999" alt="Aaron_Schultz_2-1787507951836.png" title="Aaron_Schultz_2-1787507951836.png" /></span><EM style="font-family: inherit;"><STRONG>Note:</STRONG>&nbsp;From the image, you can see that it also captured additional text, "Hi, " that you may not want. Do not worry, as we can create a clean up rule later.</EM></P> <P>&nbsp;</P> </LI> </OL> <P class="code-line" data-line="50">If the column is empty, go back to Part 1 and verify the CSS selector and the<SPAN>&nbsp;</SPAN><STRONG>innerText</STRONG><SPAN>&nbsp;</SPAN>processing step are configured correctly. Generate new user actions in the monitored application (for example, load a page while signed in) and then re-run the query.</P> <H2 class="code-line" dir="auto" data-line="52">&nbsp;</H2> <H2 id="part-3-create-a-pipeline-to-map-the-user-name" class="code-line" dir="auto" data-line="52">Part 3: Create a pipeline to map the user name</H2> <P class="code-line" data-line="54">In this part, you create an OpenPipeline pipeline under<SPAN>&nbsp;</SPAN><STRONG>User events</STRONG><SPAN>&nbsp;</SPAN>and add a DQL processing rule to map the captured property to the<SPAN>&nbsp;</SPAN><CODE>user.identifier</CODE><SPAN>&nbsp;</SPAN>field.</P> <OL class="code-line" dir="auto" data-line="56"> <LI class="code-line" dir="auto" data-line="56">In Dynatrace, go to<SPAN>&nbsp;</SPAN><STRONG>Settings</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>Process and contextualize</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>OpenPipeline</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="57">Under<SPAN>&nbsp;</SPAN><STRONG>User events</STRONG>, select the<SPAN>&nbsp;</SPAN><STRONG>Pipelines</STRONG><SPAN>&nbsp;</SPAN>tab and select<SPAN>&nbsp;</SPAN><STRONG>+ Pipeline</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="58">Give the pipeline a descriptive name, for example<SPAN>&nbsp;</SPAN><CODE>Map user name</CODE>.</LI> <LI class="code-line" dir="auto" data-line="59">In the<SPAN>&nbsp;</SPAN><STRONG>Processing</STRONG><SPAN>&nbsp;</SPAN>stage, select<SPAN>&nbsp;</SPAN><STRONG>Add rule</STRONG><SPAN>&nbsp;</SPAN>and set the processor type to<SPAN>&nbsp;</SPAN><STRONG>DQL</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="60">Configure the rule: <UL class="code-line" dir="auto" data-line="61"> <LI class="code-line" dir="auto" data-line="61"><STRONG>Name</STRONG>: Enter a descriptive name, for example<SPAN>&nbsp;</SPAN><CODE>Set user identifier from username</CODE>.</LI> <LI class="code-line" dir="auto" data-line="62"><STRONG>Matching condition</STRONG>: Enter the following to only process events where the property was captured: <PRE>isNotNull(event_properties.username)</PRE> </LI> <LI class="code-line" dir="auto" data-line="66"><STRONG>DQL processor definition</STRONG>: Enter the following expression: <PRE>fieldsAdd user.identifier = event_properties.username</PRE> <span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Aaron_Schultz_3-1787508208221.png"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/34115i3ED1FC236641AD34/image-size/large?v=v2&amp;px=999" alt="Aaron_Schultz_3-1787508208221.png" title="Aaron_Schultz_3-1787508208221.png" /></span> <P class="code-line" data-line="70"><EM><STRONG>Note:</STRONG>&nbsp;If your CSS selector captures additional text alongside the user name—for example, a greeting prefix such as "Hi, Priya", use&nbsp;<CODE>replaceString</CODE>&nbsp;to strip the unwanted text:&nbsp;<CODE>fieldsAdd user.identifier = replaceString(event_properties.username, "Hi, ", "")</CODE></EM></P> </LI> </UL> </LI> <LI class="code-line" dir="auto" data-line="71">Select<SPAN>&nbsp;</SPAN><STRONG>Save</STRONG><SPAN>&nbsp;</SPAN>on the rule.</LI> </OL> <H2 class="code-line" dir="auto" data-line="52">&nbsp;</H2> <H2 id="part-3-create-a-pipeline-to-map-the-user-name" class="code-line" dir="auto" data-line="52"><SPAN>Part 4: Create a routing rule to direct data through the new pipeline</SPAN></H2> <P class="code-line" data-line="76">OpenPipeline uses the default pipeline unless a routing rule sends data to a specific pipeline. In this part, you create a routing rule that directs the relevant user events through the pipeline you created in Part 3.</P> <OL class="code-line" dir="auto" data-line="78"> <LI class="code-line" dir="auto" data-line="78">In Dynatrace, go to<SPAN>&nbsp;</SPAN><STRONG>Settings</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>Process and contextualize</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>OpenPipeline</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="79">Under<SPAN>&nbsp;</SPAN><STRONG>User events</STRONG>, select<SPAN>&nbsp;</SPAN><STRONG>Dynamic Routing</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="80">Select<SPAN>&nbsp;</SPAN><STRONG>+ Dynamic route</STRONG>. The<SPAN>&nbsp;</SPAN><STRONG>Edit Dynamic route</STRONG><SPAN>&nbsp;</SPAN>dialog opens.</LI> <LI class="code-line" dir="auto" data-line="81">Configure the route: <UL class="code-line" dir="auto" data-line="82"> <LI class="code-line" dir="auto" data-line="82"><STRONG>Name</STRONG>: Enter a descriptive name, for example<SPAN>&nbsp;</SPAN><CODE>Change user names</CODE>.</LI> <LI class="code-line" dir="auto" data-line="83"><STRONG>Matching condition</STRONG>: Enter a condition that matches the application you want this pipeline to process: <PRE>matchesValue(frontend.name, "Your App Name")</PRE> </LI> <LI class="code-line" dir="auto" data-line="87"><STRONG>Pipeline</STRONG>: Select the pipeline you created in Part 3.<span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Aaron_Schultz_4-1787508330885.png"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/34116iD0827AAA6386C1B7/image-size/large?v=v2&amp;px=999" alt="Aaron_Schultz_4-1787508330885.png" title="Aaron_Schultz_4-1787508330885.png" /></span> <P>&nbsp;</P> </LI> </UL> </LI> <LI class="code-line" dir="auto" data-line="88">Select<SPAN>&nbsp;</SPAN><STRONG>Save</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="89">If multiple routing rules exist, drag the new rule above any others that might match the same data so it takes priority.</LI> </OL> <H2 class="code-line" dir="auto" data-line="91">&nbsp;</H2> <H2 id="part-5-verify-user-names-appear-in-the-user-sessions-view" class="code-line" dir="auto" data-line="91">Part 5: Verify user names appear in the User sessions view</H2> <P class="code-line" data-line="93">After completing Parts 1–4, generate new user sessions by interacting with the monitored application while signed in. Then confirm the user name appears in Experience Vitals.</P> <OL class="code-line" dir="auto" data-line="95"> <LI class="code-line" dir="auto" data-line="95">In Dynatrace, go to<SPAN>&nbsp;</SPAN><STRONG>Experience Vitals</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>Overview</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>Web</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="96">Select the application.</LI> <LI class="code-line" dir="auto" data-line="97">Select<SPAN>&nbsp;</SPAN><STRONG>Open with User &amp; Sessions</STRONG><SPAN>&nbsp;</SPAN>to open the session list.</LI> <LI class="code-line" dir="auto" data-line="98">Select a<SPAN>&nbsp;</SPAN><STRONG>Recent sessions</STRONG><SPAN>&nbsp;</SPAN>on from the top left of the page.</LI> <LI class="code-line" dir="auto" data-line="99">Confirm the<SPAN>&nbsp;</SPAN><STRONG>User Identifier</STRONG><SPAN>&nbsp;</SPAN>field shows the name captured from the page.</LI> </OL> <span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Aaron_Schultz_5-1787508479901.png"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/34117i4C66CEF20AAF4965/image-size/large?v=v2&amp;px=999" alt="Aaron_Schultz_5-1787508479901.png" title="Aaron_Schultz_5-1787508479901.png" /></span> <P>&nbsp;</P> <P class="code-line" data-line="101"><EM><STRONG>Note:</STRONG>&nbsp;Only sessions ingested after the pipeline and routing rule were published display the mapped user name. Earlier sessions retain the generated identifier.</EM></P> <P class="code-line" data-line="103">You can also verify with DQL:</P> <PRE>fetch user.sessions, from: now()-2h<BR />| fields<BR />user.identifier,<BR />dt.rum.session.id,<BR />frontend.name,<BR />dt.rum.application.type<BR />| filter isNotNull(user.identifier)<BR />| limit 100</PRE> <H2 class="code-line" dir="auto" data-line="116">&nbsp;</H2> <H2 id="troubleshooting" class="code-line" dir="auto" data-line="116">Troubleshooting</H2> <P class="code-line" data-line="118"><STRONG>The<SPAN>&nbsp;</SPAN><CODE>event_properties.username</CODE><SPAN>&nbsp;</SPAN>column is empty/null in the Notebook query.</STRONG></P> <UL class="code-line" dir="auto" data-line="120"> <LI class="code-line" dir="auto" data-line="120">Confirm the CSS selector resolves to a visible element at the time the page loads. Elements rendered asynchronously by a JavaScript framework may not be available when the RUM agent first runs. Try interacting with the page to trigger a user action after the element appears.</LI> <LI class="code-line" dir="auto" data-line="121">Confirm the<SPAN>&nbsp;</SPAN><STRONG>Access property</STRONG><SPAN>&nbsp;</SPAN>step is set to<SPAN>&nbsp;</SPAN><STRONG>innerText</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="122">Confirm the property key is spelled correctly in the query (keys are case-sensitive).</LI> </UL> <P class="code-line" data-line="124"><STRONG>The event property is captured but<SPAN>&nbsp;</SPAN><CODE>user.identifier</CODE><SPAN>&nbsp;</SPAN>is still empty/<SPAN>Anonymous</SPAN> after setting up the pipeline.</STRONG></P> <UL class="code-line" dir="auto" data-line="126"> <LI class="code-line" dir="auto" data-line="126">Confirm the routing rule is targeting the correct pipeline and is positioned above other matching rules.</LI> <LI class="code-line" dir="auto" data-line="127">Confirm the pipeline has been published. Unpublished pipelines do not process data.</LI> <LI class="code-line" dir="auto" data-line="128">Confirm the DQL expression in the processing rule uses the same property key as the one in Part 1.</LI> <LI class="code-line" dir="auto" data-line="128">Confirm that you have the <A href="https://docs.dynatrace.com/docs/shortlink/rum-on-grail-permissions#field-permissions" target="_blank">correct permission</A>, as&nbsp;user.events and user.sessions are sensitive fields that required additional permission for viewing.&nbsp;</LI> </UL> <P class="code-line" data-line="130"><STRONG>Sessions show the user name in DQL but not in the Experience Vitals UI.</STRONG></P> <UL class="code-line" dir="auto" data-line="132"> <LI class="code-line" dir="auto" data-line="132">Allow a few minutes for the UI to reflect newly ingested data.</LI> <LI class="code-line" dir="auto" data-line="133">Confirm you are viewing a session that was ingested after the pipeline was published.</LI> </UL> <H2 class="code-line" dir="auto" data-line="135">&nbsp;</H2> <H2 id="whats-next" class="code-line" dir="auto" data-line="135">What's next</H2> <P class="code-line" data-line="137">If this article did not resolve your issue, open a support case and include:</P> <UL class="code-line" dir="auto" data-line="139"> <LI class="code-line" dir="auto" data-line="139">The CSS selector you configured and a screenshot of the matching DOM element in browser developer tools.</LI> <LI class="code-line" dir="auto" data-line="140">A screenshot of the<SPAN>&nbsp;</SPAN><STRONG>Capture properties</STRONG><SPAN>&nbsp;</SPAN>configuration for the application.</LI> <LI class="code-line" dir="auto" data-line="141">A screenshot of the OpenPipeline pipeline and routing rule configuration.</LI> <LI class="code-line" dir="auto" data-line="142">The output of the DQL query from Part 2 showing the current state of<SPAN>&nbsp;</SPAN><CODE>event_properties.username</CODE>.</LI> <LI class="code-line" dir="auto" data-line="143">The output of the DQL query from Part 5 showing the current state of<SPAN>&nbsp;</SPAN><CODE>user.identifier</CODE>.</LI> </UL> <P class="code-line" data-line="145"><STRONG>Additional resources:</STRONG></P> <UL class="code-line" dir="auto" data-line="147"> <UL class="code-line" dir="auto" data-line="147"> <LI class="code-line" dir="auto" data-line="147"><A href="https://docs.dynatrace.com/docs/shortlink/new-rum-event-and-session-properties-web" target="_blank" rel="noopener" data-href="https://docs.dynatrace.com/docs/shortlink/new-rum-event-and-session-properties-web">Event and session properties for web</A></LI> <LI class="code-line" dir="auto" data-line="148"><A href="https://docs.dynatrace.com/docs/shortlink/openpipeline-processing" target="_blank" rel="noopener" data-href="https://docs.dynatrace.com/docs/shortlink/openpipeline-processing">OpenPipeline processing rules</A></LI> <LI class="code-line" dir="auto" data-line="148"><A href="https://docs.dynatrace.com/docs/shortlink/semantic-dictionary-sensitive-user-events-and-user-sessions-fields" target="_blank">Sensitive user.events and user.sessions fields</A></LI> <LI class="code-line" dir="auto" data-line="148"><A href="https://docs.dynatrace.com/docs/observe/digital-experience/rum/permissions#field-permissions" target="_blank">Field Permissions</A></LI> </UL> </UL> </DIV> Thu, 27 Aug 2026 07:21:19 GMT Aaron_Schultz 2026-08-27T07:21:19Z https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/ta-p/303682 <P><LI-TOC indent="15" liststyle="disc" maxheadinglevel="2"></LI-TOC></P> <DIV class="lia-message-template-content-zone"> <P>*<EM>Use a table of contents for longer articles.&nbsp;</EM></P> <H2>Summary</H2> <P><EM>*This is a mandatory section.</EM></P> <P><EM>Short description of which part of the Dynatrace platform the article refers to and what kind of problem it will help resolve/ task it will describe.</EM></P> <P>&nbsp;</P> <H2>Problem</H2> <P><EM>*This is a mandatory section.</EM></P> <P><EM>Provide a precise description of the problem/ task to be described. Use anonymized screenshots, and include text for&nbsp;important messages, errors, or information that will help the customer find this article when searching.</EM></P> <P>&nbsp;</P> <H2>Troubleshooting steps</H2> <P><EM>*This section can be omitted as necessary.</EM></P> <P><EM>Explain what troubleshooting steps should be taken to ensure the problem matches this article.</EM></P> <P>&nbsp;</P> <H2>Resolution</H2> <P><EM>*This section can be omitted for articles that guide customers on case creation.</EM></P> <P><EM>Explain the solution or all possible solutions resulting from the troubleshooting steps.<BR /><BR /></EM></P> <H2>What's next</H2> <P><EM>*This is a mandatory section. Customers need a way to respond or follow up if they have questions.&nbsp;</EM></P> <P><EM>Explain what to do if the article didn't help.&nbsp;</EM><EM>Note that there are multiple options available, including:</EM></P> <OL> <LI><EM><STRONG>Opening a chat or support case&nbsp;</STRONG>- be as specific as possible about the information the customer should include in the case.&nbsp;</EM><EM>Use the following formula and fill or change the bullet points:<BR /><BR /></EM> If this article didn't help, <STRONG>create a chat or open a support case</STRONG> <UL> <LI>Mention that you reviewed this article.</LI> <LI>Include the following details: <UL> <LI>Link to XYZ</LI> <LI>Screenshot of XYZ</LI> <LI>Information about XYZ</LI> </UL> </LI> </UL> </LI> <LI><EM><STRONG>Suggesting Product Idea</STRONG> - encourage the customer to suggest/ vote for a Product Idea explaining their business use case.<BR /></EM> <DIV>Please submit a Product Idea with detailed information about your request and use case in the Product Ideas forum. Our Product Management team regularly reviews these suggestions:</DIV> <A href="https://community.dynatrace.com/t5/Dynatrace-product-ideas/idb-p/DynatraceProductIdeas" target="_blank" rel="noopener">https://community.dynatrace.com/t5/Dynatrace-product-ideas/idb-p/DynatraceProductIdeas</A></LI> <LI><STRONG><EM>Explain this will change in the future </EM></STRONG><EM>- explain that this behavior will change in a future release. (No product idea / support case needed)</EM></LI> <LI><STRONG><EM>Alternatives -</EM></STRONG><EM>&nbsp;any other actions or links to other articles that could move the customer forward.</EM></LI> </OL> <H2><BR />Related reading</H2> <P><EM>*Link this article to other relevant configuration or troubleshooting guides, including any applicable troubleshooting maps.<BR />:open_book:&nbsp;&nbsp;</EM><A href="https://community.dynatrace.com/t5/Troubleshooting/" target="_blank" rel="noopener">XXX Troubleshooting Map</A></P> <P>:open_book:&nbsp; Link 1</P> <P>:open_book:&nbsp; Link 2</P> <P>:open_book:&nbsp; Link 3</P> <P>:open_book:&nbsp; Link 4</P> </DIV> Thu, 27 Aug 2026 07:21:19 GMT https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/ta-p/303682 Aaron_Schultz 2026-08-27T07:21:19Z https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/tac-p/303761#M1185 <P>Thank you!&nbsp;<img class="lia-deferred-image lia-image-emoji" src="https://community.dynatrace.com/html/@9BD876A77FEF3D5EF4BC972CF8A97CB1/images/emoticons/take_my_money.png" alt=":take_my_money:" title=":take_my_money:" /></P> Tue, 25 Aug 2026 12:26:36 GMT https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/tac-p/303761#M1185 AntonPineiro 2026-08-25T12:26:36Z https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/tac-p/303770#M1186 <P><a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/43791">@Aaron_Schultz</a>&nbsp;I know this is more a question for the PM, but since the CSS capturing is there, why did they not keep the option to capture user tags in the same way as it was in RUM classic?</P> Tue, 25 Aug 2026 16:10:11 GMT https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/tac-p/303770#M1186 Julius_Loman 2026-08-25T16:10:11Z https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/tac-p/303826#M1191 <P><a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/3364">@Julius_Loman</a> My apologies, but unfortunately, I do not have an answer to that. Someone else would have to answer that question.</P> Wed, 26 Aug 2026 19:22:30 GMT https://community.dynatrace.com/t5/Troubleshooting/How-to-display-user-names-in-new-RUM-Experience-using-the-UI/tac-p/303826#M1191 Aaron_Schultz 2026-08-26T19:22:30Z