Hi,
I only started with Amplitude recently and everything seemed to be going well, however, since Tuesday, I’ve noticed my User Session charts are reporting zero sessions. (It’s Thursday today.)
Before you ask, yes, I can be sure that I’ve actually had user sessions since Tuesday. My Amplitude Event Segmentation charts are still reporting events, so there’s a contradiction in the data Amplitude is reporting for Sessions vs Events.
Any ideas?
Best answer by Saish Redkar
Hey
If your events are flowing in correctly but zero sessions are reported, then I would check if the Session ID for events since Tuesday is reported as -1 just in case. If it’s -1, then I believe all those events won’t contribute to any session metrics. Are you sending events via the HTTP API or a SDK implementation?
If not, then I suspect a potential bug. You can raise a ticket to the support team directly who can help look into this issue in depth.
Hope this helps!
+10Hey
If your events are flowing in correctly but zero sessions are reported, then I would check if the Session ID for events since Tuesday is reported as -1 just in case. If it’s -1, then I believe all those events won’t contribute to any session metrics. Are you sending events via the HTTP API or a SDK implementation?
If not, then I suspect a potential bug. You can raise a ticket to the support team directly who can help look into this issue in depth.
Hope this helps!
Yup, -1s. It looks like our Segment integration is no longer sending across our session IDs. I’ll investigate with Segment support. Thanks for your help.
+8Hi
Did you follow the Amplitude guide to integrating with Segment? Here is another by segment. I would read the parts about tracking sessions in the first link. I would especially read this article from Segment themselves which shows how to add a session ID with the Amplitude integration. Can you read the above articles and let me know if you followed the steps in the integrations and setting the session ID and if you still have the issue? Thank you!
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.
+8This 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.
Nice one! Thanks for the update
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. You can also create a Guest account below!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. Want to sign up as a guest? Create a Community account.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
