Abstract: A collection configuration management system can be used to manage one or more monitoring objects, such as tags, included in one or more content objects. The collection configuration management system can compartmentalize monitoring object configurations into a monitoring object bundle that may be executed as a result of loading the one or more content objects. The monitoring object bundle can be generated to include one or more monitoring objects, as well as monitoring object management loader functionality.

Abstract: Embodiments of the systems described herein can implement one or more visitor stitching processes. Visitor stitching can include, among other things, one or more processes by which multiple visitors that may appear distinctly independent may be merged into a new single united visitor profile due to the leveraging of one or more unique persistent identifiers.

Abstract: Embodiments of the systems described herein can implement one or more processes remotely delivering customized code to a host application and/or computing device. The host application may be configured as an Application Programming Interface with a customized code processing library that may configure the host application to receive further instructions remotely. The host application may be further configured to execute host code and/or third-party code. The host application may be configured to receive remote application logic, after the host application has been installed on a computing device, and to execute the received application logic to alter the behavior of the host application, such as selectively tracking end user interactions.

Abstract: Systems and methods are provided for analysis and selection of attributes used to segment data entities. The attributes used to segment data entities may be analyzed to identify segments of data entities (e.g., distinct audiences of visitors) that share values for a given subset of attributes. By intelligently selecting attributes for use in the segmentation process based on the values that they may take (e.g., the cardinality of the attributes), the selected attributes can be used to generate a reasonable or otherwise desirable number of data entity segments. Other attributes can be excluded from the segmentation process.

Abstract: A tag management system can include features to assist in developing a cross-vendor profile for individual visitors to content pages of a content site. The visitors to the content site can obtain universal identifiers usable by the content site to identify the visitors. The universal identifiers can be included in the content pages by the visitor end user systems so that browser tags that may not have native access to the universal identifier can access the universal identifiers. The universal identifiers may then be provided to tag vendor systems with associated visitor data, thereby enabling the tag vendor systems to provide processed or raw data that can be compared by individual universal identifiers. Using this processed data, the content site can prepare the cross-vendor profile of individual visitors and realize insights that may be unavailable using conventional systems and methods.

Abstract: Embodiments of the systems described herein can implement one or more visitor tearing processes. Visitor tearing can include, among other things, one or more processes by which multiple visitors that may appear to be the same visitor may be separated into different visitor profiles due to the leveraging of one or more unique persistent identifiers.

Abstract: In some embodiments, a system is disclosed for processing event data for an application and transmitting the event data via a computer network. The system can include a memory device and a hardware processor. The memory device can store an application. The hardware processor can execute the application, characterize a user engagement with the application as being a first level of engagement or a second level of engagement, generate event data responsive to user interactions with the application, and control the batch collection of the event data depending on whether the user engagement with the application is characterized as the first level of engagement or the second level of engagement.

Abstract: A collection configuration management system can be used to manage one or more monitoring objects, such as tags, included in one or more content objects. The collection configuration management system can compartmentalize monitoring object configurations into a monitoring object bundle that may be executed as a result of loading the one or more content objects. The monitoring object bundle can be generated to include one or more monitoring objects, as well as monitoring object management loader functionality.

Abstract: In some embodiments, an electronic device is disclosed for intelligently prefetching data via a computer network. The electronic device can include a device housing, a user interface, a memory device, and a hardware processor. The hardware processor can: communicate via a communication network; determine that the hardware processor is expected to be unable to communicate via the communication network; responsive to determining that the hardware processor is expected to be unable to communicate via the communication network, determine prefetch data to request prior to the hardware processor being unable to communicate via the communication network; request the prefetch data; receive and store the prefetch data prior to the hardware processor being unable to communicate via the communication network; and subsequent to the hardware processor being unable to communicate via the communication network, process the prefetch data with an application responsive to processing a first user input with the application.

Abstract: A tag management system can implement a combined synchronous and asynchronous tag-loading scheme. In an embodiment of this scheme, a synchronous tag may be included at the top of or near the top of a content page. This synchronous tag can hide one or more page elements that are to be modified by a subsequent asynchronous personalization tag. Subsequently, the asynchronous personalization tag can update the page element and then cause the page element to be displayed. As a result, flicker between the old and new page elements can be reduced or avoided.

