To do that, we would need a leave event which is either saved when the user leaves (but an asynchronous request >would be lost much of the time,
Correct
and a synchronous one would decrease site performance),
Correct
or store the event and replay it as soon as the user is on a wiki page again. I guess we can just use localstorage for that
Very well, thank you. The least cookies connected to EL the better.
On Mon, May 19, 2014 at 7:29 AM, Gergo Tisza gtisza@wikimedia.org wrote:
On Fri, May 16, 2014 at 1:10 AM, Nuria Ruiz nuria@wikimedia.org wrote:
So we agree you do not need to use cookies right? Being a single page app you should not need them. As you said you actually do not even need local storage.
Well, the one use case that is not covered by simply reporting everything as soon as it happens is Pau's request to track the time spent in failed conversion steps, from entering the step to closing the window/navigating away. To do that, we would need a leave event which is either saved when the user leaves (but an asynchronous request would be lost much of the time, and a synchronous one would decrease site performance), or store the event and replay it as soon as the user is on a wiki page again. I guess we can just use localstorage for that; with the flow_id multiple tabs is not a problem, and since we only lose the last event when the logging fails, not the whole event chain, we don't have to worry about the results becoming biased by non-localStorage-supporting browsers or infrequent users.
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics