Where would you describe analytics before launching an application?

The analytics description before launching the application should be documented in the following documents and artifacts:

• Technical Specification (TS): In the "Analytics Requirements" or "Analytics System" section, the main metrics, events, and parameters to be collected are listed. The analytics platforms planned for integration are specified.
• Functionality Specifications: For each functionality requiring analytics, specific events to be sent and their parameters are described. For example: "When clicking the 'Buy' button, send the 'purchase_button_clicked' event with the 'item_id' parameter."
• Analytics API Documentation: If a third-party SDK or an internal system is used, detailed integration documentation should be provided, including descriptions of classes, methods, and examples of event sending.
• Test Plan: Test cases should include verification of the correctness of sending analytical events for the declared usage scenarios.
• Product/Business Team Documentation: Description of collected metrics, their purpose, and ways to interpret them for making business decisions. This helps align data collection with product goals.

It is important that the description is accessible to all team members: developers, testers, product managers, and analysts.