Abstract: Systems and methods described herein can take advantage of the caching abilities of the browser and the idle time of the user to prefetch tag libraries of one or more tags for execution in a subsequent content page. For example, these systems and methods can provide the ability to prefetch and not execute a tag library on a content page before it is required so the tag library is cached in the browser. When the browser hits the page that uses the tag library, the tag library can be quickly retrieved from memory and executed.

Abstract: Style instructions, which may be coded in a style language and not include application logic, can be used to both control presentation of content of a web page by a web browser and control monitoring of interactions with the web page. Selectors in the style instructions, for example, can be used to identify elements of the web page and define styles for the elements. As a result of implementing such style instructions, individuals tasked with design of a web page can more easily and quickly configure monitoring of interactions with the web page.

Abstract: Embodiments of the systems described herein can implement one or more visitor stitching processes. Visitor stitching can include, among other things, one or more processes by which multiple visitors that may appear distinctly independent may be merged into a new single united visitor profile due to the leveraging of one or more unique persistent identifiers.

Abstract: Embodiments of the systems described herein can implement one or more processes remotely delivering customized code to a host application and/or computing device. The host application may be configured as an Application Programming Interface with a customized code processing library that may configure the host application to receive further instructions remotely. The host application may be further configured to execute host code and/or third-party code. The host application may be configured to receive remote application logic, after the host application has been installed on a computing device, and to execute the received application logic to alter the behavior of the host application, such as selectively tracking end user interactions.

Abstract: An improved approach to tracking media playback includes tracking logic that is based on abandonment indicators. An abandonment indicator is detected during media playback, such as a user interaction with a computing device that is detected prior to ceasing playback of the media content. Tracking messages are reduced, suppressed, or suspended until an abandonment indicator is detected. After an abandonment indicator is detected, the system quickens, releases, or restart sending tracking messages to a collection system.

Abstract: A tag management system can include features to assist in developing a cross-vendor profile for individual visitors to content pages of a content site. The visitors to the content site can obtain universal identifiers usable by the content site to identify the visitors. The universal identifiers can be included in the content pages by the visitor end user systems so that browser tags that may not have native access to the universal identifier can access the universal identifiers. The universal identifiers may then be provided to tag vendor systems with associated visitor data, thereby enabling the tag vendor systems to provide processed or raw data that can be compared by individual universal identifiers. Using this processed data, the content site can prepare the cross-vendor profile of individual visitors and realize insights that may be unavailable using conventional systems and methods.

Abstract: The systems and methods described herein use a tag for collecting data associated with a content object of a content page. The tag may be a universal tag which can provide a single point of data collection and thereby reduce the number of network requests due to piggyback tags. The data collected from the content page may be communicated to a stream management system which can process the data and split the data into multiple data streams to be fed to a downstream system. The downstream system can further process the data and communicate to another downstream system. In some embodiments, the stream management system can access the repositories of its downstream system and veto the data flows created by the downstream system.

Abstract: A collection configuration management system can be used to manage one or more monitoring objects, such as tags, included in one or more content objects. The collection configuration management system can compartmentalize monitoring object configurations into a monitoring object bundle that may be executed as a result of loading the one or more content objects. The monitoring object bundle can be generated to include one or more monitoring objects, as well as monitoring object management loader functionality.

Abstract: A tag management system in a computer data network can be used to manage one or more tag configurations with templates. A template may enable efficient tag configuration by causing presentation of an improved user interface that facilitates user-specified mappings between a custom content site and predefined tag management attributes. By completing a template, which may depend on other templates or have templates that depend on it, the tag management system can automatically deploy complex tag management configurations to track end user interactions over a data network.

Abstract: In some embodiments, an electronic device is disclosed for intelligently prefetching data via a computer network. The electronic device can include a device housing, a user interface, a memory device, and a hardware processor. The hardware processor can: communicate via a communication network; determine that the hardware processor is expected to be unable to communicate via the communication network; responsive to determining that the hardware processor is expected to be unable to communicate via the communication network, determine prefetch data to request prior to the hardware processor being unable to communicate via the communication network; request the prefetch data; receive and store the prefetch data prior to the hardware processor being unable to communicate via the communication network; and subsequent to the hardware processor being unable to communicate via the communication network, process the prefetch data with an application responsive to processing a first user input with the application.