How This Briefing Works
This report opens with key findings, then maps the gaps between what Connexity 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
Connexity was observed loading and executing before user consent was obtained on 2% of sites where it was detected.
Consent Disclosure
24 distinct third-party vendors detected on connexity.com
Undisclosed Party
Not in privacy policy
Undisclosed Sharing
Hidden data recipients
CMP Disclosure Mismatch
CMP vendor list vs runtime
Claims vs. Observed Behavior
Consent Disclosure
“CMP states 9 third parties for user consent choice”
24 distinct third-party vendors detected on connexity.com
BLACKOUT scan 2026-01-24, ConsentManager banner inspection
Subprocessor Disclosure
“Privacy policy names Google, DoubleClick, Criteo as third parties”
20+ additional vendors including LinkedIn, HGinsights, TrenDemon, Versium detected
Runtime detection of third-party scripts and tracking pixels
Pre-Consent Tracking
“ConsentManager CMP provides consent choice before tracking”
GoogleAnalytics4 and LinkedIn fire before consent granted (pre_consent=true)
BLACKOUT detection with pre_consent flag analysis
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Connexity
- →Audit your consent banner to ensure ALL 24 detected vendors are disclosed, not just the 9 shown in CMP
- →Update your privacy policy to name Connexity and its downstream data recipients explicitly
- →Verify pre-consent firing is blocked by testing your implementation against detection data
- →Request contractual restrictions on data sales specifically for your customer records
If You're Evaluating Connexity
- →Understand that Connexity explicitly sells personal data — assess whether this aligns with your privacy commitments
- →Request complete vendor list and compare against CMP coverage before signing
- →Evaluate whether Taboola subsidiary status creates data flow risks beyond Connexity itself
- →Require contractual opt-out from data sales for your customer data as a condition of engagement
Negotiation Leverage
- →Explicit data sales: Connexity admits to selling personal data including identifiers and purchase records — use this to negotiate data sales restrictions for your customer data specifically
- →CMP vendor undercount: 24 vendors detected vs. 9 in CMP — require all vendors to be consent-gated and disclosed as a contract condition
- →Taboola subsidiary risk: Retail data flows within a native advertising conglomerate — negotiate restrictions on data sharing within the Taboola corporate family
- →Purchase record sensitivity: Connexity processes transaction data revealing YOUR customers' buying patterns — negotiate enhanced data protection and restrictions on behavioral inference sales
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.
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Full session replay
Ignoring CMP signals
Device identification
IOC Manifest
Indicators of compromise across 3 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
168 detection signatures across scripts, domains, cookies, and network endpoints