Skip to main content

So we are using Amplitude’s built-in Session solution on our mobile apps. However, because of the very large amount of events it is using, we are thinking of just removing the “End Session” and keeping “Start Session”. 

I’m curious from Amplitude’s standpoint, are we able to just use “Block” feature on the “End Session”, but keep the Start Session? This would allow us to remove the “End Session” from our usage, while still keep each session by tracking “Start Session”. 

How I understand it, it should still technically work because Amplitude still tracks sessions the exact same way when apps enable Auto Session Tracking - by checking a maximum time threshold after the last event before a new session is created. So although the sessions will technically be shorter with End Session missing, it will still pick up the last event fired by the user and log that as a session, right? Or will Amplitude be expecting an explicit “End Session” and break if it doesn’t find it?

Hi @liukaichi , Thanks for writing to the Community!

If you were to block the “End Session” event, you're telling Amplitude you want to continue to query on historical data but would like to stop collecting new data for that event or property. This can be helpful if a particular event is causing you to hit your monthly event volume limit. Please note that blocked events and properties will still count towards your project's instrumentation limit.

If you block “End Session”, you will still be able to track sessions using the “Start Session” and set up a session timeout. If you’re about to fire a new event, the SDK will compare it with the latest event. If the time difference is over the session timeout, then it will be a new session.

You can read more about how Amplitude tracks sessions here.

You can also read more about blocking events here. 

Reply


Terms & ConditionsCookie settings