The session_id=-1 when we use segment send data to amplitude

xiaomeng.zhang

Our system is Android mobile, when we use segment send data to amplitude, we found the session_id=-1, and we don not konw why? 

{<br />  "$insert_id": "ad359f15-3f6c-44fe-8a7d-51abe6d1fa5d",<br />  "$row_source": "realtime",<br />  "$schema": 12,<br />  "_time": 1634624174745,<br />  "adid": null,<br />  "amplitude_attribution_ids": [<br />    "d63abe7cdc0f0b2aa76ae262402f7e03"<br />  ],<br />  "amplitude_event_type": null,<br />  "amplitude_id": 251319235937,<br />  "app": 346475,<br />  "city": "Beijing",<br />  "client_event_time": "2021-10-19T06:16:14.745",<br />  "client_upload_time": "2021-10-19T06:16:27.923",<br />  "country": "China",<br />  "data": {<br />  },<br />  "device_brand": null,<br />  "device_carrier": "中国联通",<br />  "device_family": "Redmi Phone",<br />  "device_id": "c6adc3fd07f5e282",<br />  "device_manufacturer": "Xiaomi",<br />  "device_model": "M2006J10C",<br />  "device_type": "Redmi K30 Ultra",<br />  "display_name": "Page Viewed",<br />  "dma": null,<br />  "event_id": 118285483,<br />  "event_properties": {<br />    "app_country": "ID",<br />    "page_path": "/account"<br />  },<br />  "event_time": "2021-10-19T06:16:14.745",<br />  "event_type": "Page Viewed",<br />  "group_properties": {<br />  },<br />  "groups": {<br />  },<br />  "idfa": null,<br />  "ip_address": "103.90.177.233",<br />  "is_attribution_event": false,<br />  "language": "Chinese",<br />  "library": "segment",<br />  "location_lat": null,<br />  "location_lng": null,<br />  "os": "android 11",<br />  "os_name": "android",<br />  "os_version": "11",<br />  "partner_id": null,<br />  "paying": null,<br />  "plan": {<br />  },<br />  "platform": "Android",<br />  "region": "Beijing",<br />  "sample_rate": null,<br />  "server_received_time": "2021-10-19 06:16:27.923000",<br />  "server_upload_time": "2021-10-19T06:16:27.942",<br />  "session_id": -1,<br />  "start_version": "1.0.0",<br />  "timeline_hidden": false,<br />  "user_creation_time": "2021-10-15T09:38:05.579",<br />  "user_id": "801ebeea3212d50e2650513015b60074",<br />  "user_properties": {<br />    "anonymousId": "73a7c091-f0ef-4037-8c44-754a0ff78443",<br />    "userId": "801ebeea3212d50e2650513015b60074"<br />  },<br />  "uuid": "19c1c607-30a4-11ec-b00f-066df468c0f1",<br />  "version_name": "1.0.0"<br />}

 

Saish Redkar

Hey xiaomeng.zhang 
Here are some posts which address this issue, which seems to be prominent since a month 

 

Quoting zerosesh’s resolution in here:

This turned out to be a bug on Segment’s end.

We’re using the new ‘Amplitude (Actions)’ destination rather than the old ‘Amplitude’ classic destination. Until Tuesday last week, Amplitude Actions was mapping session ids via the ‘integrations.Amplitude.session_id’ key, until a change Segment’s side meant they started looking for ‘integrations.Amplitude Actions.session_id’ instead.

It’s possible to override this in the Amplitude Actions destination settings under the ‘Track’ action. Also, it appears case-sensitive and their UI doesn’t allow capital letters. To get around this you can trigger a test event in the same panel and then the proper cased option should appear in your ‘session_id’ dropdown.

 

Hope this helps.