Opening Scenario
The growth team needs a real-time view of what users are doing across the web and mobile app: page views, button clicks, search queries, scroll depth, video plays. Targets: an executive dashboard showing today's funnels live; A/B test result calculations within minutes (not the current 24-hour batch); a feature flag rollback dashboard if conversion drops after a deploy; an export to the warehouse for analysts. Current setup: each app sends events via REST to a single ingestion service that writes to Postgres, which is melting under the load. Marketing wants attribution within an hour, finance wants every revenue-attributable event reconciled, and a security review just flagged that one event contains a credit-card number a developer forgot to redact. Before you redesign, you need to understand the canonical click-stream pipeline, the quality and PII gotchas, and how to serve four very different downstream use cases from one ingestion path.
In the full tutorial
- Question Progression
- When to Reach for This