LWCArchitect (Hardest)telemetryprivacyanalytics
Architect LWC telemetry without PII leakage to browser analytics
Real World Scenario
Marketing installs browser analytics on Experience Cloud; LWCs accidentally emit user email and Account names in custom event payloads.
Expected Answer
• Define telemetry schema allowing only anonymized IDs and action names
• Hash record Ids if correlation needed — never emit names emails phones
• Centralize telemetry helper module reviewed by security
• Block production PRs adding new telemetry fields without review
• Use server-side event logging for sensitive audit trails
• Document prohibited fields in LWC coding standards
• Periodic scan of event payloads in staging with DLP rules
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Define telemetry schema allowing only anonymized IDs and action names. Hash record Ids if correlation needed — never emit names emails phones. Pick based on your integration pattern and team capability. Client telemetry is a data exfiltration risk — treat event payloads like public API contracts. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Client telemetry is a data exfiltration risk — treat event payloads like public API contracts.