Is your feature request related to a problem? Please describe?
Currently, Amplitude events do not include region-level context, making it difficult to analyze migration data across different regions.
Detailed Description
The OS Region name available from credentials is unique in most cases, as no two customers typically share the same region.
We should include the OS Region name as part of the Amplitude event payload during migration-related actions. This will allow:
- Tracking migrations at a region level
- Better segmentation and analysis of usage patterns
- Improved visibility into region-specific behaviors and performance
Expected Implementation:
- Extract the OS Region name from selected credentials
- Attach it as a property in relevant Amplitude events (e.g., migration started, completed, etc.)
Anything else you would like to add?
No response
Is your feature request related to a problem? Please describe?
Currently, Amplitude events do not include region-level context, making it difficult to analyze migration data across different regions.
Detailed Description
The OS Region name available from credentials is unique in most cases, as no two customers typically share the same region.
We should include the OS Region name as part of the Amplitude event payload during migration-related actions. This will allow:
Expected Implementation:
Anything else you would like to add?
No response