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: 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: 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: 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: 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: 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 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: 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 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 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 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: A visitor processing system can include features for providing a fully configurable visitor model. The visitor processing system may also provide the ability to see the results of this visitor model in a real time or near real time. This level of configurability can be beneficial when a goal is to reduce a visitor set to a highly targeted visitor segment. This rich configurability can include the ability to set and manipulate a number of attributes and rules for a visitor. By allowing marketing users to configure attributes regarding their content sites' visitors, the visitor processing system can enable marketing users to obtain real-time (or near real-time) reports on these visitors. These reports can provide a highly desirable capability to filter a live and/or historic stream of visitors on the specified attributes, resulting in precisely targeted reporting on a highly segmented and highly targeted segment of visitors.

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: An Internet-based analysis tool follows, in real-time, the flow of traffic through a website. For every website page requested by a website visitor, the state of the visitor's browser is recorded and data relating to the path visitors take through the website is collected and studied. The state of the visitor's browser path is maintained in a traffic analysis cookie that is passed between a website file server and the visitor browser with every page requested for viewing. The cookie is maintained in a size that can be passed from server to browser and back again without negatively impacting server performance and without negatively impacting browser performance. The data in the cookie can follow the visitor browser through independent file servers, regardless of how the pages of a website might be distributed in storage.

Abstract: An Internet-based analysis tool follows, in real-time, the flow of traffic through a website. For every website page requested by a website visitor, the state of the visitor's browser is recorded and data relating to the path visitors take through the website is collected and studied. The state of the visitor's browser path is maintained in a traffic analysis cookie that is passed between a website file server and the visitor browser with every page requested for viewing. The cookie is maintained in a size that can be passed from server to browser and back again without negatively impacting server performance and without negatively impacting browser performance. The data in the cookie can follow the visitor browser through independent file servers, regardless of how the pages of a website might be distributed in storage.

Abstract: An Internet-based analysis tool follows, in real-time, the flow of traffic through a website. For every website page requested by a website visitor, the state of the visitor's browser is recorded and data relating to the path visitors take through the website is collected and studied. The state of the visitor's browser path is maintained in a traffic analysis cookie that is passed between a website file server and the visitor browser with every page requested for viewing. The cookie is maintained in a size that can be passed from server to browser and back again without negatively impacting server performance and without negatively impacting browser performance. The data in the cookie can follow the visitor browser through independent file servers, regardless of how the pages of a website might be distributed in storage.

Abstract: An Internet-based analysis tool follows, in real-time, the flow of traffic through a website. For every website page requested by a website visitor, the state of the visitor's browser is recorded and data relating to the path visitors take through the website is collected and studied. The state of the visitor's browser path is maintained in a traffic analysis cookie that is passed between a website file server and the visitor browser with every page requested for viewing. The cookie is maintained in a size that can be passed from server to browser and back again without negatively impacting server performance and without negatively impacting browser performance. The data in the cookie can follow the visitor browser through independent file servers, regardless of how the pages of a website might be distributed in storage.

Abstract: An Internet-based analysis tool follows, in real-time, the flow of traffic through a website. For every website page requested by a website visitor, the state of the visitor's browser is recorded and data relating to the path visitors take through the website is collected and studied. The state of the visitor's browser path is maintained in a traffic analysis cookie that is passed between a website file server and the visitor browser with every page requested for viewing. The cookie is maintained in a size that can be passed from server to browser and back again without negatively impacting server performance and without negatively impacting browser performance. The data in the cookie can follow the visitor browser through independent file servers, regardless of how the pages of a website might be distributed in storage.

Abstract: An Internet-based analysis tool follows, in real-time, the flow of traffic through a website. For every website page requested by a website visitor, the state of the visitor's browser is recorded and data relating to the path visitors take through the website is collected and studied. The state of the visitor's browser path is maintained in a traffic analysis cookie that is passed between a website file server and the visitor browser with every page requested for viewing. The cookie is maintained in a size that can be passed from server to browser and back again without negatively impacting server performance and without negatively impacting browser performance. The data in the cookie can follow the visitor browser through independent file servers, regardless of how the pages of a website might be distributed in storage.

Abstract: An Internet-based analysis tool follows, in real-time, the flow of traffic through a website. For every website page requested by a website visitor, the state of the visitor's browser is recorded and data relating to the path visitors take through the website is collected and studied. The state of the visitor's browser path is maintained in a traffic analysis cookie that is passed between a website file server and the visitor browser with every page requested for viewing. The cookie is maintained in a size that can be passed from server to browser and back again without negatively impacting server performance and without negatively impacting browser performance. The data in the cookie can follow the visitor browser through independent file servers, regardless of how the pages of a website might be distributed in storage.