When engineering teams release a major new module—such as a batch report generator, an advanced filtering modal, or an automated workflow trigger—the immediate question asked by stakeholders is invariably: “How many users are using it?”
To answer this, analytics dashboards commonly display an aggregate count of monthly active users who triggered at least one event associated with the new feature. But this single metric conflates three wildly different user realities:
- The user who clicked the new button accidentally, found the modal confusing, and immediately clicked “Cancel”.
- The user who diligently configured all parameters, attempted to run the process, encountered a validation error, and abandoned the task.
- The power user who executes the complete workflow five times a day as part of their routine operational responsibilities.
Lumping all three into a single “Adoption Rate” percentage creates a dangerous illusion of success while masking critical product friction.
The Anatomy of Adoption Depth
To obtain a genuine reading of feature adoption, telemetry architects must measure Depth alongside Breadth. Breadth measures how widely a capability has penetrated across the total user base. Depth measures the degree of operational commitment exhibited by individual accounts.
We structure adoption depth across four distinct verification tiers:
[ Tier 1: Exposure ]
└─ User encounters feature UI entry point (viewed tab, hovered tooltip).
[ Tier 2: Exploration ]
└─ User initiates configuration (opened modal, adjusted form inputs).
[ Tier 3: Execution ]
└─ User achieves full transaction success (received server 200 OK confirmation).
[ Tier 4: Habituation ]
└─ User repeats execution across multiple distinct operational cycles.
Instrumenting the Critical Transition Points
The most valuable insights emerge not from the raw counts within each tier, but from the conversion ratios between tiers.
Transition 1: Exposure to Exploration (The Discoverability Ratio)
If 10,000 active users view the parent navigation bar, but only 200 ever click to explore the sub-feature, the bottleneck is discoverability. The entry point may be buried beneath unintuitive hierarchy or poorly labeled.
Transition 2: Exploration to Execution (The Usability Ratio)
If 2,000 users open the configuration modal, but only 150 successfully click the final execution button, the bottleneck is workflow usability or cognitive friction. This requires auditing form length, field validation clarity, and permission gating.
Transition 3: Execution to Habituation (The Value Ratio)
If 1,000 users successfully execute the feature once, but only 20 repeat the action the following week, the feature may fail to deliver enough ongoing utility to warrant integration into habitual workflows.
Key Payload Properties to Record
To support multi-tier depth calculations, ensure your client-side event payloads contain these critical attributes:
interaction_depth_tier: Explicit integer (1-4) reflecting the current milestone.workflow_session_id: Unique identifier binding the entire sequence from modal open to final completion.step_completion_count: Cumulative count of intermediate inputs successfully validated.prior_execution_count: Historical count of lifetime completions recorded for the current authenticated user.
By instrumenting telemetry with these structured parameters, product and engineering leaders gain the ability to pinpoint exact points of attrition rather than debating ambiguous macro metrics.