Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-32749

[Tech Debt] Investigate and fix duplicate Segment events in Amplitude

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None

      Overview:
      Amplitude is receiving duplicate events - every event is logged twice: once with its original name (e.g., Page Viewed) and once with a [Segment] prefix (e.g., [Segment] Page Viewed). This inflates event counts and causes confusion in analytics.

      Problem:

      • 107 total events in Amplitude, ~36 are [Segment] duplicates
      • Same event data, just different names
      • Causes double-counting in charts/dashboards
      • Makes taxonomy maintenance harder

      Root Cause:
      This is a Segment-to-Amplitude integration configuration issue, not a UI codebase issue. The UI sends one event via window.analytics (Segment SDK) - Segment appears to forward it twice to Amplitude.

      Acceptance Criteria:

      • [ ] Investigate Segment workspace configuration for duplicate destination or misconfigured settings
      • [ ] Fix configuration to send events only once
      • [ ] Verify events no longer duplicate in Amplitude
      • [ ] Consider archiving existing [Segment] prefixed events in Amplitude Data Governance

      Related Tickets:

      • ROX-32641 - Amplitude audit (identified this issue)

              Unassigned Unassigned
              schaudhr Saif Chaudhry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: