QA mode · Tier:PUBLIC(override via ?tier=paid | premium)
← All Vendors
tag_manager

Optimizely

Experimentation platform with session recording, cross-domain tracking, and pre-consent visitor assignment to test cohorts.

197 IOCs observed26 detections81% pre-consent18 sites
70
Vendor Risk Score
Tier: GRAY
Observation Coverage

BLACKOUT observes runtime behavior in the browser. This dossier reflects browser-side execution, which is one of five vendor data-egress classes. Server-to-server transfers, backend integrations, and offline data flows are outside this observation boundary.

BLACKOUT observes runtime behavior and cites the regulations that address that behavior pattern. Legal determinations are the customer's counsel's call.

How This Briefing Works

This dossier opens with key findings, then maps the gap between what Optimizely discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.

Key Findings

At a Glance

Detections
26

across 18 sites

Pre-Consent Rate
81%

vendor fires before consent

Disclosure Gaps
1

Summary

Briefing

Optimizely activates A/B testing and experimentation infrastructure before consent collection. Session recording captures interaction data for test result analysis. Cross-domain synchronization enables persistent visitor tracking across properties. Pre-consent cohort assignment processes visitor data without lawful basis.

Customer Impact

What This Means For You

Product and marketing teams lose A/B testing capabilities if Optimizely is removed. Experimentation velocity declines without infrastructure for controlled testing. Personalization features may degrade. However, retention creates exposure: regulatory complaints for pre-consent cohort assignment, cross-domain tracking creating expanded consent liability, potential measurement bias if consent rates differ across test variants.

Collapse Engine

Risk Channel Breakdown

Oracle
Truth Collapse
15

Distorts attribution data

Broker
Control Collapse
90

Limited Oracle impact (15) suggests some measurement distortion from pre-consent test assignment. Moderate Broker score (65) indicates test result data may flow to analytics platforms.

Reaper
Safety Collapse
0

Expands attack surface

Counselor
Legitimacy Collapse
85

Pre-consent visitor tracking and cross-domain synchronization violate GDPR consent requirements and ePrivacy Directive cookie rules.

BTI Codes

Threat Indicators

Runtime-observed (BTI-C)

BTI-C07
Session Recording

Full session replay

BTI-C08
Cross-Domain Sync

Identity stitching

BTI-C09
Consent Bypass

Ignoring CMP signals

BTI-C13
Persistence Mechanisms

Long-lived identifiers

3
BTI Consequences Identified

Per-code narrative explanations of what each detected behavior means for your organization

Available in VIDB Subscription

Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →

Disclosure Gaps

Claims vs. Reality

1
Gaps Observed

BLACKOUT analyzed Optimizely's public claims against observed runtime behavior and identified 1 contradiction.

Available in VIDB Subscription

Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →

Recommended Actions

What To Do

Recommended Actions
8

4 for current users · 4 for evaluators

Negotiation Leverage
4

contractual leverage points

Available in VIDB Subscription

Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →

Ecosystem

Supply Chain & Pairings

Subprocessor Disclosure Gap
1undisclosed

Claims 0, observed 1

Commonly Paired With
9

googletagmanager, googleanalytics4, onetrust

Available in VIDB Subscription

Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →

Profile: optimizelyFirst Seen: 2026-01-06Last Updated: 2026-02-28