How This Briefing Works
This report opens with key findings, then maps the gaps between what Act-On 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 Act-On official documentation, beacon installation guides, and integration partner listings
pending
“Cookie-to-identity retroactive linking unverified”
Act-On documents this capability but runtime data retention and scope require direct observation
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Act-On
- →- Audit Act-On Beacon deployment to confirm what behavioral events are captured and verify cookie consent mechanisms are in place before the beacon fires - Review email tracking pixel behavior and determine whether pixel tracking can be disabled for recipients in consent-sensitive jurisdictions - Map all bidirectional CRM sync fields to understand which behavioral data elements flow into Salesforce/Dynamics contact records - Inventory all active Act-On integrations with ad platforms and ABM vendors to identify behavioral data sharing pathways - Review Act-On's data retention policies and verify that deleting a contact also purges their pre-identification behavioral history
Negotiation Leverage
- →Leverage: Act-On competes in a crowded mid-market marketing automation space against HubSpot, Marketo, and Pardot. Customer retention is critical, giving existing customers leverage to negotiate data handling terms. Their reliance on CRM integration stickiness means they are motivated to accommodate contractual requirements to prevent migration. Key questions: (1) Can the Act-On Beacon be configured to require consent before placing tracking cookies? (2) When a contact is deleted, is their pre-identification anonymous behavioral history also purged? (3) Which ad platform and ABM integrations receive behavioral data, and can these data flows be disabled per-contact? (4) Does Act-On use aggregate behavioral data from customer accounts for its own product development or benchmarking? Protections to negotiate: Contractual commitment that beacon tracking respects consent signals (e.g., no tracking before cookie consent), data deletion guarantees that cover anonymous behavioral history, and explicit restrictions on sharing behavioral data with advertising and ABM partners without per-contact consent.
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
184 detection signatures across scripts, domains, cookies, and network endpoints