**Goal** This issue is aimed at creating a plan to promote the new unified Internal Event Tracking API to internal users. The plan is aimed at increasing awareness of the existence of this new system and highlighting its benefits over the old system. **Tasks** * [ ] Documents to be updated - [Analytics Instrumentation getting started page](https://about.gitlab.com/handbook/product/analytics-instrumentation-guide/getting-started/) (To be marked deprecated?) - [Analytics Instrumentation Guide](https://about.gitlab.com/handbook/product/analytics-instrumentation-guide/)(To be marked deprecated?) - [Analytics Instrumentation Vision Page](https://about.gitlab.com/handbook/engineering/development/analytics/analytics-instrumentation/) (Needs update) - [Gitlab Docs](https://docs.gitlab.com/ee/development/) * [ ] Slack channels that will need to be updated - g_analyze_analytics_instrumentation - product - data - g_analyze_product_analytics - analytics-section * [ ] Follow [multimodal communication](https://about.gitlab.com/handbook/communication/#multimodal-communication) guidelines in the handbook * [ ] Follow [informing team members](https://about.gitlab.com/handbook/product/#informing-team-members-about-the-changes) about changes guidelines **Ideas** - Add warning/alert banners to all handbook pages that have instructions on using the old system - Collect feedback on regular basis from users - Highlight the availability of the new systems in Product and Developer on following slack groups #product, #eng-managers, and #ux-managers (highlight our office hours for anyone wanting to ask question) - Add the change to [Engineering Week in Review](https://docs.google.com/document/d/1JBdCl3MAOSdlgq3kzzRmtzTsFWsTIQ9iQg0RHhMht6E/edit#heading=h.wl5oryd6kv3u) - ~~is there a way to detect and send an automated email guiding the user to the new system when they use the old way of instrumenting their applications?~~ cc @stkerr