Right now, real time CrowdLogger events (e.g., searches, clicks, page
loads/focuses/blurs, etc.) are triggered prior to the events being saved to the
logging database. As log IDs are not assigned to events until the actual DB
write, the real time events do not include that ID. This can make it difficult
to line up real time events with their saved counterparts (thought timestamps
are a pretty good surrogate).
It might be useful for CrowdLogger Remote Module (CLRM) developers if
CrowdLogger emitted real time events _after_ they have been logged and include
the ID.
Original issue reported on code.google.com by
hafe...@gmail.comon 15 Apr 2013 at 8:30