Design Product Page View Tracking

Quick Overview

This question evaluates a candidate's ability to design scalable, reliable event-collection and analytics systems, covering client- and server-side instrumentation, event schemas/APIs, counting total versus unique views, handling high write volumes for popular products, storage choices for raw events and aggregated counters, and operational concerns such as bot filtering, deduplication, privacy, fraud prevention, freshness, reliability, and monitoring. It is commonly asked in the System Design domain to assess architectural thinking and operational trade-offs, testing both conceptual understanding of distributed systems and practical application of scalable data pipelines, storage, and observability.

Design Product Page View Tracking

Company: Uber

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design a view-tracking system for a large e-commerce product detail page. When a shopper opens a product page on web or mobile, the system should record the view. The product page may display view-related information such as total views, recent views, or seller-facing analytics. Please cover: - Client-side and server-side event collection. - APIs or event schemas for recording page views. - How to count total views and unique views. - How to handle very popular products with high write volume. - Storage choices for raw events and aggregated counters. - Bot filtering, duplicate handling, privacy, and fraud prevention. - Freshness requirements, reliability, and monitoring.

Quick Answer: This question evaluates a candidate's ability to design scalable, reliable event-collection and analytics systems, covering client- and server-side instrumentation, event schemas/APIs, counting total versus unique views, handling high write volumes for popular products, storage choices for raw events and aggregated counters, and operational concerns such as bot filtering, deduplication, privacy, fraud prevention, freshness, reliability, and monitoring. It is commonly asked in the System Design domain to assess architectural thinking and operational trade-offs, testing both conceptual understanding of distributed systems and practical application of scalable data pipelines, storage, and observability.

|Home/System Design/Uber
Uber logo
Uber
Apr 12, 2026, 12:00 AM
mediumSoftware EngineerOnsiteSystem Design
10
0

Design a view-tracking system for a large e-commerce product detail page.

When a shopper opens a product page on web or mobile, the system should record the view. The product page may display view-related information such as total views, recent views, or seller-facing analytics.

Please cover:

  • Client-side and server-side event collection.
  • APIs or event schemas for recording page views.
  • How to count total views and unique views.
  • How to handle very popular products with high write volume.
  • Storage choices for raw events and aggregated counters.
  • Bot filtering, duplicate handling, privacy, and fraud prevention.
  • Freshness requirements, reliability, and monitoring.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Uber•More Software Engineer•Uber Software Engineer•Uber System Design•Software Engineer System Design