Event Deprecation

Event deprecation is the deliberate process of retiring an event: announcing it should no longer be used, migrating to a replacement, and finally stopping it — without breaking existing reports.

Unlike a sudden deletion, deprecation is a gradual, announced process, because an event cut off abruptly can silently break dependent dashboards and alerts. Its correct steps are: first the event is marked “deprecated” and its replacement introduced, then teams are given time to migrate, and only after it is no longer used anywhere is its sending stopped. The most dangerous mistake is renaming an event instead of deprecating it properly: the old name keeps its history and the new one starts from zero, and until the two are stitched together every trend chart stays broken. Orderly deprecation exists precisely to avoid this historical rupture; without it, every cleanup costs a loss of data continuity.