Diagnose a 20 percent drop in activation for AirCover at global 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 has observed a 20% drop in activation for AirCover at global scale, with particular concern for first-time guests who rely on trust, protection, and reassurance when booking a stay. This is a root-cause analysis scenario: your task is to structure how you would investigate the decline, separate a true user-behavior issue from a measurement or rollout issue, and determine what action Airbnb should take next.

AirCover sits within a broader guest booking journey where users discover a listing, evaluate trust signals, complete checkout, and expect support if something goes wrong. A drop in activation could affect guest confidence, conversion, customer support demand, host trust, marketplace quality, and Airbnb’s competitive position against hotels and travel platforms.

You should approach the problem as if you are working with product, data science, engineering, design, operations, customer support, and regional market teams. The scope is global, so your investigation should account for differences across countries, platforms, languages, traffic sources, guest tenure, booking types, and recent product or policy changes.

The investigation should consider:

- How “AirCover activation” is defined, including the numerator, denominator, event timing, eligibility rules, and whether the metric applies to all guests or only specific booking flows.

- Whether the 20% decline is statistically significant, when it began, how long it has persisted, and whether it is a step-change, gradual trend, or seasonal pattern.

- Segmentation by first-time versus returning guests, geography, platform, app version, device, listing type, trip length, price band, cancellation policy, and acquisition channel.

- Instrumentation checks, including event logging, data pipelines, experiment flags, eligibility logic, localization, consent settings, and dashboard changes.

- Product and workflow hypotheses across discovery, listing page, checkout, trust messaging, support entry points, post-booking communication, and claim or protection flows.

- External and marketplace factors such as travel seasonality, regional regulation, host supply quality, pricing shifts, support backlogs, competitor messaging, or trust-related incidents.

- Evidence needed to prioritize hypotheses, including funnel data, experiment readouts, user research, customer support contacts, complaint themes, operational metrics, and host-side signals.

- Immediate mitigation, monitoring, escalation paths, and prevention mechanisms to reduce recurrence and protect guest trust while the root cause is being confirmed.

The goal is to demonstrate a rigorous, structured RCA approach that identifies the most likely drivers of the activation drop, quantifies business and user impact, defines the data needed to validate or reject hypotheses, and recommends a clear path for containment, recovery, and long-term prevention without jumping prematurely to a solution.