How This Briefing Works
This report opens with key findings, then maps the gaps between what Mediamath 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
Mediamath was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
disclosure
“Pending claims extraction”
Counselor score (40) suggests consent mechanisms are bypassed. Privacy policy likely lacks specific disclosure of bid stream participants and cross-site tracking scope.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Mediamath
- →Gate all MediaMath pixels behind explicit consent for advertising cookies
- →Audit Data Processing Agreement for bid stream data sharing disclosures
- →Confirm MediaMath complies with IAB Transparency & Consent Framework
- →Review privacy policy for adequate disclosure of programmatic data flows
If You're Evaluating Mediamath
- →Require consent before any MediaMath script loads
- →Demand contractual limits on bid stream participant data access
- →Assess first-party data clean room alternatives to third-party cookie dependence
- →Consider server-side ad decisioning to reduce client-side tracking exposure
Negotiation Leverage
- →MediaMath contract permits sharing visitor data with "platform partners" - demand exhaustive partner list and sharing purpose limitations
- →Bid stream data persists in partner systems beyond MediaMath retention - negotiate contractual liability for downstream violations
- →Confirm MediaMath honor browser-based tracking opt-outs (GPC, DNT) and consent withdrawal requests
- →Request evidence of IAB TCF compliance and consent string validation before pixel activation
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.
Ignoring CMP signals
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
14 detection signatures across scripts, domains, cookies, and network endpoints