How This Briefing Works
This report opens with key findings, then maps the gaps 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 data and evidence underneath.
Key Findings
Pre-Consent Activity
Optimizely was observed loading and executing before user consent was obtained on 75% of sites where it was detected.
Claims vs. Observed Behavior
disclosure
“Pending claims extraction”
Moderate Broker (65) and Counselor (70) scores indicate data sharing and consent violations. Privacy policy likely lacks disclosure of cross-domain tracking and pre-consent cohort assignment.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Optimizely
- →Implement consent gate before Optimizely experimentation activates
- →Audit cross-domain tracking scope and visitor identifier persistence
- →Review Data Processing Agreement for experiment data retention and third-party sharing
- →Confirm privacy policy discloses visitor cohort assignment and cross-domain tracking
If You're Evaluating Optimizely
- →Defer Optimizely scripts until post-consent confirmation
- →Assess server-side experimentation alternatives to reduce client-side tracking exposure
- →Require vendor documentation on consent-aware experiment assignment capabilities
- →Consider whether cross-domain tracking is necessary or can be eliminated
Negotiation Leverage
- →Optimizely contract should specify experiment data retention limits - negotiate deletion after statistical significance achieved
- →Cross-domain tracking requires additional consent under ePrivacy - confirm Optimizely supports domain-scoped experiments
- →Request evidence of consent-aware experimentation capabilities that preserve statistical validity
- →Demand technical controls for visitor identifier lifespan limits and cross-domain sync opt-out
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Full session replay
Identity stitching
Ignoring CMP signals
Long-lived identifiers
IOC Manifest
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
197 detection signatures across scripts, domains, cookies, and network endpoints