# AI-generated descriptions for events and properties — Amplitude Changelog

Amplitude now makes it much easier to maintain a shared understanding of your taxonomy by automatically generating descriptions from both Amplitude usage and AI context, while still providing transparency about what’s been verified and what has been generated.

Source: https://amplitude.com/en-us/releases/ai-generated-descriptions-for-events-and-properties

---

[Changelog](/releases)/AI-generated descriptions for events and properties

DataSep 14, 2026

# AI-generated descriptions for events and properties

Amplitude now makes it much easier to maintain a shared understanding of your taxonomy by automatically generating descriptions from both Amplitude usage and AI context, while still providing transparency about what’s been verified and what has been generated.

## What it is

**Description:** Amplitude now makes it much easier to maintain a shared understanding of your taxonomy by automatically generating descriptions from both Amplitude usage and AI context, while still providing transparency about what’s been verified and what has been generated. Customers still have full control over the metadata, modify any definitions they want, and maintain verified descriptions while still taking advantage of automatic improvements.

**Why:** Most customers have thousands of events and properties with empty or stale descriptions and no realistic way to backfill them by hand, which blocks them from trusting AI answers about their data. Previously, the only path was documenting the taxonomy manually, one entity at a time, and it drifted from the team's spec as soon as it was written. Amplitude now drafts those descriptions automatically, provides transparency on the source, and flips to a model where you can bring in a lot of context automatically and modify a few things.

**How we generate them:** There are two primary inputs: First, files uploaded to the project under Settings -> AI Controls (a data dictionary, a tracking plan, a product spec), which we treat as the most authoritative input. Second, the project's own Amplitude data, meaning how the entity is actually used: the charts, dashboards and cohorts it appears in, how popular and recently use those are, the events and properties it co-occurs with, its event and query volume, and for a property, the values it takes. We only suggest what we can trace back to one of those, so an entity with thin usage and no matching file gets no suggestion at all. Because uploaded files outrank anything we can infer on our own, getting a customer to upload their data dictionary is the highest-leverage thing we can do for description quality, and one covering both events and properties beats an event-only or partial reference.

**Where it's used:** These descriptions don't just sit in Data. They already enrich the context behind Global Agent, new event search in dropdowns, and Data Health Score, so customers benefit immediately with no extra work.

**Availability:** All paid plans with AI features enabled.

**Not supported:** Every other property type other than event and user properties, custom events, labeled events, and transformations. Only files scoped to the project are used, not organization-level files.

**Available in EUDC:** Yes

**When:** Available now.

**Public Docs:** <https://amplitude.com/docs/data/event-property-descriptions#ai-generated-descriptions>

Release details

- Release ID

  ai-generated-descriptions-for-events-and-properties

- Shipped

  Sep 14, 2026

- Area

  Data

[Follow ](/releases/feed.xml?area=Data)

<!-- -->

[Data](/releases/feed.xml?area=Data)