Overview
Adobe Experience Manager (AEM) is an enterprise content management system and digital experience platform. When detected on a website, it means the site is built on and served through Adobe's CMS infrastructure. AEM is not a third-party tag or tracker — it is the website itself, handling content authoring, delivery, personalization, and asset management as part of the site's core platform.
What This Script Does
AEM operates as the website's content management and delivery layer. Its scripts handle:
- Content rendering — AEM's client libraries (clientlibs) bundle CSS and JavaScript required to render page components. These load from the site's own domain (or an AEM-managed CDN) with paths typically containing
/etc.clientlibs/or/content/ - Asset optimization — Dynamic Media scripts handle responsive image delivery, video playback, and asset transformation through Adobe's Scene7 infrastructure or AEM's built-in asset servlet
- Component interactivity — Client-side JavaScript for interactive page components (carousels, accordions, forms, navigation) that are part of AEM's Core Components or custom component libraries
- Personalization engine — AEM's ContextHub framework collects session-level data (browser properties, geolocation, referrer, time of day) to drive content targeting rules configured by content authors
AEM sets cookies for platform operations:
cq-authoring-mode— indicates whether the page is being viewed in authoring or preview mode; session-scoped; only present for content authorswcmmode— content management mode indicator; used during authoring- Session cookies for authenticated author/editor access
- ContextHub cookies storing personalization segment data when ContextHub targeting is active
For published pages viewed by end users, AEM's cookie footprint is minimal. The platform does not set cross-site tracking cookies, advertising identifiers, or third-party analytics cookies. Any analytics or marketing tracking present on an AEM-built site comes from separately integrated vendors (Adobe Analytics, Google Analytics, etc.), not from AEM itself.
Network requests go to the site's own origin servers or AEM's CDN infrastructure (which may include Adobe's Fastly-based CDN or a customer-configured CDN). Dynamic Media requests may go to Adobe's Scene7 delivery network for optimized image and video delivery.
Consent & Compliance
AEM is classified as essential. It is the content management system that builds and serves the website. Without AEM's scripts, the website's pages would not render — there would be no content, no navigation, no interactive components.
Under the GDPR, AEM's core scripts are part of the website's own infrastructure. Processing is governed by the website operator's relationship with Adobe under their enterprise data processing agreement. The CMS scripts themselves process minimal personal data; any personalization via ContextHub should be assessed separately, but even ContextHub's default data points (browser properties, referrer) are session-scoped and used for content presentation, not advertising.
Under the ePrivacy Directive, AEM's cookies are strictly necessary for the website to function. The clientlibs, component scripts, and session management cookies all fall under the Article 5(3) exemption for services explicitly requested by the user (loading and navigating the website). No consent is required for the CMS platform itself.
Under CCPA/CPRA, AEM does not sell or share personal information. Adobe acts as a service provider under the website operator's enterprise agreement. The CMS infrastructure processes data solely for content delivery on behalf of the website owner.
Should You Block This Without Consent?
No. Adobe Experience Manager is the website's content management system. Blocking its scripts would be equivalent to blocking the website from loading. AEM sets no advertising cookies, performs no cross-site tracking, and collects no behavioral data for marketing purposes. It is core infrastructure that must load for the website to function at all.
Consent Categories
Also Known As
Industries
Frequently Asked Questions
Do I need consent to use Adobe Experience Manager?
No. AEM is the website itself — its scripts render page content, navigation, and components. Under ePrivacy, CMS infrastructure cookies are strictly necessary and exempt from consent requirements.
What cookies does Adobe Experience Manager set?
AEM sets cq-authoring-mode and wcmmode cookies scoped to content authors. End-user page visits have a minimal footprint. ContextHub may store session-level personalization segments when targeting is active.
How does ConsentStack handle Adobe Experience Manager?
ConsentStack classifies AEM as essential and does not block its scripts. It detects AEM via /etc.clientlibs/ path patterns and Scene7 domains, allowing all AEM scripts to load without requiring visitor consent.
Other Adobe Products
Related Vendors
Manage consent for Adobe Experience Manager
ConsentStack automatically detects and manages Adobe Experience Manager trackers so your site stays compliant with global privacy regulations.