Overview
Liferay is an enterprise digital experience platform that powers corporate portals, intranets, and customer-facing websites. Unlike third-party script vendors, Liferay is typically the application framework itself — sites built on Liferay run its JavaScript natively as part of the platform's page rendering and navigation system. Liferay also offers optional analytics and personalization modules that add tracking capabilities to portal pages.
What This Script Does
On Liferay-powered sites, the platform's JavaScript manages core page functionality: content rendering, navigation, form handling, and user session management. Authentication cookies are set for logged-in portal users, with session cookies maintaining login state and CSRF protection tokens securing form submissions.
Liferay Analytics Cloud, when enabled, loads an additional JavaScript agent from analytics.liferay.com or a self-hosted endpoint. This agent tracks page views, content interactions, form submissions, and asset downloads. It sets persistent cookies (typically expiring after 1 year) to identify unique visitors and build behavioral profiles for content recommendations and audience segmentation.
Data collected by the analytics module includes page URLs, time on page, click events, form field interactions, search queries within the portal, and document download events. User identifiers from the portal's authentication system may be linked to analytics profiles for known-user tracking.
Consent & Compliance
Liferay scripts span analytics and functional categories. The core platform scripts — session management, authentication, navigation — are functional and essential to the portal's operation. The Liferay Analytics Cloud module falls under analytics, as it collects behavioral data for reporting and personalization purposes.
Under GDPR and ePrivacy, the core session and authentication cookies are strictly necessary for delivering the portal service and do not require consent. The Analytics Cloud cookies and behavioral tracking, however, require consent before activation as they serve non-essential analytics purposes. Under CCPA/CPRA, the analytics data collection may require disclosure and opt-out mechanisms, particularly if visitor profiles are shared with Liferay's cloud infrastructure.
Should You Block This Without Consent?
Conditional. The core Liferay platform scripts that handle page rendering, navigation, and authentication are functional and should not be blocked. However, the Liferay Analytics Cloud module and any personalization tracking scripts should be blocked until the visitor has consented to analytics data collection. Ensure the analytics module is loaded separately from core platform scripts to enable selective blocking.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
liferay.comAnalyticsFrequently Asked Questions
Which Liferay components require consent?
Liferay's core portal scripts — session management, authentication, navigation — are functional and do not require consent. The Liferay Analytics Cloud module requires consent because it sets persistent cookies and collects behavioral data including page views, clicks, and form interactions.
What does Liferay Analytics Cloud collect?
Liferay Analytics Cloud tracks page views, time on page, click events, form field interactions, search queries, and asset downloads. It sets persistent cookies expiring after approximately one year to identify unique visitors and link known portal users to behavioral analytics profiles.
How does ConsentStack manage Liferay deployments?
ConsentStack allows Liferay's core platform scripts to load without consent while blocking the Analytics Cloud module until analytics consent is granted. This requires the analytics module to be loaded separately from core platform scripts so selective blocking is possible.
Related Vendors
Manage consent for Liferay
ConsentStack automatically detects and manages Liferay trackers so your site stays compliant with global privacy regulations.