Does Acquia require consent before loading?

Yes. Acquia Lift sets persistent visitor identification cookies that expire after one to two years and builds cross-session behavioral profiles used for content personalization. This constitutes non-essential processing under ePrivacy, requiring consent before the script activates.

What does Acquia track on Drupal-powered sites?

Acquia's Lift agent collects page views, content interactions, click patterns, form submissions, UTM parameters, and device metadata. This data feeds Acquia's customer data platform to build visitor profiles used for real-time personalization and audience segmentation across sessions.

How does ConsentStack manage Acquia?

ConsentStack blocks Acquia's personalization and analytics scripts until the visitor consents to both analytics and functional categories. If the site separates essential Drupal content delivery from Acquia Lift tracking, ConsentStack can be configured to gate only the tracking components.

What tracker domains does Acquia use?

ConsentStack has catalogued tracker domains for Acquia including acquia.com. These are the network destinations Acquia's scripts contact, which a consent platform blocks until a visitor agrees.

Acquia - Drupal Personalization Privacy Controls

Back to Vendor Library

Overview

Acquia provides a digital experience platform built on Drupal, offering content management, personalization, and customer data orchestration capabilities. Its web-facing scripts include the Acquia Lift personalization engine and Acquia Analytics modules that embed directly into Drupal-powered websites. These components work together to deliver targeted content variations and collect visitor engagement data for optimization.

What This Script Does

Acquia's client-side components typically load from domains such as lift.acquia.com or custom subdomains configured per deployment. The Acquia Lift agent script collects visitor behavior data — page views, content interactions, click patterns, and form submissions — to build visitor profiles used for real-time content personalization.

The scripts set cookies for visitor identification and audience segmentation. A persistent visitor identity cookie (commonly expiring after 1–2 years) tracks the visitor across sessions to build a behavioral profile. Additional cookies store segment membership, A/B test variant assignments, and personalization rule matches. Session cookies maintain state for active personalization decisions.

Data collected includes page URLs, content element interactions, referrer information, UTM parameters, device and browser metadata, and any custom events configured by the site operator. This data feeds into Acquia's customer data platform (CDP) for profile unification and segment building.

Consent & Compliance

Acquia scripts span analytics and functional categories. The analytics classification covers the visitor behavior tracking, profile building, and A/B testing functionality. The functional classification applies when personalization directly affects the content experience — such as displaying region-specific information or language preferences.

Under GDPR and ePrivacy, the persistent visitor identification cookies and cross-session behavioral profiling clearly require consent before activation. The profiling activities may also trigger GDPR Article 22 considerations regarding automated decision-making. Under CCPA/CPRA, the collection and processing of behavioral data for content personalization may constitute "profiling" as defined by CPRA, and the sharing of visitor data with Acquia's cloud infrastructure requires disclosure in privacy policies.

Should You Block This Without Consent?

Yes. Acquia's personalization and analytics scripts set persistent tracking cookies and build cross-session visitor profiles, which constitute non-essential processing under ePrivacy rules. Block these scripts until the visitor has consented to analytics cookies. If the site relies on Acquia for essential content delivery (not personalization), those components should be separated from the tracking scripts.

Is Acquia GDPR compliant?

Acquia typically loads analytics and functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Acquia can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Acquia, not on Acquia itself.

Visit website