How This Briefing Works
This report opens with key findings, then maps the gaps between what Sailthru 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”
Sailthru deploys JavaScript from sail-horizon.com and drops multiple tracking cookies that require runtime analysis to determine pre-consent firing behavior, actual data transmission scope, and third-party data sharing patterns.
data_flow
“Marigold data sharing boundaries unverified”
Sailthru operates under Marigold (formerly CM Group, formerly Zeta Global acquisition target). The data boundaries between Sailthru, Campaign Monitor, Emma, Cheetah Digital, and other Marigold properties have not been independently verified.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Sailthru
- →- Audit Sailthru JavaScript cookie deployment timing to verify whether sailthru_content and sailthru_hid cookies fire before or after consent collection on your properties - Review Marigold's data processing agreement for cross-brand data sharing provisions between Sailthru, Campaign Monitor, Cheetah Digital, and other Marigold entities - Implement the GDPR Do Not Track option Sailthru provides to ensure anonymous tracking respects user opt-out preferences before identification - Document the full scope of anonymous behavioral data that gets retroactively stitched to identified profiles and assess GDPR data minimization compliance - Establish independent engagement measurement alongside Sailthru's reported metrics to validate personalization effectiveness claims
Negotiation Leverage
- →Sailthru's position within the Marigold conglomerate creates negotiation leverage around data governance boundaries. Marigold has assembled multiple marketing platforms through acquisition (CM Group acquired Sailthru, then rebranded to Marigold after further consolidation). Negotiators should demand: (1) explicit contractual prohibitions on cross-brand data sharing within the Marigold portfolio, (2) data isolation guarantees that survive future corporate restructuring or acquisition, (3) transparency into what anonymous behavioral data is collected before user identification and how long it persists, and (4) audit rights covering both Sailthru's direct data handling and any Marigold parent-level data processing. The anonymous-to-known stitching capability is the key risk to pin down contractually — demand explicit consent requirements before retroactive profile merging occurs.
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
4 detection signatures across scripts, domains, cookies, and network endpoints