Skip to main content

Hello allย ๐Ÿ˜„

I wanted to raise a question regarding session IDs and their use in Amplitude Analytics.

We have found (through searching for specific session IDs in Amplitude Analytics) that Amplitude adds on an extra three zeroes to our existing session IDs, which initially caused some confusion while searching for said IDs.

For an example: we may have a session ID of โ€œ1234567891โ€ that we pass into Amplitude. When we then search for this in Amplitude Analytics, we find that this session ID can now be found as โ€œ1234567891000โ€

I wanted to raise this to understand whether this intentional or whether this was potentially a bug?

Thank you for any responses!

Hey @ccreaserย 

Amplitude sets/ingests session IDs as milliseconds since epoch.

ย 


Reply