How This Briefing Works
This report opens with key findings, then maps the gaps between what Acoustic 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”
Analysis based on public documentation, Acoustic 2025 Marketing Benchmark Report, and integration partner disclosures
pending
“Runtime email pixel behavior unverified”
Email tracking pixel data collection scope and third-party sharing patterns require direct observation
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Acoustic
- →- Audit all Acoustic email templates for tracking pixel deployment and document the data collected per pixel fire (IP, device, geolocation, timing) - Review Acoustic web beacon implementation to catalog all behavioral events being captured and where that data flows - Verify consent mechanisms cover Acoustic's cross-channel behavioral profiling, not just email marketing consent - Map all Acoustic integration data flows to identify where behavioral data is shared with third-party systems - Request Acoustic's data processing addendum and verify data retention, deletion, and subject access request procedures
Negotiation Leverage
- →Leverage: Acoustic's 2019 spinoff from IBM and PE ownership by Centerbridge means the company is under pressure to demonstrate growth and platform stickiness. Their investment in AI-driven personalization creates dependency on behavioral data volume, giving customers leverage to negotiate data minimization terms that limit what Acoustic retains. Key questions: (1) What specific data elements does each email tracking pixel collect, and can pixel tracking be disabled per campaign? (2) How long does Acoustic retain behavioral profiles after a contact is deleted from Campaign? (3) Which integration partners receive behavioral data, and under what contractual terms? (4) Can cross-channel profile unification be disabled to limit data aggregation? Protections to negotiate: Contractual data retention limits tied to campaign lifecycle rather than indefinite retention, explicit restrictions on behavioral data use for Acoustic's own product improvement or benchmarking, and right to audit data flows to integration partners.
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.
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Impact: Acoustic Connect unifies behavioral signals from email, web, mobile, and SMS into a single profile, enabling automated cross-channel activation that amplifies the tracking footprint beyond any single channel's disclosed purpose.
Full session replay
Ignoring CMP signals
Impact: Email tracking pixels fire automatically on open with no per-recipient consent mechanism. Web beacons deploy behavioral tracking before explicit consent for profiling is obtained.
Device identification
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
323 detection signatures across scripts, domains, cookies, and network endpoints