How This Briefing Works
This report opens with key findings, then maps the gaps between what Everflow 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”
No runtime scan data available yet
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Everflow
- →Audit which Everflow tracking methods are deployed on your web properties (JS SDK, pixels, server-to-server postbacks) and ensure each is disclosed in your privacy policy. 2. Migrate from deprecated HTML pixel tracking to server-to-server postbacks where possible to reduce client-side tracking exposure. 3. Review view-through attribution settings and evaluate whether impression tracking aligns with your privacy commitments. 4. Ensure your consent management platform captures consent before Everflow JavaScript SDK fires, particularly for EU/UK visitors. 5. Audit data retention settings in your Everflow configuration — the platform allows customer-controlled retention periods, so verify these align with your data governance policies.
Negotiation Leverage
- →Everflow offers transparent, published pricing with a platform fee model rather than revenue-share. In procurement negotiations, focus on data governance provisions: who owns the tracking data generated on your properties, what are the default data retention periods, and how does Everflow use aggregated platform data across its customer base. Key leverage points include competitive alternatives (Impact, PartnerStack, Tune) and the platform's emphasis on privacy-forward tracking. Procurement teams should negotiate contractual guarantees that conversion data shared through Everflow is used solely for attribution purposes and that Everflow does not aggregate or resell customer transaction data. The server-to-server postback capability is a genuine privacy advantage over competitors still reliant on client-side tracking.
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