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.
Planned events that never arrived: confirm the problem
An event can remain in your tracking plan for months even if the team never ships the code that sends it. The entry clutters your taxonomy and incorrectly indicates that the team implemented the event.
To prove that an event is obsolete, you must distinguish an unimplemented event from an event with no recent activity. Data Assistant doesn't identify these entries. Observe shows whether Amplitude received an event during the selected time range, up to 14 days. Use your planning records to determine when someone planned the event. Use an approved raw-data source to check a longer history.
Run this audit as part of a scheduled taxonomy review. You need permission to manage data in the project. Without a planning record, you can confirm that an event has no observed data. However, you can't establish how long the event has been in the tracking plan.
Build the review list
- In Amplitude Data, go to Data > Events and review the events in your tracking plan.
- Set Observe to its longest available time range and find planned entries with no observed data.
- Use your planning record to find entries that have remained unimplemented beyond your review period, such as 90 days.
- Ask the event owner whether the implementation still belongs on the roadmap.
- Ask an analyst or data engineer to check an authorized raw-data export or warehouse for the exact event name. If an authorized source is unavailable, record the result as "not observed in Amplitude Data." Don't claim that the event never arrived.
- Check the event's description, source, owner, and related branch or ticket before you approve removal.
No activity doesn't prove an event is obsolete
An event might belong to a rare workflow, a disabled feature, or a future release. Confirm the decision with the product and engineering owners before you remove the event from the plan.
Amplitude verification limits
Observe shows which events arrive during the selected time range. Your planning system records which events the team planned. Planned events with no observed data form the review list. After the owner approves removal, delete the planned entry in Amplitude Data or use the Taxonomy API. Follow the removal guide.
Ask Global Agent
Global Agent can check event volume. Try a prompt like:
"Has the event [EVENT NAME] received any data in the last 180 days?"
Review the result and its supporting data to confirm whether the event arrived during that period. Global Agent can't determine when someone planned the event. Use your planning records to find the creation date. Global Agent also can't remove the plan entry.
Record whether to keep or remove the event
If the implementation is still planned, keep the event and assign an owner and review date. If the event no longer belongs in the plan, send the exact ingested name and approval record to the person responsible for the removal procedure.
Was this helpful?