Overview:
Amplitude events have inconsistent granularity levels, making analysis difficult. Generic events like API Call generate ~200k events/week (mostly automated CI/CD) while specific UI events generate ~2-50k events/week. The generic events require property drilling to understand user behavior.

Problem Details:

The API Call event captures backend API usage (DetectBuildTime, Splunk integrations) rather than UI user behavior. This creates noise and inconsistent event modeling.

Acceptance Criteria:

• [ ] Decide: Archive API Call or split into specific events (e.g., CI Build Detection Triggered, Splunk Integration Sync)
• [ ] If splitting, implement new event types in backend telemetry
• [ ] Document event granularity guidelines in analytics taxonomy
• [ ] Update amplitude-audit.md with resolution

Related Tickets:

• ROX-32641 - Original Amplitude audit that identified this issue
• ROX-32749 - Duplicate Segment events (related cleanup)