How This Briefing Works
This report opens with key findings, then maps the gaps between what SALESmanago 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”
SALESmanago deploys Monitoring Code with smuuid/smclient cookies and Web Beacon technology that require runtime analysis to determine pre-consent firing behavior, actual data transmission scope, and behavioral data granularity in production deployments.
data_flow
“AI data usage boundaries unverified”
SALESmanago markets AI-driven personalization and automation but the boundaries of how customer behavioral data is used to train or improve AI models across the 3,000+ customer base 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 SALESmanago
- →- Audit SALESmanago Monitoring Code deployment to verify whether smuuid and smclient cookies fire before or after consent collection, and whether Web Beacon scripts respect consent preferences - Review the full scope of Deep Behavioral Profiling data collection against your privacy policy and consent language to ensure users are adequately informed about element-level interaction monitoring - Request SALESmanago's AI data usage policy to understand whether customer behavioral data contributes to cross-customer model training or platform-wide optimization - Implement server-side consent enforcement to prevent SALESmanago scripts from executing before valid consent is obtained, rather than relying solely on SALESmanago's client-side consent tools - Conduct a GDPR Article 35 Data Protection Impact Assessment given the granular behavioral monitoring scope of Web Beacons and Deep Behavioral Profiling
Negotiation Leverage
- →SALESmanago's positioning as a European GDPR-native platform is both its marketing strength and the primary negotiation leverage point. If SALESmanago claims GDPR compliance by design, hold them to it contractually. Negotiators should demand: (1) explicit documentation of the full behavioral data collection scope including Web Beacon and Deep Behavioral Profiling data types, (2) contractual guarantees that customer behavioral data is not used for cross-customer AI model training without explicit opt-in, (3) data processing agreements that specifically enumerate element-level tracking, mouse movement monitoring, and scroll behavior as processing activities requiring consent, and (4) audit rights covering the behavioral data pipeline from Monitoring Code capture through CDP storage to AI model consumption. The key pressure point: if SALESmanago's default behavioral monitoring scope exceeds what a typical "marketing cookies" consent covers, they have a systemic consent validity problem across their entire customer base.
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
99 detection signatures across scripts, domains, cookies, and network endpoints