![]() ![]() These events will appear in a user's event stream as disconnected green squares.īy default, Amplitude sorts events into sessions according to session ID. Out-of-session events are normally server-side events received by Amplitude (see our HTTP API article for more details). Because they do not extend the current session, they can be useful if you're logging events triggered by push notifications. Out-of-session events are not considered part of the current session. You can also log events as out-of-session by setting the session ID to -1. If you would like to send event properties for session start/end events, try implementing your own custom Open App and Close App events. You will not be able to add additional event properties to these Start Session and End Session events.The End Session event will be sent at the start of the user's next session.Start/End Session events count towards your monthly event volume limit.Refer to Amplitude's Developer Center for all SDK documentation. This only applies to Amplitude's Android, iOS, and Browser SDKs.trackingSessionEvents = YES įor Browser: amplitude. That said, if tracking Start Session and End Session events is critical to your analysis outside of session lengths, you can easily turn on tracking for these events by adding this line of code before initializing the SDK:įor Android: Amplitude amplitude = new Amplitude ( new Configuration ( apiKey = AMPLITUDE_API_KEY, context = applicationContext, trackingSessionEvents = true, )) įor iOS. I f you use session IDs, Amplitude will not add additional events to your monthly event volume limit. ![]() Amplitude also uses session ID to calculate session lengths. Start Session and End Session eventsīy default, Amplitude tracks Start Session and End Session events using the beginning and ending times of each session by session ID. As with sending data via HTTP API, you will have to explicitly set a session ID to track sessions.Įvents included in the same session will be connected with a blue line, as shown above. ![]() 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 Browser 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.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |