Dynamically generating aggregate tables

• US 8,549,019 B2
• Filed: 05/25/2010
• Issued: 10/01/2013
• Est. Priority Date: 05/26/2009
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Nandy, Sagnik, Damm, Kevin, White, David
• Primary Examiner(s): Singh, Amresh
• Application Number:
  US12/787,291
• Publication Number:
  US 20100318527A1
• Time in Patent Office: 1,225 Days
• Field of Search: 707/754
• US Class Current: 707/754
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range

Abstract

A method and system dynamically create aggregate tables. An aggregate table manager is instantiated that receives a plurality of aggregate table definitions, and generates aggregate tables based on the received aggregate table definitions. The aggregate table manager creates a view corresponding to each of the aggregate tables. The aggregate table manager creates and updates data entries in the aggregate tables based on their corresponding aggregate table definitions and data extracted from web site log files.

Claims

1. A computer-implemented method for creating aggregate tables for web analytics, the method comprising:

at a server having one or more processors and memory, performing the following;

receiving a web site selection;

receiving a plurality of aggregate table definitions;

generating respective aggregate tables for the web site according to the received aggregate table definitions;

populating and updating data entries in the generated aggregate tables for the web site based on their corresponding aggregate table definitions and server hit data derived from log files for the web site and stored in a hits table;

providing a user interface for selection of a view of web analytics data;

receiving a view selection from a user utilizing the user interface;

determining whether the selected view includes data in one or more aggregate tables;

when the selected view includes data in at least one aggregate table;

retrieving data from the at least one aggregate table; and

returning the data to the user in a respective view; and

when the selected view includes data that is not stored in any aggregate table;

executing a corresponding query in the hits table;

retrieving the data from the hits table in response to the query; and

returning the data to the user in a respective view.

2. The method of claim 1, wherein the one or more custom aggregate table definitions correspond to the web site.

3. The method of claim 1, wherein the log files for a website are in two or more different formats.

4. The method of claim 1, wherein a first aggregate table definition of the one or more custom aggregate table definitions specifies metrics and dimensions to be included in a first aggregate table and wherein the server hit data used to populate and update the first aggregate table corresponds to the metrics and dimensions specified in the first aggregate table definition.

5. The method of claim 4, further comprising:

generating an aggregate table class according to the first aggregate table definition, wherein the class executes at the server to perform the generating, populating, and updating operations for the first aggregate table.

6. The method of claim 5, wherein the aggregate table class includes:

retrievers to retrieve server hit data for the metrics and dimensions used in the first aggregate table; and

filters to limit the server hit data retrieved according to the first aggregate table definition.

7. The method of claim 4, wherein the first aggregate table definition further includes:

descriptions of filtering to be performed on the hits data corresponding to one or more of the metrics and dimensions; and

a sort order indicating a sort operation to be performed on data in the first aggregate table and a metric or dimension on which the sort operation is to be applied.

8. The method of claim 4, further comprising:

receiving a modification to an existing aggregate table definition; and

generating a new aggregate table definition using the modification.

9. The method of claim 8, further comprising:

generating from the new aggregate table definition a respective aggregate table class that, when executed, causes the server to perform the generating, populating, and updating operations for a new aggregate table.

10. The method of claim 9, further comprising:

reusing data from the first aggregate table in the new aggregate table without accessing a hits table for those dimensions or metrics that are duplicates of dimensions or metrics in the first aggregate table, wherein the hits table stores the server hit data.

11. An analytics data aggregation system, comprising:

one or more processors;

memory; and

one or more programs stored in the memory, the one or more programs comprising instructions for;

receiving a web site selection;

receiving a plurality of aggregate table definitions;

generating respective aggregate tables for the web site according to the received aggregate table definitions;

populating and updating data entries in the generated aggregate tables for the web site based on their corresponding aggregate table definitions and server hit data derived from log files for the web site and stored in a hits table;

providing a user interface for selection of a view of web analytics data;

receiving a view selection from a user utilizing the user interface;

determining whether the selected view includes data in one or more aggregate tables;

when the selected view includes data in at least one aggregate table;

retrieving data from the at least one aggregate table; and

returning the data to the user in a respective view; and

when the selected view includes data that is not stored in any aggregate table;

executing a corresponding query in the hits table;

retrieving the data from the hits table in response to the query; and

returning the data to the user in a respective view.

12. The data aggregation system of claim 11, wherein the one or more custom aggregate table definitions correspond to the web site.

13. The data aggregation system of claim 11, wherein a first aggregate table definition of the one or more custom aggregate table definitions specifies metrics and dimensions to be included in a first aggregate table and wherein the server hit data used to populate and update the first aggregate table corresponds to the metrics and dimensions specified in the first aggregate table definition.

14. The data aggregation system of claim 13, further comprising instructions for:

generating an aggregate table class according to the first aggregate table definition, wherein the class executes at the server to perform the generating, populating, and updating operations for the first aggregate table.

15. The data aggregation system of claim 14, wherein at least one aggregate table class includes:

retrievers to retrieve server hit data for the metrics and dimensions used in the first aggregate table; and

filters to limit the server hit data retrieved according to the first aggregate table definition.

16. The data aggregation system of claim 13, wherein the first aggregate table definition further includes:

descriptions of filtering to be performed on the hits data corresponding to one or more of the metrics and dimensions; and

a sort order indicating a sort operation to be performed on data in the first aggregate table and a metric or dimension on which the sort operation is to be applied.

17. The data aggregation system of claim 13, further comprising instructions for:

receiving a modification to an existing aggregate table definition; and

generating a new aggregate table definition using the modification.

18. The data aggregation system of claim 17, further comprising instructions for:

generating from the new aggregate table definition a respective aggregate table class that, when executed, causes the server to perform the generating, populating, and updating operations for a new aggregate table.

19. The data aggregation system of claim 18, further comprising instructions for:

reusing data from the first aggregate table in the new aggregate table without accessing a hits table for those dimensions or metrics that are duplicates of dimensions or metrics in the first aggregate table, wherein the hits table stored the server hit data.

20. A computer-implemented method for creating aggregate tables for web analytics, comprising:

at a server computer having one or more processors and memory, performing the following;

receiving an aggregate table definition from a user, the aggregate table definition including a description of metrics and dimensions to be included in the aggregate table for a particular web site, data for the metrics and dimensions being stored in a hit table generated from log files for the particular web site;

building an executable class definition for the aggregate table based on the aggregate table definition, the class definition including;

retriever modules configured to extract data for respective dimensions and metrics from the hit table and to populate the aggregate table with the extracted data;

generator modules configured to generate views for an end user corresponding to the data in the aggregate table;

executing a class corresponding to the executable class definition, thereby generating and populating an aggregate table according to the aggregate table definition;

providing a user interface for selection of a view of web analytics data;

receiving a view selection from a user utilizing the user interface;

determining whether the selected view includes data in one or more aggregate tables;

when the selected view includes data in at least one aggregate table;

retrieving data from the at least one aggregate table; and

returning the data to the user in a respective view; and

when the selected view includes data that is not stored in any aggregate table;

executing a corresponding query in the hits table;

retrieving the data from the hits table in response to the query; and

returning the data to the user in a respective view.