Session start and session end time stamps registered at GA are very often too late relative to other events

[11RS]

Session start and session end time stamps registered at GA are very often too late relative to other events.
This happens when session start and session end events are queued when there is no internet connection.
But it also happens whith all session end events, because session end events are only sent at the time when a new session is started.

Problem source: “QT” (Queue Time ) parameter is not appended to “SC” (Session Control) events.

Steps to Reproduce:

• Disconnect your client system from the internet.
• Do some tracking from your application: Start a session, genereate some other events, close session, wait for some seconds, start a new session.
• Re-connect to internet
• Login to analytics.google.com and open the according tracker
• Navigate to Audience / User Explorer, find your Client ID (by looking into the data),
• now here you can see all single events and check the timewise position.

[11RS]

Blame: 03bbc10
Yields: <<Do not send QT (queue time) with SC (session control) as Measurement … Protocol gets confused>>
Now I have locally reverted this change and ran som test - the issue was fixed with this revert and I could not see anything like "Protocol gets confused".
@damieng : would you have a short comment on this?

[damieng]

At the time it caused all sorts of issues. I guess that has been subsequently resolved.

This project however is no longer actively maintained so you may want to fork and apply your fix there.

[11RS]

Thanks for the infomation - and for all your work on this project.