🚫 Metrics Update: Deprecating event_dau metric

📣 Important Announcement 📣

We’re reaching out to give you a heads-up about an important change we are making to the auto-generated event_dau metric for Cloud customers in the Statsig Console.

Note: Customers on Statsig Warehouse Native will not be impacted.

In two weeks, from Wednesday, October 16 2024 onwards we plan to stop auto-generating new event_dau metrics for incoming events in Statsig. We will continue to auto-generate an event_count metric for each logged event as we do today.

• Any existing event_dau metrics that have been used in a gate, experiment, dashboard, or other Custom Metrics will NOT be affected by this change.

• Existing event_dau metrics that have been archived or not been used in another config will NO longer exist in the project. See ‘Next steps’ below if you want to retain the unused metrics.

• Going forward, new event_dau metrics will need to be created manually as a Custom Metric. See this guide to learn how to create a DAU metric.

We will be making this change on October 16, 2024. If you have any questions or concerns, please don’t hesitate to reach out!

More Context on This Change

Historically, we have automatically generated an event_count and event_dau metric for every incoming event into Statsig. After working closely with hundreds of customers, we have seen that auto generating two metrics for every event leads to confusion and clutter inside Statsig projects. The proposed change will lead to cleaner Metrics Catalog and faster Console performance, while still retaining your ability to create event_dau metrics for the events you care about most.

Next Steps

If you wish to keep any unused event_dau metrics going forward, you can earmark that metric by performing any of the below actions:

• Adding a Tag (RECOMMENDED)

• Adding a description

• Referencing in a gate/experiment/dashboard

These actions will mark your unused metric as active, signaling us that you don’t want them to be deprecated.