# Deprecating Event_dau Metric

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

### Deprecation details

From Wednesday, October 16, 2024, Statsig stopped auto-generating new event\_dau metrics for incoming events. Statsig continues to auto-generate an event\_count metric for each logged event.

> **Note:**
>
> This change only affects Statsig Cloud customers. This change doesn't affect Warehouse Native customers.

- This change doesn't affect any existing event\_dau metrics that you have used in a gate, experiment, dashboard, or other Custom Metrics.
- Existing event\_dau metrics that you archived or never used in another config no longer exist. To retain these metrics, refer to the Next steps section below.
- Going forward, you must create new event\_dau metrics manually as a Custom Metric. Refer to [this guide](https://docs.statsig.com/metrics/custom-dau) to learn how to create a DAU metric.

Contact Statsig support if you have questions or concerns about this change.

### Motivation for this change

Historically, Statsig auto-generated an event\_count and event\_dau metric for every incoming event. Auto-generating two metrics for every event causes confusion and clutter inside projects. The deprecation produces a cleaner Metrics Catalog and faster Console performance, while retaining the ability to create event\_dau metrics for specific events.

### Next steps

To keep any unused event\_dau metrics, mark them as active by performing any of the actions below:

- Adding a Tag (RECOMMENDED)
- Adding a description
- Referencing in a gate/experiment/dashboard

These actions mark your unused metric as active, indicating that Statsig shouldn't deprecate the metric.