Overview
Adobe Analytics is Adobe's enterprise web analytics platform. Pageview, event, and conversion data is transmitted to a tenant-specific subdomain of sc.omtrdc.net (or the legacy 2o7.net). Commonly deployed via Adobe Launch or Tealium iQ alongside Adobe Audience Manager (DMP, demdex.net) and Adobe Target (personalisation, tt.omtrdc.net), forming the integrated Adobe Experience Cloud stack.
Detection capabilities
- Signature count
- 2
- Detection methods
- network
- Property types
- hostname
Performance impact
Performance Impact
- Script size
- 60 KB
- Requests per page
- 2
Common mistakes
- 1Firing Adobe Analytics s.t() calls before consent is obtained, setting s_vi and s_cc cookies and transmitting pageview data to the tenant-specific omtrdc.net subdomain
- 2Not recognising that the tenant-specific subdomain (e.g. upc.d2.sc.omtrdc.net for Virgin Media Ireland) is Adobe Analytics because it does not match a generic adobeanalytics.com pattern - signature must be anchored to the *.sc.omtrdc.net suffix or the tag will be missed entirely
- 3Deploying Adobe Analytics alongside Adobe Audience Manager without understanding that visitor IDs are shared between the two products via the Adobe Experience Cloud ID service, which widens the processing footprint beyond what a standalone analytics tool would require
- 4Treating Adobe Analytics as "functional" or "strictly necessary" in the CMP - it is an analytics-category tracker that requires consent under ePrivacy and GDPR
Compliance considerations
Adobe Analytics collects pageview, click, event, and custom-dimension data and transmits it to a tenant-specific subdomain of sc.omtrdc.net. The s_vi cookie is a cross-session visitor identifier that persists for up to two years and enables longitudinal behavioural profiling. Under GDPR and the ePrivacy Directive, analytics cookies of this nature are not strictly necessary and require consent - this is the position taken by the French CNIL, Spanish AEPD, and (by extension) the Irish DPC in analytics enforcement guidance.
Adobe offers EU-hosted data centres but the default contract may route to US servers unless explicitly configured. Organisations should verify their Adobe contract specifies EU data residency, categorise Adobe Analytics under the analytics consent bucket, and include it in DPIA where deployed alongside Audience Manager or Target.
Detection gap: Adobe Analytics' tenant-specific subdomains (e.g. upc.d2.sc.omtrdc.net) were not covered by a wildcard signature in the registry - only adobe-audience-manager matched the demdex.net pattern. The gap was identified during a priority-scan cross-check. Added in sprint company_tools-ex7lt / feature company_tools-ex7lt.4.
Related services
Scan your site for Adobe
Run a free ConsentMark scan to see how Adobe is loading on your site, whether it respects consent, and where governance gaps exist across your wider tag estate.
Start a free scan