I'm using the server side Segment Ruby SDK to track events from the backend, and those events along with custom properties attached will end up in Amplitude where they are analyzed to produce product metrics. I noticed that the events tracked from the frontend using the Segment JavaScript SDK all have properties like session_id, os_name, device_brand, etc. automatically collected as part of the event properties when they are sent to Amplitude, but the backend tracking calls don't have any of those properties automatically collected. So I am wondering what do I need to do so that Amplitude can auto collect session_id, os_name, device_brand, etc. through the Segment backend (Ruby) tracking calls.
Asked
Active
Viewed 241 times
0
ctzw
- 1