How This Briefing Works
This report opens with key findings, then maps the gaps between what Dynamic Yield 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”
Runtime behavior not yet observed by BLACKOUT scanner
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Dynamic Yield
- →Audit the scope of Dynamic Yield event tracking to understand exactly what behavioral data is collected and retained, including custom events configured by your team.
- →Review whether your privacy policy adequately discloses the Mastercard data relationship and the use of aggregated transaction data for personalization decisions.
- →Implement Content Security Policy headers that restrict Dynamic Yield's script capabilities to only what is required for your use cases.
- →Assess whether A/B test fragmentation is distorting your attribution models by comparing analytics during active test periods versus holdout periods.
- →Map all data flows between Dynamic Yield and other platforms (CDPs, DMPs, tag managers) to understand where behavioral segments propagate.
Negotiation Leverage
- →Leverage: Dynamic Yield's value proposition depends on access to your site traffic and behavioral data. Request contractual clarity on data retention periods, model training rights, and whether any behavioral data feeds Mastercard's broader data products. Key questions: (1) Does on-site behavioral data collected by Dynamic Yield inform any Mastercard data assets or audience products beyond your account? (2) What happens to collected behavioral data if the contract terminates? (3) What are the data retention defaults and can they be shortened? (4) Are recommendation model weights trained on your data shared across other Dynamic Yield customers? Protections to negotiate: explicit data deletion SLAs upon contract termination, opt-out from any cross-customer model training, contractual prohibition on using your site behavioral data for Mastercard audience products, and audit rights over the data flows between Dynamic Yield and Mastercard systems.
IOC Manifest
Indicators of compromise across 2 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
2 detection signatures across scripts, domains, cookies, and network endpoints