WO2008095018A2 - Page grouping for site traffic analysis reports - Google Patents

Page grouping for site traffic analysis reports Download PDF

Info

Publication number
WO2008095018A2
WO2008095018A2 PCT/US2008/052490 US2008052490W WO2008095018A2 WO 2008095018 A2 WO2008095018 A2 WO 2008095018A2 US 2008052490 W US2008052490 W US 2008052490W WO 2008095018 A2 WO2008095018 A2 WO 2008095018A2
Authority
WO
WIPO (PCT)
Prior art keywords
page
node
group
page group
report
Prior art date
Application number
PCT/US2008/052490
Other languages
French (fr)
Other versions
WO2008095018A3 (en
Inventor
Christopher Reid Error
Brett Error
Original Assignee
Omniture, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US88746807P priority Critical
Priority to US60/887,468 priority
Application filed by Omniture, Inc. filed Critical Omniture, Inc.
Publication of WO2008095018A2 publication Critical patent/WO2008095018A2/en
Publication of WO2008095018A3 publication Critical patent/WO2008095018A3/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/02Marketing, e.g. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards; Price estimation or determination
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0893Assignment of logical groupings to network elements; Policy based network management or configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/22Tracking the activity of the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/36Network-specific arrangements or communication protocols supporting networked applications involving the display of network or application conditions affecting the network application to the application user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/22Arrangements for maintenance or administration or management of packet switching networks using GUI [Graphical User Interface]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/02Arrangements for monitoring or testing packet switching networks involving a reduction of monitoring data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/04Processing of captured monitoring data
    • H04L43/045Processing of captured monitoring data for graphical visualization of monitoring data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/06Report generation

Abstract

Website administrators can specify page groups and/or single pages as checkpoint nodes for site analysis reporting purposes, and can configure the system of the invention to provide information as to a particular visitation path through the checkpoints. Any group of pages can be designed as a single checkpoint node for website traffic analysis and reporting purposes. Page groups can be used in place of or in addition to individual web pages in any context where site traffic analysis is being presented or performed.

Description

PAGE GROUPING FOR SITE TRAFFIC ANALYSIS REPORTS

Inventors:

Christopher Reid Error

Brett Error

Cross-Reference to Related Applications

[0001 ] The present patent application claims priority from U.S. Provisional Patent Application Serial No. 60/887,468, filed January 31, 2007, for "Site Analysis Report", which is incorporated herein by reference.

Field of the Invention

[0002] The present invention is related to website traffic analysis reports, and more particularly to techniques for grouping pages in such reports.

Description of the Background Art

[0003] Website providers often wish to collect data that describes usage and visitation patterns for their websites and for individual web pages within the sites. Such information can be extremely valuable in developing usage statistics for various purposes, including for example estimating server load, determining advertising rates, identifying areas of websites that are in need of redesign, and the like.

[0004] When surfing the Web using a browser such as Internet Explorer (available from Microsoft Corporation of Redmond, Washington), users have the ability to move from one page to another by various means, such as: clicking on links within pages; typing in Uniform Resource Locators (URLs); clicking on dedicated buttons in the browser (such as Back, Forward, and Home); or selecting from a list of favorites. In addition, users can open and close new browser windows at will. As users of web browsers have grown more sophisticated over the years, they have become increasingly adept at such navigation. Furthermore, as connection speeds have increased, users have become less hesitant to click on links at will, and then back up if the information presented by the link is not of interest or is of merely momentary interest.

[0005] As a result, users often take a somewhat wandering approach through pages of a website, including side trips and tangents. The user eventually reaches the end of a theoretically linear path of pages, but may have visited some tangential pages along the way. Such tangential pages may be part of the same web domain as the linear path, or they may be external to that domain.

[0006] For example, in performing a somewhat linear task such as purchasing an item from an online retailer, there are a series of steps that are generally represented by web pages: searching for the desired item; selecting the item by putting it in a shopping cart; activating a checkout function; providing shipping and billing information; and indicating final approval. However, along the way, the user may visit some tangential pages. For example, he or she may check the shipping costs on item; or he or she may check the price of the item at a competitor's page; or he or she may, for whatever reason, check the weather forecast. The linear path of pages is eventually visited, in a discernable sequence; these tangential pages are merely momentary distractions along the way.

[0007] In many contexts, website administrators are interested in analyzing the site visitation paths of users of their websites. Visitation to the tangential pages may be of little or no interest to such administrators; alternatively, administrators may be interested in certain tangents but not others. [0008] Furthermore, it is often the case that several web pages are similar to one another in form, function, and/ or content, so that a website administrator would be interested in treating such web pages as part of a group for the purposes of website traffic analysis reports. Thus, for such purposes, it would be beneficial to have a mechanism that allows a website administrator to specify that a visit to any one of the pages in such a group should be treated as equivalent to a visit to any other page in the group. [0009] What is needed, therefore, is a system that allows website administrators to specify page groups for site analysis reporting purposes. What is further needed is a system that allows website administrators to edit, delete, and manage previously specified page groups. What is further needed is a system that generates site traffic analysis reports wherein at least one node represents a group of pages rather than a single page.

Summary of the Invention

[0010] The present invention allows website administrators to specify page groups for site analysis reporting purposes. Website administrators are able to specify single pages and/ or page groups as checkpoint nodes, and can configure the system of the invention to provide information as to a particular visitation path through the checkpoints. The system then presents usage statistics for the specified visitation path. According to the techniques of the present invention, the system is able to recognize a visitation path among checkpoints, regardless of whether the user visits other nodes in the course of the checkpoint traversal. Thus, even if a user takes "side trips" through other web pages that are not designated as checkpoints, the present invention is able to provide meaningful site path analysis with respect to those nodes that are designated as checkpoints. Thus, the present invention can be used to specify any group of pages as a single checkpoint node for website traffic analysis and reporting purposes.

[0011 ] Page groups can be used in place of or in addition to individual web pages in any context where site traffic analysis is being presented or performed. Website administrators can specify any number of page groups, and can manage such page groups as needed or desired. Thus, website administrators can name page groups, add or delete pages from them, and configure the manner in which page groups are displayed in site analysis reports. Brief Description of the Drawings

[0012] Fig. 1 is a block diagram depicting a system for website traffic data collection.

[0013] Fig. 2 is a flowchart depicting a method of specifying a group of pages for a website traffic analysis system according to one embodiment of the present invention.

[0014] Fig. 3 depicts a user interface for presenting a fall-out report for a website traffic analysis system.

[0015] Fig. 4 depicts a user interface for presenting a fall-out report for a website traffic analysis system after a page has been added as a checkpoint node.

[0016] Fig. 5 depicts a user interface for specifying a page group for a website traffic analysis system according to one embodiment of the present invention.

[0017] Fig. 6 depicts a user interface for editing information associated with a page group according to one embodiment of the present invention. [0018] Fig. 7 depicts a user interface for presenting a fall-out report for a website traffic analysis system, including a page group as a checkpoint node, according to one embodiment of the present invention. [0019] Fig. 8 depicts a pop-up menu for accessing a screen for editing information associated with a previously created page group according to one embodiment of the present invention.

[0020] Fig. 9 depicts a user interface for presenting a site analysis report for a website traffic analysis system, including a page group as a node, according to one embodiment of the present invention. [0021 ] The Figures depict a preferred embodiment of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein. Detailed Description

[0022] The following description and accompanying figures are merely illustrative of the techniques of the invention. One skilled in the art will recognize that the techniques of the invention can be implemented in other ways and in other contexts wherein it is desirable to capture and analyze sequential relationships among nodes. In addition, the particular layout and appearance of the screen shots and reports provided herein are intended to be exemplary. [0023] Referring now to Fig. 1, there is shown an example of a system

100 for website traffic data collection. User 112 interacts with client machine 107, which runs a software application such as browser 110 for accessing and displaying web pages. In response to a user 112 command such as clicking on a link or typing in a URL, client machine 107 issues a web page request 111 that is transmitted via the Internet to content server 101. In response to request 111, content server 101 transmits HTML code 102 to client machine 107. Browser 110 interprets received HTML code 102 to display the requested web page on client machine 107.

[0024] Client machine 107 also transmits web page visitation tracking information 105 to a tracking server 106, which is typically a separate server operated by a third-party website traffic statistic service. Tracking information 105 typically includes a user identifier, as well information describing the pages visited and the dates and times of the visits. Tracking information 105 can be transmitted from client 107 to tracking server 106 according to well- known techniques. For example, one well-known technique is to embed a pointer to a resource, known as a "web bug," in HTML code 102. The resource is typically invisible to the user, such as a transparent one-pixel image. The pointer directs machine 107 to request the resource from tracking server 106. Tracking server 106 records the request in a log 108, and records additional information associated with the request (such as the date and time, and possibly some identifying information that may be encoded in the resource request). Thus, tracking server 106 records the occurrence of a "hit" to the web page. Tracking server 106 also transmits the requests one-pixel image 109 to client machine 107 so that the resource request is satisfied. [0025] Site path analysis module 113 retrieves stored tracking data from log 108, filters the data, and outputs reports 114 to a web administrator 115. Reports 114 may be provided in hard copy, or via a display screen (not shown), or by some other means. Administrator 115 can request particular types of reports, and can configure the filtering, analysis, and output operations via user interface 116, as will be described in more detail below. Reports 114 include, for example, overviews and statistical analyses describing the relative frequency with which various site paths are being followed through the website. Examples of such reports are described below. [0026] Module 113 and user interface 116 may be implemented in software running on server 106 or on another computer that can access log 108. In one embodiment, the present invention is implemented primarily within module 113 and user interface 116.

[0027] Referring now to Fig. 3, there is shown an example of a fall-out report 300 for a website traffic analysis system. A fall-out report 300 is designed to show how website visitors tend to navigate through a website. Various checkpoints can be defined, as described in related U.S. Utility Patent Application Serial No. 10/609,008, filed June 27, 2003, for "Capturing and Presenting Site Visitation Path Data", which is incorporated herein by reference. Fall-out report 300 provides a visual indication of the number of users that follow the specified path of checkpoints. As described in related U.S. Utility Patent Application Serial No. 10/609,008, additional pages may be visited along the path; if those pages are not designated as checkpoints, they are ignored for purposes of the fall-out report 300.

[0028] In the example of Fig. 3, three checkpoints 301A, 301B, 301C have been defined. Each checkpoint 301 corresponds to a web page within the website that is being analyzed. For each checkpoint 301, the following information is displayed: • a label 302;

• a number of visits 303 that have followed the defined path up to the current checkpoint 301;

• of the total number of visits to the first checkpoint on the path, a percentage 304 of visits that have remained on the path up to and including the current checkpoint 301; and

• a graphical indication 305 of the relative number of visits that have remained on the path up to and including the current checkpoint 301.

[0029] For each checkpoint 301 after the first checkpoint, the following information is displayed:

• of the total number of visits to the previous checkpoint node on the path, a percentage 306 of visits that proceeded to the current checkpoint 301;

• of the total number of visits to the previous checkpoint node on the path, a percentage 307 of visits that did not proceed to the current checkpoint 301 (i.e., that were "lost"); and

• of those visits that were lost, an indication 308 of where the website visitor went after visiting the previous checkpoint node on the path

[0030] Other information can also be shown in the fall-out report 300.

One skilled in the art will recognize that the example shows a particular layout for such a report, but that many other layouts are possible. [0031 ] The report 300 of Fig. 3 shows information for a checkpoint path including a home page 301A, an "Add product to cart" page 301B, and a "Buy process - Order confirmation" page 301C. If the website includes various category pages, each showing a product category, a site administrator may wish to see how visits to these category pages may affect site traversal statistics. Accordingly, the administrator may wish to add a category page to the checkpoint path of Fig. 3. Referring now to Fig. 4, there is shown an example of fall-out report 300 after the administrator has added a "Category: Electronics" checkpoint 301D between checkpoints 301A and 301B. Fig. 4 also shows a checkpoint selector 401 interface that provides a list 402 of checkpoints that can be dragged onto the desired location within report 300. The administrator can also type a search query in field 403 to filter the list 402 of checkpoints. Fig. 4 also shows a list 404 of checkpoint groups, which will be described in more detail below.

[0032] In some cases, the administrator may be interested in the effect, on site traversal statistics, of other pages similar to the "Category: Electronics" page. If desired, the administrator can add corresponding checkpoints to fallout report 300, and can see the effect of such checkpoints on report 300. For example, a "Category: Gaming" checkpoint (not shown) could be added just below or above the "Category: Electronics" checkpoint 301D, so that the report would show statistics for a traversal path including both the "Category: Electronics" page and the "Category: Gaming" page in whatever order is specified.

[0033] The present invention also allows the administrator to generate a report for a traversal path that includes a visit to either the "Category: Gaming" page or the "Category: Electronics" page, without requiring a visit to both of these pages. To do so, the administrator creates a page group. The page group includes both of the pages, and acts as a single node, or checkpoint, within the fall-out report. The administrator can then create a target path including the checkpoint representing the page group. A visit to any page in the group will satisfy the conditions for the checkpoint, and will be considered a visit to the checkpoint for reporting purposes. The administrator can give the group a name, can add or remove pages from the group, and can perform other editing operations on the group, as shown below. [0034] Referring now to Fig. 2, there is shown a flowchart depicting a method for specifying a group of pages for a website traffic analysis system according to one embodiment of the present invention. In one embodiment, the steps of Fig. 2 are performed by site path analysis module 113 in the process of generating site path reports 114. Module 113 receives 201 input from administrator 115 or from another individual, specifying that two or more pages should be considered part of a group for purposes of a site path report 114. Additional information for the page group can be received 202, including a name for the group, search parameters, and the like, as will be described in more detail below. Once the information for the page group has been provided, the site path report 114 is displayed 203. As shown in the examples discussed below, the report 114 includes at least one node that represents a page group as specified by the administrator in step 201. The report 114 displayed in step 203 can be any type of website traffic analysis report, including for example a fall-out report, a site analysis report, or the like. [0035] Referring now to Fig. 5, there is shown a user interface for specifying a page group for a website traffic analysis system according to one embodiment of the present invention. In one embodiment, the administrator specifies a page group by dragging a checkpoint 501 from checkpoint list 402. Checkpoint list 402 is shown in Fig. 5 as part of checkpoint selector 401. List 402 includes all available checkpoints, or it can be filtered by entering a search query in field 403. The user drags the desired checkpoint 501 onto checkpoint 301B to create a group including the checkpoint 501 being dragged and the checkpoint 301B at the location where the user completes the dragging operation. Similarly, the administrator can add a page to an existing page group by dragging a checkpoint 501 from checkpoint list 402 onto an existing page group in report 300.

[0036] In the example of Fig. 5, the administrator has dragged the

"Category: Gaming" checkpoint 501 from list 402 onto "Category: Electronics" checkpoint 301B, thus initiating the process of creating a new page group including both the "Category: Gaming" page and the "Category: Electronics" page. [0037] In one embodiment, when a new page group is created, the administrator is given an opportunity to specify a name and additional information for the page group. Referring now to Fig. 6, there is shown a group editor dialog box 600 that appears when a new page group is created, according to one embodiment. In other embodiments, dialog box 600 is not presented automatically upon creation of a new group, but may be activated by the administrator when desired. Thus, the new group is given a default name that can be edited later if desired. The administrator can also activate dialog box 600 by initiating a command, for example via an on-screen menu or keyboard shortcut.

[0038] Group editor dialog box 600 includes a field 601 for entering a name for the group; in the example of Fig. 6, the administrator has entered the name "Technical Category" for the newly created group. Dialog box 600 also includes a list 602 of pages currently in the group. As shown in the example of Fig. 6, list 602 includes the "Category: Electronics" page and the "Category: Gaming" page. List 603 includes available pages that can be added to the group. The administrator can enter a search query in field 604 to filter list 603. The administrator can select a page from list 603 and click on button 605 to add the selected page to the group; the selected page is then added to list 602. The administrator can select a page from list 602 and click on button 606 to remove the selected page from the group; the selected page is then removed from list 602.

[0039] The administrator clicks OK button 607 to accept the changes to the group and dismiss dialog box 600. Alternatively, the administrator can click Cancel button 608 to dismiss dialog box 600 without making the specified changes to the group.

[0040] Referring now to Fig. 7, there is shown fall-out report 300 after the page group has been created. Now, the page group is shown as checkpoint node 701, with a special icon 702 indicating that it is a group rather than a single page. For purposes of report 300 as shown in Fig. 7, any visit to a page within the Technical Category group is considered equivalent. For example, the statistic showing 34,398 visits for the path including the Electronics Plus home page 301A and the Technical Category group 701 includes those website visitors that visited any page within the Technical Category group after visiting the Electronics Plus home page. The Technical Category group also appears as an item 703 in group list 404, allowing the user to access this group in the future, for example to drag it to a new report or to edit it. [0041 ] The administrator can right-click on group 701 within report 300 to perform actions on group 701, for example to remove it from report 300 or to edit the group. In one embodiment, a pop-up menu appears when the administrator right-clicks on group 701 within report 300. Referring now to Fig. 8, there is shown an example of a pop-up menu 800 for accessing a screen for editing information associated with a previously created page group according to one embodiment of the present invention. The administrator can select Remove 802 to remove group 701 from report 300. The administrator can select Edit 803 to access dialog box 600 as shown in Fig. 6 to perform other operations on group 701.

[0042] In one embodiment, visits to multiple pages within a page group are considered a single visit for statistical purposes. In another embodiment, each visit to a page within the group is counted separately. [0043] The above examples show the operation of the present invention in the context of a fall-out report. However, one skilled in the art will recognize that the page grouping techniques described herein can be used for any report where nodes or checkpoints representing web pages are shown. In application to such alternative contexts, the present invention allows any node within such a report to represent a single web page or a page group that can be defined by an administrator. Referring now to Fig. 9, there is shown an example of a site analysis report 900 for a website traffic analysis system, including a page group 901 as a node, according to one embodiment of the present invention. Page group 901 is shown along with other nodes 902 representing individual pages. The administrator can specify page groups 901 in the context of site analysis report 900 in a manner similar to that described above for the fall-out report 300, for example by dropping one node 902 onto another node 902 or onto a page group 901, and/ or by right-clicking on a page group 901 to access a group editor dialog box 600.

[0044] In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the invention.

[0045] Reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment.

[0046] Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self -consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. [0047] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system's memories or registers or other such information storage, transmission or display devices.

[0048] The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

[0049] The algorithms and displays presented herein are not inherently related to any particular computer, network of computers, or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the required method steps. The required structure for a variety of these systems appears from the description. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.

[0050] As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, the particular architectures depicted above are merely exemplary of one implementation of the present invention. The functional elements and method steps described above are provided as illustrative examples of one technique for implementing the invention; one skilled in the art will recognize that many other implementations are possible without departing from the present invention as recited in the claims. Likewise, the particular capitalization or naming of the modules, protocols, features, attributes, or any other aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names or formats. In addition, the present invention may be implemented as a method, process, user interface, computer program product, system, apparatus, or any combination thereof. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

Claims

Claims[0051 ] What is claimed is:
1. A method for displaying a website traffic analysis report, compris- ing: receiving input specifying at least one page group, each page group comprising at least two pages; generating a website traffic analysis report comprising at least one node representing a page group, wherein each node repre- senting a page group indicates aggregate visitation statistics for the pages in the page group; and displaying the generated website traffic analysis report.
2. The method of claim 1, wherein generating a website traffic analysis report comprises generating a report indicating a quantity of website visitors traversing a path from a first node to a second node, wherein at least one of the nodes comprises a page group.
3. The method of claim 1, wherein generating a website traffic analysis report comprises generating a report indicating a quantity of website visitors traversing a path from a page belonging to a page group represented by a first node to a page belonging to a page group represented by a second node.
4. The method of claim 1, further comprising: receiving input representing a change to a page group; changing the composition of the page group responsive to the received input.
5. The method of claim 1, further comprising: receiving input specifying a name for a page group; and wherein generating the website traffic analysis report comprises generating a report identifying the page group by the specified name.
6. The method of claim 1, wherein the generated website traffic analy- sis report comprises at least one node representing a single page.
7. The method of claim 1, wherein receiving input specifying at least one page group comprises receiving input dragging a representation of a first page onto a representation of a second page to specify a page group compris- ing the first and second pages.
8. A method for capturing and presenting node sequence data, wherein a plurality of nodes are designated as checkpoints and a plurality of nodes are not designated as checkpoints, the method comprising: receiving input designating a target path comprising a sequence of checkpoint nodes, wherein at least one of the checkpoint nodes represents a group of pages; retrieving, from a stored log, a plurality of records comprising node sequence data; filtering the retrieved records to identify records corresponding to node sequences that include: 1) for each checkpoint node of the target path that represents a group of pages, at least one page of the group; and 2) for each checkpoint node of the target path that represents a single page, the page; at least one of the identified records further including at least one node not designated as a checkpoint; and outputting a report based on the identified records.
9. The method of claim 8, wherein the node sequence data comprises website visitation path data.
10. The method of claim 9, further comprising, prior to retrieving the plurality of records: monitoring web page visits; and storing, in the log, records representing the monitored web page visits.
11. The method of claim 8, wherein outputting the report comprises outputting a report indicating relative frequencies of occurrence of node se- quences.
12. A system for displaying a website traffic analysis report, compris- ing: an input device, for receiving input specifying at least one page group, each page group comprising at least two pages; a path analysis module, coupled to the input device, for generating a website traffic analysis report comprising at least one node representing a page group, wherein each node representing a page group indicates aggregate visitation statistics for the pages in the page group; and a display device, coupled to the path analysis module, for displaying the generated website traffic analysis report.
13. The system of claim 12, wherein the site path analysis module gen- erates a report indicating a quantity of website visitors traversing a path from a first node to a second node, wherein at least one of the nodes comprises a page group.
14. The system of claim 12, wherein the site path analysis module gen- erates a report indicating a quantity of website visitors traversing a path from a page belonging to a page group represented by a first node to a page be- longing to a page group represented by a second node.
15. A system for capturing and presenting node sequence data, wherein a plurality of nodes are designated as checkpoints and a plurality of nodes are not designated as checkpoints, the system comprising: a log, for storing a plurality of records comprising node sequence data; an input device, for receiving input designating a target path compris- ing a sequence of checkpoint nodes, wherein at least one of the checkpoint nodes represents a group of pages; a path analysis module, coupled to the log and to the input device, for retrieving records from the log and for filtering the retrieved records to identify records corresponding to node sequences that include: 1) for each checkpoint node of the target path that represents a group of pages, at least one page of the group; and 2) for each checkpoint node of the target path that represents a single page, the page; at least one of the identified records further including at least one node not designated as a checkpoint; and an output device, coupled to the path analysis module, for outputting a report based on the identified records.
16. The system of claim 15, wherein the node sequence data comprises website visitation path data.
17. The system of claim 16, further comprising: a tracking server, coupled to the log, for monitoring web page visits and for transmitting a signal to the log to store records repre- senting the monitored web page visits.
18. The system of claim 15, wherein the output device outputs a report indicating relative frequencies of occurrence of node sequences.
19. A computer program product for displaying a website traffic analysis report, comprising: a computer-readable storage medium; and computer program code, encoded on the medium, for: receiving input specifying at least one page group, each page group comprising at least two pages; generating a website traffic analysis report comprising at least one node representing a page group, wherein each node representing a page group indicates aggregate visitation statistics for the pages in the page group; and displaying the generated website traffic analysis report.
20. The computer program product of claim 19, wherein the computer program code for generating a website traffic analysis report comprises com- puter program code for generating a report indicating a quantity of website visitors traversing a path from a first node to a second node, wherein at least one of the nodes comprises a page group.
21. The computer program product of claim 19, wherein the computer program code for generating a website traffic analysis report comprises com- puter program code for generating a report indicating a quantity of website visitors traversing a path from a page belonging to a page group represented by a first node to a page belonging to a page group represented by a second node.
22. The computer program product of claim 19, further comprising computer program code for: receiving input representing a change to a page group; changing the composition of the page group responsive to the received input.
23. The computer program product of claim 19, further comprising computer program code for: receiving input specifying a name for a page group; and wherein generating the website traffic analysis report comprises generating a report identifying the page group by the specified name.
24. The computer program product of claim 19, wherein the generated website traffic analysis report comprises at least one node representing a sin- gle page.
25. The computer program product of claim 19, wherein the computer program code for receiving input specifying at least one page group com- prises computer program code for receiving input dragging a representation of a first page onto a representation of a second page to specify a page group comprising the first and second pages.
PCT/US2008/052490 2007-01-31 2008-01-30 Page grouping for site traffic analysis reports WO2008095018A2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US88746807P true 2007-01-31 2007-01-31
US60/887,468 2007-01-31

