Set up Digital Experience Analytics in Splunk RUM

Configure Digital Experience Analytics alongside Splunk Real User Monitoring (RUM) to track key user analytics.

Follow the same process used to instrument applications for Splunk Real User Monitoring (RUM) in order to set up Digital Experience Analytics (DXA). To enable automatic source mapping of your browser, iOS, and Android applications at instrumentation time, install the splunk-rum CLI. For more information, see [NO TITLE FOUND].

Follow these steps to instrument your mobile and web applications to be analyzed using Splunk Digital Experience Analytics (DXA).

Instrument applications using the Splunk RUM agent

To instrument your application and get data into Splunk DXA, follow the same process used to instrument mobile and browser applications in Splunk RUM.

Configure the Splunk RUM agent

To use Splunk DXA capabilities, you must use version 2.0.0 or later of the browser or mobile RUM agent. For more information about configuring these agents with your Splunk RUM token, Splunk realm, application name, and deployment environment, see:

Use RUM data in Splunk Digital Experience Analytics

Configure end user tracking using the user.trackingMode setting to link RUM data to Digital Experience Analytics. This setting creates and attaches an anonymous user ID to spans. This setting is enabled by default in the browser RUM agents version 2.0 or later, iOS RUM agent version 2.0.5 or later, and Android RUM agent version 2.1.3 or later.

For more information, see:

To disable user tracking in the browser or mobile RUM agents, set the appropriate user tracking setting in either the browser or mobile RUM agent to noTracking.

(Optional) Turn on text collection on click events

Note: Text collection configuration is currently only available for the browser RUM agent. Support for the mobile RUM agent will be added in a future release.
Set up text collection to easily analyze clicks on elements defined by their text properties. Configure your instrumentation with the privacy property to set up text collection for click events. For more information, see [NO TITLE FOUND]in the Configure the Splunk Browser RUM instrumentation topic. The following examples show how to add this property:

  • Default safety (only node names recorded; zero privacy risk)

    JSON 
    {
  "maskAllText": true,
  "sensitivityRules": []
}

  • Selective unmask (all masked except safe product names)

    JSON 
    {
  "maskAllText": true,
  "sensitivityRules": [
    { "rule": "unmask", "selector": "p.product-name" }
  ]
}

  • Mixed (p masked except product labels; user profiles excluded completely)

    JSON 
    {
  "maskAllText": true,
  "sensitivityRules": [
    { "rule": "mask", "selector": "p" },
    { "rule": "unmask", "selector": "p.item-label" },
    { "rule": "exclude", "selector": "#user-profile" }
  ]
}

  • Unmasked by default, with specific mask (all text recorded except explicitly masked sensitive ones)

    JSON 
    {
  "maskAllText": false,
  "sensitivityRules": [
    { "rule": "mask", "selector": "p.sensitive" }
  ]
}
To check that your data is coming in, you need to first have application activity. Then, follow these steps to check that your data is in:

  1. Log in to Splunk Observability Cloud.

  2. Select Digital Experience and the Overview page for Digital experience analytics.

  3. Check that your application is listed in the Available applications.