Design the event instrumentation for Pricing Tools at scale

Problem Statement Description

Product context: Airbnb is a travel marketplace connecting guests and hosts; its products include stays, experiences, host tools, guest booking, trust and safety, payments, and reviews.

Airbnb hosts rely on Pricing Tools to set nightly rates, apply discounts, respond to demand changes, and stay competitive across different markets and guest segments, including business travelers with distinct booking patterns. At Airbnb scale, these pricing interactions happen across surfaces such as host dashboards, calendar views, mobile apps, recommendation modules, and potentially automated pricing features.

Design the event instrumentation for these Pricing Tools so product, data science, engineering, and marketplace teams can understand how hosts discover, evaluate, adopt, modify, and abandon pricing recommendations or controls. The instrumentation should support reliable analysis of host behavior, pricing feature performance, marketplace outcomes, and operational health without over-collecting sensitive data or creating brittle event definitions.

You are not being asked to design the pricing algorithm itself. Focus on what should be tracked, how events should be structured, how data quality and privacy should be handled, and how the instrumentation can scale across geographies, listing types, devices, and future pricing features.

The experience should consider:

- Core user workflows, including viewing pricing insights, editing nightly prices, applying discounts, enabling automated pricing, reviewing recommendations, and undoing changes.

- Event taxonomy and naming conventions for impressions, interactions, submissions, errors, confirmations, and downstream pricing outcomes.

- Required event properties such as listing context, host cohort, market, date range, device, feature surface, recommendation metadata, and experiment assignment.

- Data pipeline expectations, including client-side vs server-side events, deduplication, ordering, latency, schema evolution, and backfill needs.

- Reliability and observability requirements for detecting missing events, malformed payloads, instrumentation drift, and regional or platform-specific gaps.

- Privacy, security, and access-control considerations for host revenue data, listing performance, market demand signals, and business traveler-related attributes.

- Product trade-offs between comprehensive tracking, implementation complexity, performance overhead, data minimization, and long-term maintainability.

- How the instrumentation enables decisions about feature adoption, host trust, pricing effectiveness, marketplace quality, and potential negative side effects.

The goal is to define a scalable instrumentation approach that gives Airbnb teams trustworthy, actionable data about Pricing Tools usage and impact while respecting host trust, marketplace integrity, and the technical realities of a global, multi-platform product.