Skip to content

Clarify One-Time Event metrics UI display #2875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify One-Time Event metrics UI display #2875

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/metrics/create.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ The example below creates a metric to count the **number of unique users** who v
Two time window options are available for user count metrics

- Daily Participation Rate: It counts the total number of days that a user has the selected event, divided by the number of days the user is in the experiment. The result is a metric value between 0 and 1, which represents the probably of a user having the event on a daily basis. It works best for events that are expected to occur repeatedly for a given user.
- One Time Event: This checks if a user has the selected event at least once during their time in the experiment. The result is a binary metric with value 0 or 1 for each user. This is ideal for events that are only expected once per user, such as sign up events.
- One Time Event: This checks if a user has the selected event at least once during their time in the experiment. The result is a binary metric with value 0 or 1 for each user. This is ideal for events that are only expected once per user, such as sign up events. **Note: When viewing this metric in the experiment results UI, it will still show "daily_participation" as the aggregation type. This is because all unit count metrics use the same aggregation mechanism but are differentiated by their rollup property (for One-Time Events, the rollup is set to "max").**
- Custom Attribution Window: Allows you to define a custom window after exposure to count an event towards a metric calculation.

### 3. Aggregation Metrics
Expand Down
6 changes: 5 additions & 1 deletion docs/metrics/pulse.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,10 @@ Ratio metrics are computed only for users that have a non-zero value in the deno

**3. What is the difference in metrics between One-Time Event vs Daily Participation Rate?**

The distinction between these in only relevant in the context of an experiment.
The distinction between these is only relevant in the context of an experiment.
Daily participation rate counts the number of _days_ a user has that event, divided by the number of _days_ the user has been in the experiment.
One time event is a binary metric that checks whether the user has that event _at least once_ during their time in the experiment.

**4. Why does my One-Time Event metric show as "daily_participation" in the experiment review UI?**

All unit count metrics in Statsig use the same aggregation mechanism (daily_participation) in the UI but are differentiated by their rollup property. For One-Time Event metrics, the rollup property is set to "max", which ensures the metric checks if a user performed an action at least once during the experiment. This is why One-Time Event metrics will display "daily_participation" in the UI despite being configured as one-time events during setup.