<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic New RUM - Custom event and session properties in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/New-RUM-Custom-event-and-session-properties/m-p/294018#M7221</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;We have just moved to the new RUM experience, and much to my surprise the new frontend settings for &lt;EM&gt;Event and session properties&lt;/EM&gt; does not seem to include the option to add custom properties -&lt;STRONG&gt; unless via the JS RUM API&lt;/STRONG&gt;. Is that really the case?&lt;/P&gt;
&lt;P&gt;We're relying heavily on session and user action properties in our frontend monitoring, mostly with CSS selectors, and we don't always have the option to modify the code in these applications (for example with out of the box services like SAP and Tableau).&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2026 11:34:16 GMT</pubDate>
    <dc:creator>reshef</dc:creator>
    <dc:date>2026-04-27T11:34:16Z</dc:date>
    <item>
      <title>New RUM - Custom event and session properties</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/New-RUM-Custom-event-and-session-properties/m-p/294018#M7221</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;We have just moved to the new RUM experience, and much to my surprise the new frontend settings for &lt;EM&gt;Event and session properties&lt;/EM&gt; does not seem to include the option to add custom properties -&lt;STRONG&gt; unless via the JS RUM API&lt;/STRONG&gt;. Is that really the case?&lt;/P&gt;
&lt;P&gt;We're relying heavily on session and user action properties in our frontend monitoring, mostly with CSS selectors, and we don't always have the option to modify the code in these applications (for example with out of the box services like SAP and Tableau).&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 11:34:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/New-RUM-Custom-event-and-session-properties/m-p/294018#M7221</guid>
      <dc:creator>reshef</dc:creator>
      <dc:date>2026-04-27T11:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: New RUM - Custom event and session properties</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/New-RUM-Custom-event-and-session-properties/m-p/294037#M7222</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In the New RUM Experience, Event and session properties for web frontends:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;must be configured/defined first, otherwise incoming properties are dropped during ingest,&lt;/LI&gt;&lt;LI&gt;and the documented way to provide values is via the JS RUM API (addEventModifier for event properties, sendSessionPropertyEvent for session properties).&lt;/LI&gt;&lt;LI&gt;there are explicit limits (for example max 20 configured properties, naming/value limits).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Everything you can find here:&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/web-frontends/additional-configuration/event-and-session-properties" target="_blank"&gt;https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/web-frontends/additional-configuration/event-and-session-properties&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Given you rely heavily on CSS-selector-based action/session properties and often can’t modify application code (for example SAP and Tableau), the important nuance is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;New RUM currently runs alongside RUM Classic, and you can’t fully migrate away from Classic yet.&lt;/LI&gt;&lt;LI&gt;Event &amp;amp; session properties are explicitly separate from RUM Classic “user action &amp;amp; session properties” (the Classic ones are where CSS selector capture lives).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Here documentation where everything is explain:&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/relationship-to-rum-classic" target="_blank"&gt;https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/relationship-to-rum-classic&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So in practice:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;DOM/CSS selector / meta-tag style capture → keep using RUM Classic user action &amp;amp; session properties.&lt;/LI&gt;&lt;LI&gt;New RUM event &amp;amp; session properties → effectively require JS API; without a way to inject or run custom JS, they won’t replace your selector-based setup 1:1.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 02 Feb 2026 16:20:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/New-RUM-Custom-event-and-session-properties/m-p/294037#M7222</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-02-02T16:20:38Z</dc:date>
    </item>
  </channel>
</rss>

