We have an amplitude connector extracting data from our app. The data is available on the amplitude dashboard and also on our snowflake api. We compared the data loaded via the amplitude connector to snowflake with that in the amplitude dashboard and we are seeing differences in the sessions measure. Also the session_id is not converting to an accurate timestamp of the relevant session.
Best answer by belinda.chiu
Happy to help here! To clarify, did you purchase Amplitude’s Snowflake package or are you using a different way to load Amplitude data into Snowflake?
Regarding to session_id, if you are using our native SDKs, Amplitude automatically generates a session ID for each new session; that ID is the session's start time in milliseconds since epoch (also known as the Unix timestamp). All events within the same session share the same session ID. https://help.amplitude.com/hc/en-us/articles/115002323627#how-amplitude-defines-sessions
If the behavior mentioned above is not what you are seeing for your session_ids, can you clarify what you mean by the session_id is not converting to an accurate timestamp of the relevant session?