https://community.dynatrace.com/t5/Troubleshooting/Session-properties-missing-in-the-new-RUM-Experience/ta-p/303178 <P><LI-TOC indent="15" liststyle="disc" maxheadinglevel="2"></LI-TOC></P> <DIV class="lia-message-template-content-zone"> <H2>Summary</H2> <P class="code-line" data-line="4">This article applies to Dynatrace SaaS customers using Real User Monitoring (RUM). It explains why <A href="https://docs.dynatrace.com/docs/observe/digital-experience/rum-classic/web-applications/additional-configuration/define-user-action-and-session-properties" target="_blank" rel="noopener">session and action properties</A> configured in <A href="https://docs.dynatrace.com/docs/observe/digital-experience/rum-classic" target="_blank" rel="noopener">RUM Classic</A> are not visible in the <A href="https://docs.dynatrace.com/docs/observe/digital-experience/rum" target="_blank" rel="noopener">new RUM Experience</A>, and how to reconfigure them so they appear correctly.</P> <H2>Problem&nbsp;</H2> <P class="code-line" data-line="8">After you turn on the new RUM Experience, session and action properties that were previously visible in the RUM Classic view are no longer visible in the new RUM Experience view.</P> <P class="code-line" data-line="10">This is expected behavior. Session and action properties configured in RUM Classic are not automatically migrated to the new RUM Experience. They must be reconfigured manually using the new event and session properties configuration.</P> <H2>Troubleshooting steps</H2> <P class="code-line" data-line="14">If you are simply not seeing session properties in the new RUM Experience, follow these steps to confirm the problem matches this article before proceeding to the resolution.</P> <P class="code-line" data-line="16"><STRONG>Step 1: Confirm properties have not already been configured in the new RUM Experience</STRONG></P> <OL class="code-line" dir="auto" data-line="18"> <LI class="code-line" dir="auto" data-line="18">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="19">Select the affected frontend application.</LI> <LI class="code-line" dir="auto" data-line="20">Select the<SPAN>&nbsp;</SPAN><STRONG>Settings</STRONG><SPAN>&nbsp;</SPAN>tab.</LI> <LI class="code-line" dir="auto" data-line="21">Select<SPAN>&nbsp;</SPAN><STRONG>Capture properties</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="22">The page has two sections: <UL class="code-line" dir="auto" data-line="23"> <LI class="code-line" dir="auto" data-line="23"><STRONG>Captured event properties</STRONG>: lists properties captured automatically from the page using CSS selectors, DOM attributes, cookies, or JavaScript variables. A counter shows how many are configured out of the 100-property limit.</LI> <LI class="code-line" dir="auto" data-line="24"><STRONG>Allowed API-reported properties</STRONG>: lists properties reported via the JavaScript API. A counter shows how many are configured out of the 200-property limit.</LI> </UL> </LI> <LI class="code-line" dir="auto" data-line="25">Check both sections for the properties you expect to see. If both sections show "No properties configured," no event or session properties have been set up for this application in the new RUM Experience.</LI> </OL> <P class="code-line" data-line="27">If both sections show no properties configured, follow the resolution steps below.</P> <H2>Resolution</H2> <P class="code-line" data-line="30">RUM Classic and the new RUM Experience use separate property configuration models. Reconfigure your session and action properties as event and session properties directly in the new RUM Experience. The same capture methods are available (CSS selectors, JavaScript variables, cookies, and more), so you can re-create your existing properties using the new configuration interface.</P> <OL class="code-line" dir="auto" data-line="37"> <LI class="code-line" dir="auto" data-line="33">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="34">Select the frontend application you want to configure.</LI> <LI class="code-line" dir="auto" data-line="35">Go to<SPAN>&nbsp;</SPAN><STRONG>Settings</STRONG><SPAN>&nbsp;</SPAN>&gt;<SPAN>&nbsp;</SPAN><STRONG>Capture properties</STRONG>.</LI> <LI class="code-line" dir="auto" data-line="36">Select<SPAN>&nbsp;</SPAN><STRONG>Add property</STRONG><SPAN>&nbsp;</SPAN>and configure each property using the appropriate capture method: <UL class="code-line" dir="auto" data-line="37"> <LI class="code-line" dir="auto" data-line="37"><STRONG>CSS selector</STRONG>: extracts a value from a DOM element</LI> <LI class="code-line" dir="auto" data-line="38"><STRONG>DOM attribute</STRONG>: reads an attribute from a DOM element</LI> <LI class="code-line" dir="auto" data-line="39"><STRONG>Cookie</STRONG>: retrieves a cookie value</LI> <LI class="code-line" dir="auto" data-line="40"><STRONG>JavaScript variable</STRONG>: reads a value from the<SPAN>&nbsp;</SPAN><CODE>window</CODE><SPAN>&nbsp;</SPAN>object or a JavaScript variable</LI> </UL> </LI> <LI class="code-line" dir="auto" data-line="41">If your RUM Classic configuration used the JavaScript API to report properties, add those property names to the allowlist under the<SPAN>&nbsp;</SPAN><STRONG>API-reported properties</STRONG><SPAN>&nbsp;</SPAN>section. Property names must use only letters (A–Z, a–z), numbers (0–9), underscores (<CODE>_</CODE>), and dots (<CODE>.</CODE>), and must be prefixed with<SPAN>&nbsp;</SPAN><CODE>event_properties.</CODE><SPAN>&nbsp;</SPAN>or<SPAN>&nbsp;</SPAN><CODE>session_properties.</CODE><SPAN>&nbsp;</SPAN>in your code.</LI> <LI class="code-line" dir="auto" data-line="42">Repeat for each application and each property you want to carry over from RUM Classic.</LI> </OL> <BLOCKQUOTE class="code-line" dir="auto" data-line="58"> <P class="code-line" data-line="44"><STRONG>Note:</STRONG><SPAN>&nbsp;</SPAN>Steps within a single property definition run in sequence, with each step passing its output to the next. This allows you to chain operations, such as reading a cookie value and then parsing it as JSON.</P> </BLOCKQUOTE> <P class="code-line" data-line="46">After configuration, session properties are visible at the individual user session level. To view them, go to<SPAN>&nbsp;</SPAN><STRONG>Experience Vitals</STRONG><SPAN>&nbsp;</SPAN>and open a specific user session.</P> <BLOCKQUOTE class="code-line" dir="auto" data-line="48"> <P class="code-line" data-line="48"><STRONG>Note:</STRONG><SPAN>&nbsp;</SPAN>Session properties are not available on live sessions. If you cannot find the properties, make sure the session is complete before checking.<SPAN>&nbsp;</SPAN></P> </BLOCKQUOTE> <LI-CODE lang="markup">fetch user.sessions | fields session_properties | limit 10</LI-CODE> <P class="code-line" data-line="60">For a full reference on the new configuration options, see<SPAN>&nbsp;</SPAN><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>.</P> <H2>What's next</H2> <P class="code-line" data-line="50">If this article did not help, open a support case, mention that this article was used, and provide the following in the case (include a direct link for each item where possible):</P> <UL class="code-line" dir="auto" data-line="52"> <LI class="code-line" dir="auto" data-line="52">Screenshot of the<SPAN>&nbsp;</SPAN><STRONG>Session and action properties</STRONG><SPAN>&nbsp;</SPAN>page in RUM Classic for the affected application</LI> <LI class="code-line" dir="auto" data-line="53">Screenshot of the<SPAN>&nbsp;</SPAN><STRONG>Capture properties</STRONG><SPAN>&nbsp;</SPAN>page in the new RUM Experience for the same application</LI> <LI class="code-line" dir="auto" data-line="54">The name of the affected web application or frontend</LI> </UL> <P class="code-line" data-line="70"><STRONG>Additional resources:</STRONG></P> <UL class="code-line" dir="auto" data-line="72"> <LI class="code-line" dir="auto" data-line="58"><A href="https://docs.dynatrace.com/docs/shortlink/user-session-properties" target="_blank" rel="noopener" data-href="https://docs.dynatrace.com/docs/shortlink/user-session-properties">Session and action properties (RUM Classic)</A></LI> <LI class="code-line" dir="auto" data-line="59"><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 (new RUM Experience)</A></LI> </UL> </DIV> Thu, 13 Aug 2026 07:45:35 GMT Aaron_Schultz 2026-08-13T07:45:35Z https://community.dynatrace.com/t5/Troubleshooting/Session-properties-missing-in-the-new-RUM-Experience/ta-p/303178 <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 ticket 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 did not help.&nbsp;</EM><EM>Note that there are multiple options available, including:</EM></P> <OL> <LI><EM><STRONG>Opening a support ticket</STRONG> - be as specific as possible about the information the customer should include in the ticket.&nbsp;</EM> If this article did not help, please open a support ticket, mention that this article was used and provide the following in the ticket: <UL> <LI>link to XYZ</LI> <LI>screenshot of XYZ</LI> <LI>information about XYZ</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.</EM></LI> <LI><EM><STRONG>Explain this will change in the future</STRONG> - explain that this behaviour will change in a future release. (No product idea / support ticket needed)</EM></LI> <LI><EM><STRONG>Alternatives -</STRONG>&nbsp;any other actions or links to other articles that could move the customer forward.</EM></LI> </OL> <P>&nbsp;</P> <P><EM>*If it exists, link this article to the relevant troubleshooting map using the following guideline</EM></P> <H3>More articles can be found on the <A href="https://community.dynatrace.com/t5/Troubleshooting/" target="_self">XXX Troubleshooting Map</A></H3> </DIV> Thu, 13 Aug 2026 07:45:35 GMT https://community.dynatrace.com/t5/Troubleshooting/Session-properties-missing-in-the-new-RUM-Experience/ta-p/303178 Aaron_Schultz 2026-08-13T07:45:35Z