How This Briefing Works
This report opens with key findings, then maps the gaps between what RedTrack 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
“Cookieless tracking solution”
Awaiting scanner verification of Universal Tracking Script behavior, first-party cookie patterns, and server-side data flows at runtime
pending
“GDPR-compliant IP obfuscation”
Scope of data collection beyond IP addresses needs direct observation to fully characterize
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for RedTrack
- →- Audit the Universal Tracking Script to understand exactly what data is collected client-side and what is processed server-side, including all cookie patterns and identifier mechanisms. - Map conversion data flows to each connected ad network to understand what business intelligence (revenue, conversion rates, product data) is being shared externally via CAPI and S2S postbacks. - Evaluate whether server-side tracking operates on visitors who have declined consent or deployed ad blockers, and assess compliance implications under applicable privacy regulations. - Review data retention policies for the 30+ data points captured per click, particularly for GDPR-covered visitors where IP obfuscation is applied. - Establish independent conversion measurement to validate RedTrack's attribution against directly observed outcomes.
Negotiation Leverage
- →Leverage: RedTrack's ad blocker bypass capability is a compliance liability for customers — negotiate for indemnification covering regulatory actions arising from server-side tracking of users who have deployed privacy tools. The platform's role as a data intermediary between revenue platforms and ad networks means your business performance data flows to third parties; demand granular control over what data is shared with which platforms.
- →Key questions: What specific data points from the 30+ captured per click are sent to ad platforms via CAPI? Can customers restrict revenue and transaction data from flowing to ad networks? Does server-side tracking continue for visitors who have declined consent? What data does RedTrack retain independently of connected platforms, and for how long? How is IP obfuscation implemented for GDPR countries?
- →Contractual protections: Require the ability to disable ad blocker bypass functionality while retaining standard attribution. Include data deletion upon termination covering all 30+ data points and any derived analytics. Negotiate for customer approval before RedTrack adds new ad platform integrations that would receive your data. Ensure the DPA explicitly covers server-side tracking as a distinct processing activity requiring its own lawful basis.
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
124 detection signatures across scripts, domains, cookies, and network endpoints