Publications (2)

Publication Number Publication Date
WO2008095018A2 true WO2008095018A2 (en) 2008-08-07
WO2008095018A3 WO2008095018A3 (en) 2008-09-25

Family

ID=39674774

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2008/052490 WO2008095018A2 (en) 2007-01-31 2008-01-30 Page grouping for site traffic analysis reports

Country Status (1)

Country Link
WO (1) WO2008095018A2 (en)

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104102636A (en) * 2013-04-02 2014-10-15 阿里巴巴集团控股有限公司 Method and device for counting and presenting page data
US8893294B1 (en) 2014-01-21 2014-11-18 Shape Security, Inc. Flexible caching
US8892687B1 (en) 2013-12-06 2014-11-18 Shape Security, Inc. Client/server security by an intermediary rendering modified in-memory objects
US8954583B1 (en) 2014-01-20 2015-02-10 Shape Security, Inc. Intercepting and supervising calls to transformed operations and objects
US9027142B1 (en) 2014-01-21 2015-05-05 Shape Security, Inc. Dynamic field re-rendering
US9083739B1 (en) 2014-05-29 2015-07-14 Shape Security, Inc. Client/server authentication using dynamic credentials
US9210171B1 (en) 2014-05-29 2015-12-08 Shape Security, Inc. Selectively protecting valid links to pages of a web site
US9225737B2 (en) 2013-03-15 2015-12-29 Shape Security, Inc. Detecting the introduction of alien content
US9225729B1 (en) 2014-01-21 2015-12-29 Shape Security, Inc. Blind hash compression
US9258274B2 (en) 2014-07-09 2016-02-09 Shape Security, Inc. Using individualized APIs to block automated attacks on native apps and/or purposely exposed APIs
US9405910B2 (en) 2014-06-02 2016-08-02 Shape Security, Inc. Automatic library detection
US9411958B2 (en) 2014-05-23 2016-08-09 Shape Security, Inc. Polymorphic treatment of data entered at clients
US9438625B1 (en) 2014-09-09 2016-09-06 Shape Security, Inc. Mitigating scripted attacks using dynamic polymorphism
US9479526B1 (en) 2014-11-13 2016-10-25 Shape Security, Inc. Dynamic comparative analysis method and apparatus for detecting and preventing code injection and other network attacks
US9479529B2 (en) 2014-07-22 2016-10-25 Shape Security, Inc. Polymorphic security policy action
US9544329B2 (en) 2014-03-18 2017-01-10 Shape Security, Inc. Client/server security by an intermediary executing instructions received from a server and rendering client application instructions
US9608975B2 (en) 2015-03-30 2017-03-28 Shape Security, Inc. Challenge-dynamic credential pairs for client/server request validation
US9729506B2 (en) 2014-08-22 2017-08-08 Shape Security, Inc. Application programming interface wall
US9858440B1 (en) 2014-05-23 2018-01-02 Shape Security, Inc. Encoding of sensitive data
US9917850B2 (en) 2016-03-03 2018-03-13 Shape Security, Inc. Deterministic reproduction of client/server computer state or output sent to one or more client computers
US9954893B1 (en) 2014-09-23 2018-04-24 Shape Security, Inc. Techniques for combating man-in-the-browser attacks
US9986058B2 (en) 2015-05-21 2018-05-29 Shape Security, Inc. Security systems for mitigating attacks from a headless browser executing on a client computer
US10050935B2 (en) 2014-07-09 2018-08-14 Shape Security, Inc. Using individualized APIs to block automated attacks on native apps and/or purposely exposed APIs with forced user interaction
US10129289B1 (en) 2016-03-11 2018-11-13 Shape Security, Inc. Mitigating attacks on server computers by enforcing platform policies on client computers
US10187408B1 (en) 2014-04-17 2019-01-22 Shape Security, Inc. Detecting attacks against a server computer based on characterizing user interactions with the client computing device
US10212130B1 (en) 2015-11-16 2019-02-19 Shape Security, Inc. Browser extension firewall
US10230718B2 (en) 2015-07-07 2019-03-12 Shape Security, Inc. Split serving of computer code
US10298599B1 (en) 2014-09-19 2019-05-21 Shape Security, Inc. Systems for detecting a headless browser executing on a client computer
US10326790B2 (en) 2016-02-12 2019-06-18 Shape Security, Inc. Reverse proxy computer: deploying countermeasures in response to detecting an autonomous browser executing on a client computer
US10375026B2 (en) 2015-10-28 2019-08-06 Shape Security, Inc. Web transaction status tracking

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020070953A1 (en) * 2000-05-04 2002-06-13 Barg Timothy A. Systems and methods for visualizing and analyzing conditioned data
US20060149728A1 (en) * 2002-06-28 2006-07-06 Brett Error Capturing and presenting site visitation path data

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020070953A1 (en) * 2000-05-04 2002-06-13 Barg Timothy A. Systems and methods for visualizing and analyzing conditioned data
US20060149728A1 (en) * 2002-06-28 2006-07-06 Brett Error Capturing and presenting site visitation path data

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CASTILLO: 'Effective web crawling' PHD THESIS SUBMITTED TO THE UNIVERSITY OF CHILE, DEPT. OF COMPUTER SCIENCE, [Online] Retrieved from the Internet: <URL:http://www.webir.org/resources/phd/Castillo_2004.pdf> *

