Sampling Rules for Busy Product Squads

Full capture sounds thorough and usually creates a library nobody opens. Prefer rules keyed to journeys under active investigation: higher sample on checkout failures, lower on already-stable browse paths, and a temporary boost after a release that touches a fragile flow.

Pair sampling with a weekly review slot owned by one person. Without ownership, even a perfect sample rate becomes unused storage.

Revisit rules after traffic spikes and after major UI changes. Sampling is part of insight hygiene, not a one-time install setting.