Overview
Splunk is an enterprise data analytics and observability platform used for log analysis, security information and event management (SIEM), and infrastructure monitoring. Unlike most vendors in consent management contexts, Splunk operates almost entirely on the server side — ingesting machine data, application logs, and infrastructure metrics from backend systems. It does not typically deploy client-side scripts on public-facing websites.
What This Script Does
Splunk does not load scripts or set cookies on public-facing web pages in its standard deployment. The platform operates as backend infrastructure, receiving data via agents, forwarders, and API integrations installed on servers, containers, and cloud infrastructure. Splunk's Real User Monitoring (RUM) component, part of Splunk Observability Cloud (formerly SignalFx), is the one exception — when deployed, it injects a JavaScript agent that collects browser performance data including page load times, resource timing, JavaScript errors, and user session traces. The RUM agent may set cookies such as _splunk_rum_sid for session identification, typically expiring within 4 hours. It collects performance telemetry including navigation timing, resource waterfall data, long task detection, and web vitals metrics.
Consent & Compliance
Splunk is classified under the analytics category. In its standard server-side deployment, no consent considerations apply to the website visitor's browser. However, if Splunk RUM (Real User Monitoring) is deployed on a public-facing website, the JavaScript agent collects browser performance and session data that constitutes analytics processing. Under GDPR, performance monitoring that collects session-level data requires either consent or a legitimate interest assessment. The ePrivacy Directive requires consent for non-essential cookies — RUM session cookies are not strictly necessary for delivering the web page. Under CCPA/CPRA, the session and performance data collected by the RUM agent constitutes personal information that must be disclosed.
Should You Block This Without Consent?
Conditional. If Splunk is used purely for server-side log analysis and infrastructure monitoring, no client-side consent management is needed. If Splunk RUM is deployed on public-facing pages, the JavaScript agent and its session cookies should be treated as analytics scripts requiring consent. Evaluate your specific Splunk deployment to determine whether any client-side components are active.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
splunk.comAnalyticsFrequently Asked Questions
Does Splunk require consent for website deployments?
It depends. Standard Splunk server-side log analysis has no browser footprint and requires no consent. However, if Splunk Real User Monitoring is deployed on public pages, its JavaScript agent collects session and performance data, making it an analytics script that requires consent under GDPR and the ePrivacy Directive.
What does the Splunk RUM agent collect when active on a website?
Splunk's Real User Monitoring agent collects browser performance data including page load times, resource timing, JavaScript errors, and user session traces. It sets a _splunk_rum_sid cookie for session identification, typically expiring within 4 hours. Navigation timing, resource waterfall data, and web vitals metrics are also collected.
How does ConsentStack handle Splunk on a site?
ConsentStack classifies Splunk as analytics and evaluates whether any client-side RUM components are active. If Splunk RUM is detected, ConsentStack blocks the JavaScript agent until analytics consent is granted. Server-side Splunk deployments with no browser scripts require no consent action and are not blocked by ConsentStack.
Related Vendors
Manage consent for Splunk
ConsentStack automatically detects and manages Splunk trackers so your site stays compliant with global privacy regulations.