![]() ![]() NOTE: This commonly occurs when sending data to Amplitude from Segment via a cloud-mode connection. This means the event is excluded from all session metrics. ![]() However, for events sent via the HTTP API, Amplitude defaults to a session ID of -1. You can also change the property you use to group sessions.Īs noted above, session IDs for events sent via the Amplitude SDKs are automatically generated and managed. The session ID does not have to be unique across multiple users. All events with the same session ID and the same user ID will be grouped into the same session. ![]() How Amplitude tracks your sessionsīy default, the setting in Amplitude for the session property is session ID. However, if you are sending data to Amplitude using the HTTP API, you will have to explicitly set the session ID field in order to track sessions. If you are using Amplitude's SDKs, this happens automatically. All events within the same session share the same session ID. This timeout window can be customized via the JavaScript SDK configuration options.Īmplitude 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 fired within 30 minutes of each other are counted as part of the same session. Web sessions time out after 30 minutes by default.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |