Review Event Discovery Agent suggestions
이 페이지는 아직 귀하의 언어로 번역되지 않았습니다. 현재 작업 중이므로 곧 다시 확인해 주십시오.
Event Discovery Agent proposes new events for your tracking plan on a schedule. Reviewing those suggestions is ongoing work, separate from the one-time setup. For setup, requirements, and permissions, refer to Event Discovery Agent.
Each suggestion includes a description, a category, a definition, an analytical value rating, and a verdict on how reliable its definition is likely to be. Review each suggestion, edit it if needed, then accept the ones you want in your taxonomy and dismiss the rest.
Find suggestions
- In Amplitude Data, go to Events.
- Click the Agent-Suggested tab.
The Open view lists suggestions waiting for review. The Dismissed view lists suggestions someone dismissed. A sparkle icon next to each name marks the event as agent-suggested.
For each suggestion, the table shows its name, category, analytical value, whether it's safe to accept, its occurrences in the selected date range, and when the agent created it. The list sorts by analytical value, highest first. To export open suggestions as a CSV file, click Download.
Review a suggestion
Click a suggestion to open its details panel. The panel includes:
- Analytical value: The rating and why the agent assigned it.
- Verdict note: Whether the suggestion is safe to accept and why.
- Description: What triggers the event, the user journey it belongs to, and how you might use it in analysis.
- Category: An existing category from your taxonomy that fits, or a new one the agent proposes.
- Occurrences: How often the event occurred in the last 30 days.
- Screenshot / GIF: A visual of the interaction, when available.
- Definition: The Autocapture event and the element selector the labeled event matches.
Use the agent's evidence and verdict as a starting point. Then confirm that the description and definition accurately capture the interaction you want.
To build a screenshot or GIF, the agent loads the public page where the event occurs and highlights the control. If that doesn't work, for example because the page requires a login, it uses a frame from a Session Replay recording, labeled Inferred event match. Some suggestions have no visual. Visuals are approximate representations of the event, so check the definition to confirm it tracks what you want.
Analytical value
Analytical value is the agent's estimate of how much an interaction is likely to matter for your analysis, based on how central it is to your core product flows.
| Rating | Meaning |
|---|---|
| High | The interaction is critical to a core user flow, such as activation, onboarding, or a primary conversion path. Tracking it is likely to have a significant impact on your analysis. |
| Medium | The interaction is part of an important but secondary flow. It may support product discovery, engagement, or feature adoption, and is worth tracking for comprehensive analysis. |
| Low | The interaction occurs in a supporting or peripheral flow. It may be useful for edge case analysis but is less likely to affect core metrics. |
Safe to accept
Each suggestion's definition relies on identifiers your site exposes, such as attributes, IDs, or classes on an element. Some identifiers are more stable than others. The Safe to Accept? column shows how well the definition matches the event it names and how likely it is to keep working as your site changes.
The agent checks two things:
- Durability: Whether the identifier is likely to survive changes to your site.
- Accuracy: Whether the definition counts only the control the event name describes.
| Verdict | Meaning |
|---|---|
| Yes | The definition passes both checks. It's unlikely to break or lose data after you accept the suggestion. |
| Worth a check | The definition fails at least one check. It may stop matching after a site change, or it may count more than the control its name describes. Review the definition before you accept the suggestion. |
In the details panel, the verdict appears as Safe to accept or Check before accepting, with a note that explains the reason in plain language. When the agent flags a suggestion, the note also suggests a fix, such as asking your engineering team to add a fixed identifier to the control.
A definition is more durable when it uses an identifier that's specific to the element and unlikely to change:
| More durable | Less durable |
|---|---|
Attributes your team adds for testing or tracking, such as data-testid or data-track. | Identifiers the element shares with other elements, such as a class used on several buttons. |
Stable id attributes on the element. | Style classes and build-generated class names or IDs, which can change on the next deploy or redesign. |
A link destination (href) or a specific page route. | Visible text, labels such as aria-label, and values that contain prices or counts. |
Accuracy issues usually mean the definition is broader than the name. For example, the name calls the control a button, but the agent recorded the click on a container around it.
A Yes verdict reflects your site at the time the agent reviewed it. The verdict can't guarantee long-term reliability, because changes to your site's code can still affect the definition. If an accepted event stops collecting data, go to Repair a labeled event.
Edit and test a suggestion
Before you accept a suggestion, you can update its name, description, category, and definition directly in the details panel.
To check the data before you accept a suggestion, click Create Chart in the details panel. Amplitude opens a chart with the suggested event so you can confirm the volume and trend match what you expect. Volume far above or below what you expect can mean the definition matches a different element.
Admins and managers can always chart a suggestion before it's accepted. Other users can chart it only when the Show suggestions in event dropdowns before they are accepted setting is on.
Accept or dismiss a suggestion
- Accept: Click Accept in the details panel. Amplitude adds the event to your Labeled Events tab and no longer marks it as agent-suggested.
- Dismiss: Click Dismiss. The suggestion moves to the Dismissed view.
To restore a dismissed suggestion, open it from the Dismissed view, click Restore, and confirm. The suggestion returns to the Open view for review.
The agent checks dismissed suggestions so it doesn't suggest the same event again right away. If a later run finds more evidence for the interaction, the agent can suggest a similar event.
To work through a long list, click Add Filter to narrow the Open view by category, 30 Day Occurrences, 30 Day Queries, Analytical Value, Safe to Accept?, or Created Date. For example, filter to High analytical value and Yes to review the most valuable, most reliable suggestions first. To dismiss several suggestions at once, select them in the list, then click Dismiss.
이 내용이 도움이 되었나요?
For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.