How This Briefing Works
This dossier opens with key findings, then maps the gap between what CustomerIO 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.
At a Glance
across 4 sites
vendor fires before consent
1 HIGH
Briefing
Customer.io is a customer data platform and marketing automation tool detected across 10 deployments on 4 sites. BLACKOUT identified 8 behavioral threat codes including defeat device infrastructure (C01), behavioral biometrics (C06), session recording (C07), cross-domain sync (C08), consent bypass (C09), fingerprinting (C10), persistence mechanisms (C13), and identity resolution (C14). The combination of C08 + C13 + C14 constitutes a complete identity stitching stack: Customer.io resolves visitor identities, persists them across sessions with long-lived identifiers, and syncs them across domains. With a 60% pre-consent firing rate and 3 distinct tracking domains, Customer.io's data collection footprint significantly exceeds what marketing automation requires.
What This Means For You
If Customer.io is deployed on your site, your customers are being subjected to a full identity stitching operation — their identities are resolved, persisted with long-lived identifiers that survive consent withdrawal, and synchronized across domains. With a 60% pre-consent firing rate, the majority of your visitors encounter this identity infrastructure before they can consent. The persistence mechanisms (C13) mean that even customers who withdraw consent or delete cookies remain identified in Customer.io's system. Your first-party customer relationship data — the most valuable data your business holds — flows through Customer.io's 3-domain infrastructure with cross-domain sync enabled. You are effectively ceding control of your customer identity layer to a third party.
Risk Channel Breakdown
Signal corruption score of 40 reflects Customer.io's identity stitching stack distorting the boundary between marketing automation and persistent surveillance infrastructure. When your CDP resolves identities and syncs them cross-domain, your customer data is no longer contained within your marketing stack — it becomes part of a distributed identity graph.
Maximum CAC subsidization score (100) indicates Customer.io's cross-domain sync and identity resolution across their deployment network creates intelligence leakage channels. Customer behavioral data and resolved identities flow through Customer.io's infrastructure, creating visibility into your customer base and engagement patterns.
Expands attack surface
Maximum legal tail risk (100) driven by 60% pre-consent firing rate combined with persistence mechanisms (C13) that maintain identification across sessions. Long-lived identifiers that survive consent withdrawal create ongoing GDPR Art. 7(3) violations — users who withdraw consent remain tracked through persistent mechanisms.
Threat Indicators
Runtime-observed (BTI-C)
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Full session replay
Identity stitching
Ignoring CMP signals
Device identification
Long-lived identifiers
PII deanonymization
Per-code narrative explanations of what each detected behavior means for your organization
Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →
Claims vs. Reality
BLACKOUT analyzed CustomerIO's public claims against observed runtime behavior and identified 1 contradiction.
Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →
What To Do
4 for current users · 4 for evaluators
contractual leverage points
Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →
Supply Chain & Pairings
drift, googletagmanager, googleanalytics4…
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →