Amplitude is creating many session IDs for a timeline smaller than 30 minutes, breaking the events history into many incorrect sessions. This is distorting my session reports.
Does anyone had this problem before? Any suggestions?
(I’m using Amplitude SDK to track a website.)
See this example:
One minute later, the next page viewed event had another Session ID:
2 minutes later, yet another Session ID:
I did not change any Session definition in amplitude, so It should be considering all this example above within the same Session ID, as is triggered within 30 minutes timeframe.
