1. Field of the Invention
This invention relates generally to user interfaces for tools relating to queries on data in a database. More particularly, the present invention relates to interfaces for generating segment definitions or filter criteria that can be applied to a data set and used by web analytics tools.
2. Background of the Invention
Web analytics refers to the analysis of data created by website usage. For instance, web analytics can be used to mine visitor traffic data. A variety of visitor traffic data is measured such as what browser is being used, what links on a given web page were selected, whether a product was purchase, etc. There are number of web analytics tools presently available such as Site Catalyst version 11 from Omniture of Orem, Utah. These tools are able to capture data on website usage, and responsive to a user's request, display a variety of different metrics on website usage such as fallout/conversion, A/B testing, etc.
One problem with such existing tools is that typically they require a programmer be involved to generate reports and filter the data into segments that the user is interested in viewing. If a user wants to view the data in a different way by creating or modifying a segment definition, the user must provide an explanation of what is desired to a programmer who in turn translates that explanation into data understandable by the web analytics tool, such as code, rules sets, or the like. In addition to requiring additional communication and interfacing between the programmer and the user, this process is typically time consuming and does not allow the user to change or redefine the segmentation definitions on demand.
Thus, there is a need for an improved method and system for web analytics tools that solves the above shortcomings of the prior art.
The present invention as described herein is a system and method for defining a segment for filtering website visitation data. The method includes displaying a plurality of events and containers as criteria by which the website visitation data may be filtered and a canvas, as defined herein, for defining a segment. Events and containers are typically variables that act as criteria by which the data may be filtered. Events may be any activity that occurs in a users visiting or viewing of web pages, and data criteria that is stored in a data storage. For example, a rule saying “product equals radio” is easy to understand, but the scope of that rule is more difficult. Do you want only orders where product equals radio, do you want the entire visit where product was radio, or do you want all pages seen—i.e. the visitor—by anyone who ever saw a radio. Containers may be any criteria for bounding the rule or may act as a node in a hierarchical tree structure. The method further allows for receiving user input selecting events and containers to include in a segment and for displaying the relationship between selected events and containers as a rule.
The present invention is a system and method for generating a graphical or text-based user interface for a web analytics tool that allows for the creation and modification of segmentation definitions. While the present invention is described in the context of creation and modification of segmentation definitions for web analytics tools, those skilled in the art will recognize that the present invention may have various other applications, such as a user interface for generating queries on relational databases. The context in which the present invention is described is only for convenience and ease of understanding, and not to limit the scope of the present invention.
In the following 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.
The present invention also relates to 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. Coupling, as used herein, refers to communicative coupling, which may or may not be a physical attachment in the various embodiments.
The algorithms and displays presented herein are not inherently related to any particular computer 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 more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. 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.
Processor 102 processes data signals and may comprise various computing architectures including a complex instruction set computer (CISC) architecture, a reduced instruction set computer (RISC) architecture, or an architecture implementing a combination of instruction sets. Although only a single processor is shown in
Main memory 104 may store instructions and/or data that may be executed by processor 102. The instructions and/or data may comprise code for performing any and/or all of the techniques described herein. Main memory 104 may be a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, or some other memory device known in the art. The memory 104 is described in more detail below with reference to
Data storage device 107 stores data and instructions for processor 102 and may comprise one or more devices including a hard disk drive, a floppy disk drive, a CD-ROM device, a DVD-ROM device, a DVD-RAM device, a DVD-RW device, a flash memory device, or some other mass storage device known in the art.
System bus 101 represents a shared bus for communicating information and data throughout control unit 150. System bus 101 may represent one or more buses including an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, a universal serial bus (USB), or some other bus known in the art to provide similar functionality.
Additional components coupled to control unit 150 through system bus 101 include display device 100, keyboard 122, cursor control device 123, network controller 124, and audio device 125. Display device 100 represents any device equipped to display electronic images and data as described herein. Display device 100 may be a cathode ray tube (CRT), liquid crystal display (LCD), or any other similarly equipped display device, screen, or monitor. Keyboard 122 represents an alphanumeric input device coupled to control unit 150 to communicate information and command selections to processor 102. Cursor control 123 represents a user input device equipped to communicate positional data as well as command selections to processor 102. Cursor control 123 may include a mouse, a trackball, a stylus, a pen, a touch screen, cursor direction keys, or other mechanisms to cause movement of a cursor. Network controller 124 links control unit 150 to a network that may include multiple processing systems. The network of processing systems may comprise a local area network (LAN), a wide area network (WAN) (e.g., the Internet), and/or any other interconnected data path across which multiple devices may communicate.
One or more I/O devices 125 are coupled to the system bus 101. For example, the I/O device 125 may be an audio device 125 equipped to receive audio input and transmit audio output. Audio input may be received through various devices including a microphone within audio device 125 and network controller 124. Similarly, audio output may originate from various devices including processor 102 and network controller 124. In one embodiment, audio device 125 is a general purpose, audio add-in/expansion card designed for use within a general purpose computer system. Optionally, audio device 125 may contain one or more analog-to-digital or digital-to-analog converters, and/or one or more digital signal processors to facilitate audio processing.
It should be apparent to one skilled in the art that control unit 150 may include more or less components than those shown in
The operating system 202 in one embodiment is one of a conventional type such as, WINDOWS®, SOLARIS®, or LINUX® based operating systems.
The web browser 204 is of a conventional type that provides access to the Internet and processes HTML, XML, or other mark up language to generated images on the display device 100. For example, the web browser 204 could be Mozilla Firefox or Microsoft Internet Explorer.
The memory unit 104 also includes one or more application programs 206 including, without limitation, word processing applications, electronic mail applications, spreadsheet applications, and web browser applications.
The memory also includes a web analytics tool 210 such as Site Catalyst version 11 from Omniture of Orem, Utah. Such a tool 210 is disclosed in co-pending provisional patent application titled “Website Traffic Analysis Engine and User Interface,” Ser. No. 60/688,076 by Chris Error et al., filed Jun. 6, 2005 which is incorporated by reference in its entirety.
The segmentation builder user interface module 208 in one embodiment is a module for generation of graphical or text-based user interfaces that allows the user to define the filters or segment definitions that will be applied to a web analytics data store to produce data sets that are in turn used by the workbench portion of the web analytics tool 210. In addition, the interface displays to the user the relationship between events and containers making up the segment, as those terms are defined within this document. This function provides the ability to provide an interface that is intuitive, easy to use, and can be used by a layperson to extract the desired data from a data store. The segmentation builder user interface module 208 provides a variety of displays as will be described below with reference to
In one embodiment, the segmentation builder user interface module 208 provides functionality for displaying components for inclusion as a rule in a segment, displaying a canvas for defining the segment, receiving input for modification of a segment, displaying modified segments, saving segments, clearing the canvas, and applying the segment to stored data.
The segmentation engine 212 is a module that generates a data set based on input data source and a segmentation or rule definition. The segmentation engine 212 is coupled to a data source. A non-exhaustive list of exemplary data sources includes data warehouses, databases, and data files. The data source may be available via a network connection or may be stored on a data storage device 107 coupled by the bus 101 to the segmentation engine 212. The segmentation engine 212 applies a segmentation definition, or rule to the data source with the result being a data set that can be used by the web analytics tool 210.
The segmentation definition builder 214 is a module that translates input from segmentation builder user interface module 208 into instructions for the segmentation engine 212. The segmentation definition builder 214 effectively builds a segmentation definition that can be provided to the segmentation engine 212 and when run by the segmentation engine 212 on the data source produces the data set desired. The segmentation definition builder 214 is coupled to the segmentation builder user interface module 208 and the segmentation engine 212.
Referring now to
The process begins with displaying components 1110 for inclusion as a rule in a segment. In one embodiment, the components are broken into events and containers, and are displayed in a list as part of a user interface.
Next, a canvas is displayed 1120 for defining the segment, by allowing placement of components onto the canvas to form rules. If the user wants to create a new segment, the canvas displayed 1120 is blank. If the user wants to edit an existing segment, the canvas is populated with the components for the existing segment, for example by loading the segment, e.g., from memory. In one embodiment, there may be more than one canvas, for example, one canvas for including rules and one for excluding rules.
The next step is receiving input for modification of the segment 1130. In various embodiments, modifying the segment may include dragging and dropping components to a canvas, defining components, and deleting rules. In one embodiment, the components may be added in combination as either AND or OR combination operations. Following modification, 1130, modified segments are displayed 1140, e.g., via a user interface. The user may perform other tasks on the segments as well, such as saving the segment and clearing the canvas button. In addition, the user can choose to apply 1150 the segment to stored data.
Referring now to
Referring now to
The user interface 402 advantageous conveys this information using graphical bounding boxes or containers 410 according to one embodiment. The bounding boxes may be displayed in a visually distinct manner to reflect different types of containers. For example, different colors or different icons may be used to represent different types of containers. Moreover, the containers may vary in sized depending on the number of rules they contain, the number of other containers they contain and other factors upon which filtering is occurring.
The window of
Referring now to
The rule 502 includes a define/edit selector 504. When a component has not yet been defined, the define/edit selector 504 displays as Click here to define <component>, and the data returned is all data for the component 424. When a component has been defined, the define/edit selector 504 displays as Click here to edit <component>. Upon clicking the define/edit selector 504, the user can define or edit attributes to be included in a component 424. Clicking the define/edit selector 504 opens a define component screen 905.
Referring now to
The name field 910 allows the user to type a name for the canvas element. The match selector 915 allows the user to select whether the element will match “all” or “at least one” of the rules. The definition area 920 allows the user to define a text string, e.g., 804-808 as described in conjunction with
The definition area 920 further includes an item selector 930, an operator selector 935, a value selector 940, a select item link 945, and an add button 950. The item selector 930 allows the user to select an item from a list, for example a drop down menu. Examples of items include “Browser,” as shown in
The value selector 940 allows the user to select a value to apply to the item. The user can type in a value or can select from a list using the select item link 945. Clicking the select item link 945 opens a choose value screen 1005, such as shown in
Referring again to
Referring again to
The user interface allows any number of attributes of a component 424 to be included as variables in the text string and allows any logical, numerical, or Boolean operator between attributes and values. Multiple variables also can be combined within a single rule according to one embodiment.
Referring now to
Referring now also to
The text-based user interfaces 1205, 1210 shown are particularly advantageous because the relationships between containers and events in the hierarchy are shown, along with whether they are combined as AND and/or OR functions.
Workflow
The following is a description of interface functionality for defining a rule for filtering website visitation data according to one embodiment of the present invention in the context of
Beginning with blank canvases 412, 416 as shown in
When the user is finished selecting and editing rules, the user can save the segment by clicking the save button 419. The user can also apply the segment by selecting the apply segment filter button 422. If the user wants to start over, the user clicks the clear canvas button 420, which returns the user to the blank canvases 412, 416 shown in
Thus, those skilled in the art will recognize how the above user interface shown in
While the present invention has been described with reference to certain embodiments, those skilled in the art will recognize that various modifications may be provided. For example, certain embodiments may employ multiple application servers, acting in cooperation to perform a function or request. Any of the above functions or requests can be sent across a network. Variations upon and modifications to the described embodiments are provided for by the present invention.
This application is a continuation of U.S. application Ser. No. 11/313,445, filed on Dec. 20, 2005 now U.S. Pat. No. 7,761,457, which claims priority under 35 U.S.C. §119 from U.S. Provisional Application Ser. No. 60/688,211, filed Jun. 6, 2005 by Christopher R. Error et al., entitled “User Interface for the Creation of Segmentation Definitions in a Web Analytic Tool,” and is related to U.S. Provisional Application Ser. No. 60/688,076, filed Jun. 6, 2005 by Chris Error et al., entitled “Website Traffic Analysis Engine and User Interface,” each of which is incorporated herein in its entirety by reference.
Number | Name | Date | Kind |
---|---|---|---|
5760772 | Austin | Jun 1998 | A |
5796402 | Ellison-Taylor | Aug 1998 | A |
5821931 | Berquist et al. | Oct 1998 | A |
5835087 | Herz et al. | Nov 1998 | A |
5870559 | Leshem et al. | Feb 1999 | A |
5966139 | Anupam et al. | Oct 1999 | A |
6008809 | Brooks | Dec 1999 | A |
6026397 | Sheppard | Feb 2000 | A |
6182097 | Hansen et al. | Jan 2001 | B1 |
6188405 | Czerwinski et al. | Feb 2001 | B1 |
6266649 | Linden et al. | Jul 2001 | B1 |
6310631 | Cecco et al. | Oct 2001 | B1 |
6393479 | Glommen et al. | May 2002 | B1 |
6414677 | Robertson et al. | Jul 2002 | B1 |
6470335 | Marusak | Oct 2002 | B1 |
6473102 | Rodden et al. | Oct 2002 | B1 |
6489968 | Ortega et al. | Dec 2002 | B1 |
6654036 | Jones | Nov 2003 | B1 |
6671711 | Pirolli et al. | Dec 2003 | B1 |
6704016 | Oliver et al. | Mar 2004 | B1 |
6744729 | Tinsley et al. | Jun 2004 | B2 |
6754873 | Law et al. | Jun 2004 | B1 |
6766370 | Glommen et al. | Jul 2004 | B2 |
6850988 | Reed | Feb 2005 | B1 |
6862574 | Srikant et al. | Mar 2005 | B1 |
6931391 | Tang et al. | Aug 2005 | B2 |
6938041 | Brandow et al. | Aug 2005 | B1 |
6950993 | Breinberg | Sep 2005 | B2 |
6963874 | Kasriel et al. | Nov 2005 | B2 |
6968511 | Robertson et al. | Nov 2005 | B1 |
6980962 | Arganbright et al. | Dec 2005 | B1 |
7161487 | Tracey et al. | Jan 2007 | B1 |
7640252 | Tang et al. | Dec 2009 | B2 |
20010049671 | Joerg | Dec 2001 | A1 |
20020040395 | Davis et al. | Apr 2002 | A1 |
20020042750 | Morrison | Apr 2002 | A1 |
20020087621 | Hendriks | Jul 2002 | A1 |
20020091591 | Tsumura et al. | Jul 2002 | A1 |
20020093529 | Daoud et al. | Jul 2002 | A1 |
20020099812 | Davis et al. | Jul 2002 | A1 |
20020152284 | Cambray et al. | Oct 2002 | A1 |
20020165936 | Alston et al. | Nov 2002 | A1 |
20020186237 | Bradley et al. | Dec 2002 | A1 |
20020186253 | Rodden et al. | Dec 2002 | A1 |
20020198939 | Lee et al. | Dec 2002 | A1 |
20030023712 | Zhao et al. | Jan 2003 | A1 |
20030025737 | Breinberg | Feb 2003 | A1 |
20030055883 | Wiles, Jr. | Mar 2003 | A1 |
20030128231 | Kasriel et al. | Jul 2003 | A1 |
20030131097 | Kasriel et al. | Jul 2003 | A1 |
20030236784 | Tang et al. | Dec 2003 | A1 |
20040049417 | Nickerson et al. | Mar 2004 | A1 |
20040059746 | Error et al. | Mar 2004 | A1 |
20040070606 | Yang et al. | Apr 2004 | A1 |
20040133671 | Taniguchi | Jul 2004 | A1 |
20040205157 | Bibeinieks et al. | Oct 2004 | A1 |
20050044508 | Stockton | Feb 2005 | A1 |
20050108625 | Bhogal et al. | May 2005 | A1 |
20050144163 | Tang et al. | Jun 2005 | A1 |
20050204307 | Nadal | Sep 2005 | A1 |
20050229110 | Gegner et al. | Oct 2005 | A1 |
20050235222 | Barbanson et al. | Oct 2005 | A1 |
20050246283 | Gwiazda et al. | Nov 2005 | A1 |
20050273727 | Barbanson et al. | Dec 2005 | A1 |
20060026147 | Cone et al. | Feb 2006 | A1 |
20060085132 | Sharma et al. | Apr 2006 | A1 |
20090030771 | Eder | Jan 2009 | A1 |
Number | Date | Country |
---|---|---|
0058866 | Oct 2000 | WO |
0223438 | Mar 2002 | WO |
03105024 | Dec 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20100251130 A1 | Sep 2010 | US |
Number | Date | Country | |
---|---|---|---|
60688211 | Jun 2005 | US | |
60688076 | Jun 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11313445 | Dec 2005 | US |
Child | 12815286 | US |