> ## Documentation Index
> Fetch the complete documentation index at: https://mixpanel-edb78807-docs-events-properties-soft-limit-5000.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# AI-Powered Data Governance

Mixpanel uses AI to help you keep your project clean and well-governed with less manual effort. Instead of hunting through Lexicon by hand, these capabilities proactively surface issues in your data and let you resolve them in bulk.

<Info>
  AI-Powered Data Governance is available to organizations on an **Enterprise** plan that have Mixpanel's AI features (Mixpanel Agent) enabled in your organization settings. See our [pricing page](https://mixpanel.com/pricing/) for more details.
</Info>

## Merge suggestions

Over time, the same concept often ends up tracked under several names — `Add to Cart`, `add_to_cart`, and `addToCart`, or `from_date` and `from-date`. These duplicates clutter Lexicon, split your data across reports, and make analysis harder.

Merge suggestions automatically discover these potential duplicates in your project for you, so you don't have to hunt for them by hand. Mixpanel groups near-duplicate **events** and **event properties** together and suggests a single canonical name for each group, so you can clean them up in bulk instead of merging one pair at a time.

<Info>
  Merge suggestions cover events and event properties only — user (profile) properties cannot be merged at this time.
</Info>

To review and apply merge suggestions:

1. Open [Lexicon](/docs/data-governance/lexicon) and click **Tidy Up**, then **Reduce clutter**.

   <img src="https://mintcdn.com/mixpanel-edb78807-docs-events-properties-soft-limit-5000/xEO55mq8wbySO3SL/images/data-governance/merge-suggestions-tidy-up.png?fit=max&auto=format&n=xEO55mq8wbySO3SL&q=85&s=7374c1f3c22da011bb32d1a6dc95e78c" alt="Tidy Up entry point in Lexicon" width="194" height="198" data-path="images/data-governance/merge-suggestions-tidy-up.png" />

2. The **Merge Duplicate Events and Properties** window opens, listing the suggested groups of duplicates in two sections — Events and Event Properties.

   <img src="https://mintcdn.com/mixpanel-edb78807-docs-events-properties-soft-limit-5000/xEO55mq8wbySO3SL/images/data-governance/merge-suggestions-modal.png?fit=max&auto=format&n=xEO55mq8wbySO3SL&q=85&s=d68d61e72085ec9ec57fcc9f11da335b" alt="Merge suggestions modal listing duplicate events and properties" width="749" height="719" data-path="images/data-governance/merge-suggestions-modal.png" />

3. Review the suggestions. **Every group is selected by default.** Each group shows the near-duplicate names it found and the canonical name they'll merge into. To change the canonical name or drop a name from a group, edit the group before submitting.

4. Uncheck any group you don't want to merge, or use **Select all** / **Deselect all** to adjust the whole list at once.

5. Click **Merge Duplicates** to submit.

<Warning>
  Submitting is a single batch action: **selected groups are merged, and every unselected group is dismissed** so it won't be suggested again. If you want to keep a suggestion for later, leave the window without submitting rather than deselecting it.
</Warning>

Merging behaves exactly like a [manual Lexicon merge](/docs/data-governance/lexicon#merging-data) — the underlying raw data is unaffected, and a merge can be undone from Lexicon. As with any merge, update any reports or custom events that referenced the old names afterward, and note that [Autocapture](/docs/tracking-methods/autocapture) events cannot be merged. Merging requires the same permission as a manual merge.

## Automated Metadata Enrichment

Raw event names rarely explain themselves. `btn_clk_add_crt` means something to the engineer who instrumented it and little to anyone else, including Mixpanel Agent and MCP, which rely on Lexicon to understand your data. Writing a display name and description for every event takes time, so most projects have gaps. Mixpanel can now fill them for you.
With this update, you can:

* **Fill every gap in one action**: From Lexicon → Tidy Up → Fill in the blanks, Mixpanel generates a display name and description for each event missing one and applies them across your project.
* **Get names that fit your data**: Suggestions draw on the event name, sample property values, and your project's Business Context, and follow your naming convention when Data Standards is enabled.
* **Keep what you wrote**: Enrichment only fills gaps. Events with an existing display name or description keep what you gave them.
* **See what changed**: Every enriched field is recorded in the event's history, attributed to the user who ran the fill, marked as AI-applied, and written to your audit log like any other Lexicon edit.

The same fill is available to agents over MCP via the Fill-Event-Metadata tool and inside Mixpanel Agent.
This release covers events. Property enrichment is next.
