Abstract: A seemingly infinite and continuous stream of online content can be tracked by a movement tracker that can track an amount of movement of a stream of content. For example, such a movement tracker can track the amount of movement per session of a client-side application, such as per session of a web browser. In an example, the tracking of the movement can occur by tracking a measurable parameter of the stream that indicates the amount of movement, such as scroll distance. The movement tracker may also be configured to determine user interaction data according to the tracked amount of movement.

Abstract: A system can stream content items and ad items to a user interface of a client-side application (such as a web browser) without refreshing the user interface and by requesting such items from a local cache and/or a remote cache associated with the client-side application or the user interface. The remote cache can operate much like a local cache for the client-side application or the user interface. Items can be streamed to a user interface without refreshing the user interface and by requesting such items from a remote cache dedicated to caching the items that can be presented by the user interface. Because the tracking of such items and the tracking of the interactions with such items creates such large amounts of data, communicating the tracked data may be impracticable without use of a system that can effectively compress associated instrumentation data.

Abstract: A seemingly infinite and continuous stream of online content can be tracked by a movement tracker that can track an amount of movement of a stream of content. For example, such a movement tracker can track the amount of movement per session of a client-side application, such as per session of a web browser. In an example, the tracking of the movement can occur by tracking a measurable parameter of the stream that indicates the amount of movement, such as scroll distance. The movement tracker may also be configured to determine user interaction data according to the tracked amount of movement.

Abstract: A seemingly infinite and continuous stream of online content can be tracked by a movement tracker that can track an amount of movement of a stream of content. For example, such a movement tracker can track the amount of movement per session of a client-side application, such as per session of a web browser. In an example, the tracking of the movement can occur by tracking a measurable parameter of the stream that indicates the amount of movement, such as scroll distance. The movement tracker may also be configured to determine user interaction data according to the tracked amount of movement.

Abstract: A system can stream content items and ad items to a user interface of a client-side application (such as a web browser) without refreshing the user interface and by requesting such items from a local cache and/or a remote cache associated with the client-side application or the user interface. The remote cache can operate much like a local cache for the client-side application or the user interface. Items can be streamed to a user interface without refreshing the user interface and by requesting such items from a remote cache dedicated to caching the items that can be presented by the user interface. Because the tracking of such items and the tracking of the interactions with such items creates such large amounts of data, communicating the tracked data may be impracticable without use of a system that can effectively compress associated instrumentation data.

Abstract: A system can stream content items and ad items to a user interface of a client-side application (such as a web browser) without refreshing the user interface and by requesting such items from a local cache and/or a remote cache associated with the client-side application or the user interface. The remote cache can operate much like a local cache for the client-side application or the user interface. Items can be streamed to a user interface without refreshing the user interface and by requesting such items from a remote cache dedicated to caching the items that can be presented by the user interface. Because the tracking of such items and the tracking of the interactions with such items creates such large amounts of data, communicating the tracked data may be impracticable without use of a system that can effectively compress associated instrumentation data.

Abstract: A system can effectively compress instrumentation data related to a page view on a client-side application thread (such as a web browser thread) and communicate the compressed data over the Internet to a server (such as an analytics server). Leading up to the compression, the system can include data scanning, code building, code encoding, and code serialization. The compression can run on a background thread of the client-side application, so that it does not interfere with other processes run by the client-side application. For example, a web worker can implement the code compression described herein.

Abstract: A system can throttle compression of instrumentation data related to a page view, by throttled scanning processes. Then that data can be communication over the Internet to a server effectively. The scanning of instrumentation data can be performed via batch processing; and therefore, data for compression may be maximized or throttled. The system can also accelerate the various caching options involved with the streaming of content items and ad items. For example, such items can be retrieved by the local and/or remote caches associated with the client-side application and/or the page view, prior to the items being requested by and/or presented to a user, via batch retrieval processes. These batch retrieval processes can also be combined with the batch scanning processes.

Abstract: A system can throttle compression of instrumentation data related to a page view, by throttled scanning processes. Then that data can be communication over the Internet to a server effectively. The scanning of instrumentation data can be performed via batch processing; and therefore, data for compression may be maximized or throttled. The system can also accelerate the various caching options involved with the streaming of content items and ad items. For example, such items can be retrieved by the local and/or remote caches associated with the client-side application and/or the page view, prior to the items being requested by and/or presented to a user, via batch retrieval processes. These batch retrieval processes can also be combined with the batch scanning processes.

Abstract: A system can effectively compress instrumentation data related to a page view on a client-side application thread (such as a web browser thread) and communicate the compressed data over the Internet to a server (such as an analytics server). Leading up to the compression, the system can include data scanning, code building, code encoding, and code serialization. The compression can run on a background thread of the client-side application, so that it does not interfere with other processes run by the client-side application. For example, a web worker can implement the code compression described herein.

Abstract: A system can stream content items and ad items to a user interface of a client-side application (such as a web browser) without refreshing the user interface and by requesting such items from a local cache and/or a remote cache associated with the client-side application or the user interface. The remote cache can operate much like a local cache for the client-side application or the user interface. Items can be streamed to a user interface without refreshing the user interface and by requesting such items from a remote cache dedicated to caching the items that can be presented by the user interface. Because the tracking of such items and the tracking of the interactions with such items creates such large amounts of data, communicating the tracked data may be impracticable without use of a system that can effectively compress associated instrumentation data.

Abstract: A seemingly infinite and continuous stream of online content can be tracked by a movement tracker that can track an amount of movement of a stream of content. For example, such a movement tracker can track the amount of movement per session of a client-side application, such as per session of a web browser. In an example, the tracking of the movement can occur by tracking a measurable parameter of the stream that indicates the amount of movement, such as scroll distance. The movement tracker may also be configured to determine user interaction data according to the tracked amount of movement.

Abstract: Methods and systems for instrumenting a web page to collect information on user actions associated with the web page and any of the elements contained therein are provided. For an element contained in the web page for which user actions are to be instrumented, include a single piece of instrumentation code in the source code of the web page, such that the piece of instrumentation code references the element with a unique element ID. Upon execution of the piece of instrumentation code, a hierarchical data structure representing the web page and the elements contained therein is parsed to determine any additional element(s) contained in the element. Information on one or more user actions associated with the element and the additional element(s) contained therein are transmitted. The piece of instrumentation code may invoke one or more library functions to perform various operations related to the collection of user action information.