Cited By (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9973519B2 (en) 2013-03-15 2018-05-15 Shape Security, Inc. Protecting a server computer by detecting the identity of a browser on a client computer
US9609006B2 (en) 2013-03-15 2017-03-28 Shape Security, Inc. Detecting the introduction of alien content
US9225737B2 (en) 2013-03-15 2015-12-29 Shape Security, Inc. Detecting the introduction of alien content
CN104102636A (en) * 2013-04-02 2014-10-15 阿里巴巴集团控股有限公司 Method and device for counting and presenting page data
US9270647B2 (en) 2013-12-06 2016-02-23 Shape Security, Inc. Client/server security by an intermediary rendering modified in-memory objects
US8892687B1 (en) 2013-12-06 2014-11-18 Shape Security, Inc. Client/server security by an intermediary rendering modified in-memory objects
US10027628B2 (en) 2013-12-06 2018-07-17 Shape Security, Inc. Client/server security by an intermediary rendering modified in-memory objects
US8954583B1 (en) 2014-01-20 2015-02-10 Shape Security, Inc. Intercepting and supervising calls to transformed operations and objects
US9584534B1 (en) 2014-01-21 2017-02-28 Shape Security, Inc. Dynamic field re-rendering
US9225729B1 (en) 2014-01-21 2015-12-29 Shape Security, Inc. Blind hash compression
US9027142B1 (en) 2014-01-21 2015-05-05 Shape Security, Inc. Dynamic field re-rendering
US9405851B1 (en) 2014-01-21 2016-08-02 Shape Security, Inc. Flexible caching
US8893294B1 (en) 2014-01-21 2014-11-18 Shape Security, Inc. Flexible caching
US10212137B1 (en) 2014-01-21 2019-02-19 Shape Security, Inc. Blind hash compression
US9544329B2 (en) 2014-03-18 2017-01-10 Shape Security, Inc. Client/server security by an intermediary executing instructions received from a server and rendering client application instructions
US10187408B1 (en) 2014-04-17 2019-01-22 Shape Security, Inc. Detecting attacks against a server computer based on characterizing user interactions with the client computing device
US9411958B2 (en) 2014-05-23 2016-08-09 Shape Security, Inc. Polymorphic treatment of data entered at clients
US9858440B1 (en) 2014-05-23 2018-01-02 Shape Security, Inc. Encoding of sensitive data
US9621583B2 (en) 2014-05-29 2017-04-11 Shape Security, Inc. Selectively protecting valid links to pages of a web site
US9083739B1 (en) 2014-05-29 2015-07-14 Shape Security, Inc. Client/server authentication using dynamic credentials
US9716702B2 (en) 2014-05-29 2017-07-25 Shape Security, Inc. Management of dynamic credentials
US9210171B1 (en) 2014-05-29 2015-12-08 Shape Security, Inc. Selectively protecting valid links to pages of a web site
US9405910B2 (en) 2014-06-02 2016-08-02 Shape Security, Inc. Automatic library detection
US10050935B2 (en) 2014-07-09 2018-08-14 Shape Security, Inc. Using individualized APIs to block automated attacks on native apps and/or purposely exposed APIs with forced user interaction
US9258274B2 (en) 2014-07-09 2016-02-09 Shape Security, Inc. Using individualized APIs to block automated attacks on native apps and/or purposely exposed APIs
US9479529B2 (en) 2014-07-22 2016-10-25 Shape Security, Inc. Polymorphic security policy action
US9729506B2 (en) 2014-08-22 2017-08-08 Shape Security, Inc. Application programming interface wall
US9438625B1 (en) 2014-09-09 2016-09-06 Shape Security, Inc. Mitigating scripted attacks using dynamic polymorphism
US10298599B1 (en) 2014-09-19 2019-05-21 Shape Security, Inc. Systems for detecting a headless browser executing on a client computer
US9954893B1 (en) 2014-09-23 2018-04-24 Shape Security, Inc. Techniques for combating man-in-the-browser attacks
US9479526B1 (en) 2014-11-13 2016-10-25 Shape Security, Inc. Dynamic comparative analysis method and apparatus for detecting and preventing code injection and other network attacks
US9608975B2 (en) 2015-03-30 2017-03-28 Shape Security, Inc. Challenge-dynamic credential pairs for client/server request validation
US10367903B2 (en) 2015-05-21 2019-07-30 Shape Security, Inc. Security systems for mitigating attacks from a headless browser executing on a client computer
US9986058B2 (en) 2015-05-21 2018-05-29 Shape Security, Inc. Security systems for mitigating attacks from a headless browser executing on a client computer
US10230718B2 (en) 2015-07-07 2019-03-12 Shape Security, Inc. Split serving of computer code
US10375026B2 (en) 2015-10-28 2019-08-06 Shape Security, Inc. Web transaction status tracking
US10212130B1 (en) 2015-11-16 2019-02-19 Shape Security, Inc. Browser extension firewall
US10326790B2 (en) 2016-02-12 2019-06-18 Shape Security, Inc. Reverse proxy computer: deploying countermeasures in response to detecting an autonomous browser executing on a client computer
US9917850B2 (en) 2016-03-03 2018-03-13 Shape Security, Inc. Deterministic reproduction of client/server computer state or output sent to one or more client computers
US10212173B2 (en) 2016-03-03 2019-02-19 Shape Security, Inc. Deterministic reproduction of client/server computer state or output sent to one or more client computers
US10129289B1 (en) 2016-03-11 2018-11-13 Shape Security, Inc. Mitigating attacks on server computers by enforcing platform policies on client computers
US10447726B2 (en) 2016-03-11 2019-10-15 Shape Security, Inc. Mitigating attacks on server computers by enforcing platform policies on client computers

Also Published As

Publication number Publication date
WO2008095018A3 (en) 2008-09-25

Similar Documents

Publication Publication Date Title
US8001105B2 (en) System and method for keyword extraction and contextual advertisement generation
AU2010201642B2 (en) Remote module incorporation into a container document
US8046693B2 (en) Obtaining user feedback on displayed items
US8560964B2 (en) Method and system for predictive browsing
EP1488353B1 (en) Recording user interaction with an application
US8918713B2 (en) Module specification for a module to be incorporated into a container document
US7660815B1 (en) Method and system for occurrence frequency-based scaling of navigation path weights among online content sources
US7953725B2 (en) Method, system, and storage medium for providing web information processing services
US7725530B2 (en) Proxy server collection of data for module incorporation into a container document
US6021416A (en) Dynamic source code capture for a selected region of a display
KR101791623B1 (en) Visualizing realationships between a transaction trace graph and a map of logical subsystems
US7685192B1 (en) Method and system for displaying interest space user communities
US20090198662A1 (en) Techniques for Crawling Dynamic Web Content
US6144962A (en) Visualization of web sites and hierarchical data structures
US8230320B2 (en) Method and system for social bookmarking of resources exposed in web pages that don&#39;t follow the representational state transfer architectural style (REST)
US7877392B2 (en) Centralized web-based software solutions for search engine optimization
US20030046385A1 (en) User-side tracking of multimedia application usage within a web page
US20020026441A1 (en) System and method for integrating multiple applications
US6775675B1 (en) Methods for abstracting data from various data structures and managing the presentation of the data
US6968507B2 (en) Method and apparatus for defeating a mechanism that blocks windows
US9002895B2 (en) Systems and methods for providing modular configurable creative units for delivery via intext advertising
US7673340B1 (en) System and method for analyzing system user behavior
US7516118B1 (en) Methods and systems for assisted network browsing
DE112012000944B4 (en) Web-based editing and web content sharing in real time
EP1428104B9 (en) Method and system for characterization of online behavior

Legal Events

Date Code Title Description
NENP Non-entry into the national phase in:

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08728579

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 08728579

Country of ref document: EP

Kind code of ref document: A2