Great idea, but why do we require real-time and user-impacting statistics in the first place?
Why not place a AJAX script to a local session monitor that stores up details about a visit and flushes the results via hits to GA? That way, a user doesn't have to wait for GA to load on a page (I've see it be the majority of load time on many websites). The AJAX script could be tied to all types of events such as mouse movement (people hover over links, images, ect. without clicking so capture that as interactivity), onFocus events, and in future eye-tracking events.
This could be built up as a off-screen buffer that generates a more detailed session and fires it off to AG in near-real-time. One other important factor could be to label the events in a concatenated nomenclature so that home.hover, home.idle.30s, home.unFocus, home.gaze.rightMenu.17s, and home.scroll.down.x143 all make sense.
Why not place a AJAX script to a local session monitor that stores up details about a visit and flushes the results via hits to GA? That way, a user doesn't have to wait for GA to load on a page (I've see it be the majority of load time on many websites). The AJAX script could be tied to all types of events such as mouse movement (people hover over links, images, ect. without clicking so capture that as interactivity), onFocus events, and in future eye-tracking events.
This could be built up as a off-screen buffer that generates a more detailed session and fires it off to AG in near-real-time. One other important factor could be to label the events in a concatenated nomenclature so that home.hover, home.idle.30s, home.unFocus, home.gaze.rightMenu.17s, and home.scroll.down.x143 all make sense.