Abstract: A system displays and filters reports including website vitiation data in response to receiving user input. The system allows users to launch various reports onto a workspace and filter the entire result set by selected criteria. The system allows the user to specify and configure segments while viewing reports, simply by clicking next to the desired criteria within the report alone or in combination with various keyboard functions. Filtered reports can be further adjusted per additional filters and criteria. The results are returned virtually instantaneously, enabling users to analyze the effects of combinations of factors.

Abstract: A system and method for defining a segment for filtering website visitation data is disclosed. The method allows for creation and editing of a segment using various rules. The rules are defined using events and containers, which act as criteria by which the data is filtered. The system displays the segments and allows the user to apply them to stored data.

Abstract: Graphic user interfaces for a web analytic system include new modules for automatic generation of calendar notes, targets and alarms. The calendar module is a program for generation of user interfaces, maintenance of a calendar and display settings for same. In particular, the calendar module 208 allows calendar notes or flags to be added to data provided by the web analytics tool 210. These calendar notes or flags are displayed across all reports output by the web analytics tool 210. The calendar notes or events are particularly advantageous because they are: 1) user specific, but may be shared with others as set by the user, 2) allow the user to remember important dates or events automatically, 3) allow easy and direct comparison of pre/post event data, and the 4) the events can be a period of time in addition to a point in time. The functionality provided by the calendar module 208 will be fully described below in the calendar notes section and in conjunction with the description of FIGS. 4-7D.

Abstract: Node sequence data, such as website visitation records, are filtered, analyzed, and summarized in reports. An administrator can designate particular target paths of interest in terms of a checkpoint node sequence. Node sequences are filtered based on the checkpoint node sequence, without regard to any additional or tangential nodes appearing in the sequences. In addition, node sequences can be specified in terms of specific nodes of interest along with wild cards. Reports depict the relative frequency of occurrence of node sequences using visual indicators such as line thickness and/or color.

Abstract: Overlay reports showing user interaction with web plug-in content are generated. Dimensions of elements within plug-in resources are determined by moving the elements to various locations with an output region and noting changes in overall dimensions of the output region. Once dimensions have been determined, overlay reports are generated including color-coded regions depicting relative levels of interaction.

Abstract: User behavior on a website, including intra-page interactions, are tracked while avoiding the need to transmit each intra-page interaction to the data collection server via a separate request. Client-side code instructs the client to store intra-page interaction data in a local data store such as a cookie file. The client transmits the accumulated data to the data collection server in response to a triggering event. For example, data may be transmitted when a new page is loaded, or when the web browser application crashes or is terminated, or when the client machine is turned off, or at periodic intervals, or in response to any other type of triggering event.

Abstract: Elements on a website are associated with the business success of the website, such as determined by sales or orders. Contribution of the elements to the business success is accomplished by assignment a fraction of the success value to each element using allocation, participation, and/or allocated participation methods. Reports are generated quantifying website element usage, for example by superimposing color shadings or other visual indicia on a representation of a page of the website.

Abstract: A method and system for the efficient customization of website tracking data includes a data collector with a user interface for assigning custom events and attributes to events occurring on a website. The data collector receives custom tracking data from the website in response to the occurrence of an event to be tracked. Customization of tracking data is achieved through the use of an embedded tracking code and associated data collection file. The embedded tracking code is configured to report tracking data customized for the website. The data collection server is configured via a graphical user interface to receive and store the customized tracking data. A configuration string from the data collector is inserted into the data collection file on the web site. In this manner, the data collection server and website is customized to collect customized tracking data efficiently without assistance from others.

Abstract: A client rendering a web page discovers embedded content directing the client to request embedded content from a data collection server. The data collection server performs a cookie handshake by determining whether the request includes a visitor identifier. If a visitor identifier is present, the request data is collected and categorized with the visitor identifier. If the visitor identifier is not present, the data collection server creates a visitor identifier and do not repeat flag and sends these items with a redirection request to the client, thereby establishing a visitor identifier for the redirected contact. Where the client does not accept visitor identifiers, or the visitor identifier otherwise is lost, the data collection server creates a visitor identifier based on the client's address, or some other available data.

Abstract: Node sequence data, such as website visitation records, are filtered, analyzed, and summarized in reports. An administrator can designate particular target paths of interest in terms of a checkpoint node sequence. Node sequences are filtered based on the checkpoint node sequence, without regard to any additional or tangential nodes appearing in the sequences. In addition, node sequences can be specified in terms of specific nodes of interest along with wild cards. Reports depict the relative frequency of occurrence of node sequences using visual indicators such as line thickness and/or color.