Does CloudBees Feature Management require cookie consent?

Conditional. CloudBees Feature Management is classified as functional — evaluating feature flags is a core application delivery mechanism, not tracking. Under the ePrivacy Directive, storage used for consistent feature delivery falls within the strictly necessary exemption.

What does CloudBees Feature Management store in the browser?

CloudBees Feature Management uses localStorage to store device identifiers and cached feature flag configurations for consistent flag assignment across page loads. It also captures A/B test variant assignments per session. No advertising or marketing cookies are set.

How does ConsentStack handle CloudBees Feature Management?

ConsentStack categorizes CloudBees Feature Management as functional. The script is not blocked by default because feature flag evaluation is essential to application delivery. If functional consent is explicitly denied, ConsentStack can gate the script, potentially affecting controlled feature rollouts.

What tracker domains does CloudBees Feature Management use?

ConsentStack has catalogued tracker domains for CloudBees Feature Management including rollout.io. These are the network destinations CloudBees Feature Management's scripts contact, which a consent platform blocks until a visitor agrees.

CloudBees Feature Management - Flag Consent Controls

Back to Vendor Library

Overview

CloudBees Feature Management (formerly Rollout.io) provides enterprise-grade feature flagging with fine-grained targeting rules, gradual rollouts, and experiment orchestration. The platform integrates with CI/CD pipelines to coordinate feature releases with deployment workflows. Its client-side SDK evaluates targeting rules locally after downloading flag configurations, minimizing latency in feature state resolution.

What This Script Does

The CloudBees Feature Management JavaScript SDK loads from cdn.cloudbees.com or a configured endpoint. On initialization, the SDK fetches the current flag configuration for the application environment, including targeting rules, percentage allocations, and experiment assignments.

The SDK generates or reads a device identifier stored in localStorage to ensure consistent flag evaluation across page loads. This identifier enables sticky bucketing for percentage-based rollouts—ensuring the same user sees the same feature variant consistently. No traditional cookies are set by default.

When experiment tracking is enabled, the SDK sends impression events to CloudBees' servers recording which flag variants were served to which device identifiers. These events include timestamps, flag keys, variant values, and the device identifier. Custom properties attached to the user context (e.g., plan tier, region) may also be transmitted for targeting rule evaluation.

Network requests go to CloudBees' API endpoints for configuration fetches and event reporting. The SDK supports offline mode with cached configurations in localStorage.

Consent & Compliance

CloudBees Feature Management is classified as functional under GDPR and ePrivacy frameworks. Feature flag evaluation is a core application delivery mechanism, not a tracking or marketing function. The localStorage usage for device identifiers and cached configurations serves the technical purpose of consistent feature delivery.

Under the ePrivacy Directive, the storage access qualifies for the strictly-necessary exemption when used solely for feature flag evaluation. If experiment impression tracking is enabled for analytics purposes, this secondary use should be assessed independently—though it typically remains within the functional scope of A/B testing for product improvement.

Under GDPR, the device identifiers constitute pseudonymous data. Processing is supportable under legitimate interest (Article 6(1)(f)) for the purpose of delivering consistent application features.

Should You Block This Without Consent?

No.

CloudBees Feature Management controls which application features are visible to users. Blocking the SDK would prevent feature flags from resolving, potentially exposing unfinished features or hiding completed ones. The device identifier storage serves functional consistency, not behavioral tracking, and qualifies for the ePrivacy strictly-necessary exemption.

Is CloudBees Feature Management GDPR compliant?

CloudBees Feature Management typically loads 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 CloudBees Feature Management 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 CloudBees Feature Management, not on CloudBees Feature Management itself.

Visit website