How This Briefing Works
This report opens with key findings, then maps the gaps between what Campaign Monitor 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
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Awaiting scanner verification”
Signature-only assessment pending runtime observation
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Campaign Monitor
- →Review your Campaign Monitor data processing agreement to understand how recipient engagement data is used within the broader Marigold ecosystem. Assess whether your email privacy policy adequately discloses the use of tracking pixels and link redirect tracking. For GDPR-regulated audiences, evaluate whether your lawful basis for email tracking is documented and defensible. Consider enabling Campaign Monitor's plain-text alternatives for sensitive communications where tracking is inappropriate. Audit which third-party integrations are connected to your Campaign Monitor account and what data flows to each. Monitor the impact of Apple MPP and Gmail proxying on your open rate metrics to understand how much behavioral data is still being reliably collected.
Negotiation Leverage
- →Campaign Monitor's position within the Marigold portfolio is the key leverage point. When negotiating: (1) Demand clarity on data isolation — confirm in writing whether recipient engagement data from Campaign Monitor is accessible to or shared with other Marigold products (Sailthru, Cheetah Digital, Selligent). (2) Request data processing agreement amendments that explicitly scope data usage to your Campaign Monitor instance only. (3) Negotiate data retention limits on recipient behavioral data — open/click tracking data should have defined expiration. (4) Request transparency on sub-processors, particularly any Marigold-internal data sharing that occurs at the infrastructure level. (5) For HIPAA-regulated communications, ensure the BAA covers tracking pixel and link redirect data, not just email content delivery.
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
Impact: Email tracking pixels fire automatically upon message rendering with no recipient-side consent mechanism. While Apple MPP and proxy-based protections have emerged, the default tracking architecture operates without explicit recipient consent for behavioral observation.
PII deanonymization
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
76 detection signatures across scripts, domains, cookies, and network endpoints