Situation
Cross-domain analytics needed to connect sessions without ignoring browser privacy or organisational trust boundaries.
A local implementation review was required to coordinate security and legal alignment.
System flow
Traceability of ownership and gate dependencies across systems.
Experience Analytics Security Review sequential logic
- Four web properties — Market storefronts (Partner-owned delivery)
- Cross-domain tracking requirement — Vendor analytics (Partner-owned delivery)
- Architecture options — Solution design (Partner-owned delivery)
- Cyber-security review — Andrew-led local compliance (Andrew led)
- Legal and budget gates — Budget holders (Partner-owned delivery)
- Deployment decision — Final state (External approval gate)
My scope
Andrew owned or led
- •Local implementation review coordination
- •Security and compliance documentation assembly
Partner or external ownership
- •Vendor analytics implementation architecture
- •Legal and budget approval gates
Decisions & execution
Decision 01
Balanced cross-domain tracking requirements with local privacy and security review constraints
Why it mattered
Protected browser-side user privacy and organisational trust boundaries.
Key Execution Actions
- Assembled cyber-security and data-processing documentation.
- Led implementation review across vendor, IT security, and legal teams.
Outcome & attribution
Outcome & System Change
Architecture and cyber-security documentation were completed. Deployment remained gated on budget and legal approval.
Individual Contribution & Boundary
Coordinated local cyber-security review, assembled documentation, and aligned legal/IT stakeholders.