Set up Digital Experience Analytics

Configure Digital Experience Analytics to run in your environment.

Attention:

Alpha features described in this document are provided by Splunk to you "as is" without any warranties, maintenance and support, or service-level commitments. Splunk makes this alpha feature available in its sole discretion and may discontinue it at any time. These documents are not yet publicly available and we ask that you keep such information confidential. Use of alpha features is subject to the Splunk Pre-Release Agreement for Hosted Services.

Follow the same process used to instrument applications for Splunk Real User Monitoring (RUM) in order to set up Digital Experience Analytics (DEA). To enable automatic source mapping of your browser, iOS, and Android applications at instrumentation time, install the splunk-rum CLI. For more information, see Install the splunk-rum CLI .
Install version 1.1.0 or later of the Splunk Browser RUM agent to use DEA capabilities. For more information, see Decide which version to run in your environment.

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

Instrument applications using the Splunk RUM agent

To instrument your application and get data into Splunk DEA, follow the same process used to instrument browser applications in Splunk RUM. For more information, see Browser-based web applications. Currently, only browser-based applications are supported for the Alpha release.

Configure the Splunk RUM agent settings

To use Splunk DEA capabilities, add a custom user.trackingMode property to the agent instrumentation. Without this property, you won't be able to view or monitor applications in DEA. Additionally, you must use version 1.1 or later of the Browser RUM agent. The following examples show how to add this property:

CDN

<script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.js" crossorigin="anonymous"></script>
<script>
   SplunkRum.init({
      realm: '<realm>',
      rumAccessToken: '<your_rum_token>',
      applicationName: '<application-name>',
     user: {
         trackingMode: 'anonymousTracking'
      },
   });
</script>

npm

import SplunkOtelWeb from '@splunk/otel-web';

SplunkOtelWeb.init({
   beaconEndpoint: 'https://rum-ingest..signalfx.com/v1/rum',
   rumAccessToken: '<your_rum_token>',
   applicationName: '<application-name>',
   user: {
      trackingMode: 'anonymousTracking'
   },
});

(Optional) Turn on text collection on click events

Set up text collection to easily analyze clicks on elements defined by their text properties. The following examples show how to add this property:

CDN

<script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.js" crossorigin="anonymous"></script>
<script>
  SplunkRum.init({
      realm: '<realm>',
      rumAccessToken: '<your_rum_token>',
      applicationName: '<application-name>',
      user: {
         trackingMode: 'anonymousTracking',
      },
     privacy: {
	     maskAllText: false,
	     sensitivityRules: [
		   { rule: 'mask', selector: 'h1' } // This selector: h1 rule is an example of how to explicitly mask specific elements.
	     ]
      },
   });
</script>

npm

import SplunkOtelWeb from '@splunk/otel-web';

SplunkOtelWeb.init({
   beaconEndpoint: 'https://rum-ingest..signalfx.com/v1/rum',
   rumAccessToken: '<your_rum_token>',
   applicationName: '<application-name>',
   user: {
      trackingMode: 'anonymousTracking',
   },
   privacy: {
      maskAllText: false,
      sensitivityRules: [
         { rule: 'mask', selector: 'h1' }
      ],
   },
});

To check that your data is coming in, you need to first have activity on your application. Then, follow these steps to check that your data is in:

Log in to Splunk Observability Cloud.
Select Digital Experience and the Overview page for Digital experience analytics.
Check that your application is listed in the Available applications.