How This Briefing Works
This report opens with key findings, then maps the gaps between what Realytics 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
Realytics was observed loading and executing before user consent was obtained on 7% of sites where it was detected.
Claims vs. Observed Behavior
tv_attribution
“Pending claims extraction”
Runtime shows full tracking suite active before consent for TV attribution
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Realytics
- →Audit TV attribution methodology for probabilistic vs deterministic matching
- →Map cross-device data flow including TV ecosystem participants
- →Document consent bypass scope across all tracking components
- →Calculate measurement impact from consent-first activation
If You're Evaluating Realytics
- →Require demonstration of consent-respecting TV attribution
- →Demand written confirmation of data retention post-consent-revocation
- →Negotiate exclusivity preventing TV match data sharing with competitors
- →Evaluate server-side attribution alternatives
Negotiation Leverage
- →Five active BTI codes: Demand DPA rewrite addressing each threat category
- →C09 enabler: All tracking requires consent bypass for TV matching - negotiate unlimited liability or consent-first activation
- →C08 exposure: Require disclosure of ALL cross-device sync partners and TV ecosystem participants
- →Oracle corruption: Request technical validation of attribution model accuracy and synthetic path filtering
- →Alternative: First-party TV attribution via promo codes + vanity URLs eliminates vendor dependency
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.
Keystroke/mouse tracking
Full session replay
Identity stitching
Ignoring CMP signals
Container/loader (neutral)
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
158 detection signatures across scripts, domains, cookies, and network endpoints