The special DevSandbox telemetry is not being properly used in the Developer Sandbox clusters. This is caused by two things:

1. Developer Sandbox clusters were migrated from OSD to ROSA, thus the current if statement https://github.com/openshift/console/blob/a00af1a77a8a85f558733609a6dd8b258b1a6348/frontend/packages/console-shared/src/hooks/useTelemetry.ts#L44 is not applicable anymore. As a result, the cluster type is not marked as DEVSANDBOX, which means that any other DevSandbox-specific logic is not applied: https://github.com/openshift/console/blob/a00af1a77a8a85f558733609a6dd8b258b1a6348/frontend/packages/console-telemetry-plugin/src/listeners/segment.ts#L68-L74

2. The priority of loading the telemetry keys has been changed so the DEVSANDBOX_SEGMENT_API_KEY is loaded as the last one - see: https://github.com/openshift/console/blob/aa30da36c804d9e523f51902ae123c02586551cc/frontend/packages/console-dynamic-plugin-sdk/src/api/segment-analytics.ts#L4-L7
However, since the managed ROSA clusters already come with the SEGMENT_API_KEY set (set by SD team and we cannot do anything with it), then the DEVSANDBOX_SEGMENT_API_KEY is never used.
The priority of the keys was changed in this commit https://github.com/openshift/console/commit/56139d0778e22d7c1dd428ce025800cb30d7006f

4.20.x

You need to provision a cluster with Developer Sandbox setup and check the telemetry

    1. Provision ROSA cluster
    2. Set values for:
        telemetry.console.openshift.io/DEVSANDBOX_SEGMENT_API_KEY
        telemetry.console.openshift.io/DEVSANDBOX: 'true'
    3. See the Segment events
    

there are no events sent with the devsandbox segment api key
the events are anonymized 

there are events sent with the devsandbox segment api key 
the events are not anonymized