Abstract: Systems and methods provide for data management and governance to enforce proper usage of combined data formed from different pieces of data. Data governance metadata identifying authentication states for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative authentication states. Similarly, data governance metadata identifying standard contractual considerations for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative standard contractual considerations. An extent to which the combined data can be used to identify and/or contact a person is determined, and data governance metadata is tagged to the combined data identifying the extent to which the data can be used to identify and/or contact the person.

Abstract: Systems and methods provide for data management and governance to enforce proper usage of data. Data is tagged with data governance metadata dictating usage of the data. Standard types of data governance metadata are set forth with each type having predefined options such that applications can share data and understand the associated data governance metadata. When data is to be used by an application, an available action is identified, and a set of data governance rules for that action is accessed. The data governance rules set forth an impact of each type of data governance metadata on the ability to perform that action. As such, the action is allowed or disallowed for the data based on the data governance metadata for the data and on the data governance rules for the action.

Abstract: Systems and methods provide for data management and governance to enforce proper usage of combined data formed from different pieces of data. Data governance metadata identifying authentication states for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative authentication states. Similarly, data governance metadata identifying standard contractual considerations for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative standard contractual considerations. An extent to which the combined data can be used to identify and/or contact a person is determined, and data governance metadata is tagged to the combined data identifying the extent to which the data can be used to identify and/or contact the person.

Abstract: Systems and methods provide for data management and governance to enforce proper usage of combined data formed from different pieces of data. Data governance metadata identifying authentication states for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative authentication states. Similarly, data governance metadata identifying standard contractual considerations for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative standard contractual considerations. An extent to which the combined data can be used to identify and/or contact a person is determined, and data governance metadata is tagged to the combined data identifying the extent to which the data can be used to identify and/or contact the person.

Abstract: Systems and methods provide for data management and governance to enforce proper usage of data. Data is tagged with data governance metadata dictating usage of the data. Standard types of data governance metadata are set forth with each type having predefined options such that applications can share data and understand the associated data governance metadata. For a given data, one or more options are selected for each type of data governance metadata and tagged to the data to control usage of the data.

Abstract: Systems and methods provide for data management and governance to enforce proper usage of data. Data is tagged with data governance metadata dictating usage of the data. Standard types of data governance metadata are set forth with each type having predefined options such that applications can share data and understand the associated data governance metadata. When data is to be used by an application, an available action is identified, and a set of data governance rules for that action is accessed. The data governance rules set forth an impact of each type of data governance metadata on the ability to perform that action. As such, the action is allowed or disallowed for the data based on the data governance metadata for the data and on the data governance rules for the action.

Abstract: Systems and methods provide for data management and governance to enforce proper usage of combined data formed from different pieces of data. Data governance metadata identifying authentication states for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative authentication states. Similarly, data governance metadata identifying standard contractual considerations for the individual pieces of data are combined to tag the combined data with new data governance metadata indicating the cumulative standard contractual considerations. An extent to which the combined data can be used to identify and/or contact a person is determined, and data governance metadata is tagged to the combined data identifying the extent to which the data can be used to identify and/or contact the person.

Abstract: Systems and methods provide for data management and governance to enforce proper usage of data. Data is tagged with data governance metadata dictating usage of the data. Standard types of data governance metadata are set forth with each type having predefined options such that applications can share data and understand the associated data governance metadata. For a given data, one or more options are selected for each type of data governance metadata and tagged to the data to control usage of the data.

Abstract: Multiple selected checkpoints define a group of paths represented in an analytics database. One or more events which appear between the multiple checkpoints on each of a plurality of the paths are identified as common bridge events. Path analysis information is then output, such as a bridge event analysis including a list of website visitor common bridge events that are ranked by their frequency of appearance, the frequencies calculated without regard to where each visitor event appears on a given path.

Abstract: Multiple selected checkpoints define a group of paths represented in an analytics database. One or more events which appear between the multiple checkpoints on each of a plurality of the paths are identified as common bridge events. Path analysis information is then output, such as a bridge event analysis including a list of website visitor common bridge events that are ranked by their frequency of appearance, the frequencies calculated without regard to where each visitor event appears on a given path.

Abstract: Two selected checkpoints define a group of paths represented in an analytics database. One or more events which appear between the two checkpoints on each of a plurality of the paths are identified as common bridge events. Path analysis information is then output, such as a bridge event analysis including a list of website visitor common bridge events that are ranked by their frequency of appearance, the frequencies calculated without regard to where each visitor event appears on a given path.

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.

Abstract: Two selected checkpoints define a group of paths represented in an analytics database. One or more events which appear between the two checkpoints on each of a plurality of the paths are identified as common bridge events. Path analysis information is then output, such as a bridge event analysis including a list of website visitor common bridge events that are ranked by their frequency of appearance, the frequencies calculated without regard to where each visitor event appears on a given path.

Abstract: In the context of a site analysis report showing paths between nodes, a relevance slider allows a user to dynamically specify how many node-to-node connections should be shown at any given time. The user can position the slider as desired, so as to specify a threshold level. Only those node connections having a relevance level (measured, for example, as a traffic level) exceeding the specified threshold are shown. In one embodiment, lines representing node connections fade in and out as the slider is moved, so as to provide instantaneous visual feedback.

Abstract: In the context of a site analysis report showing paths between nodes, color is used to indicate a direction of traffic that follows a particular node-to-node path. Different colors are assigned to different nodes in a site analysis report. Paths are color-coded according to their destination nodes, so as to provide a distinctive visual identification of a traffic flow direction. Node connection direction can be reinforced by static or moving arrows.

Abstract: A data set containing website traffic data or other data is sampled according to a variable sample rate. A target number of samples per time period is established, and a baseline sample rate is determined. Data items in the data set are sampled according to the baseline sample rate, to obtain a sample set. For time periods where the size of the resulting sample set exceeds the target number of samples, a new sample rate is established and the data items for the time period are resampled. Appropriate sampling capability can thus be provided for website traffic in normal time periods, while maintaining capability for handling spikes and other variations in website traffic as may take place in response to certain periodic or non-periodic events.

Abstract: Objects on a web page are associated with stored records indicating historical object usage. Associations between objects and records take into account discrepancies in object identifiers resulting from authorial edits and/or differences in browser assignment of object identifiers. An object having an object identifier that differs from that of a stored record by not more than a predetermined tolerance value, and that has other indicia that match the stored record, is considered to match the stored record. Reports are generated quantifying web page object usage, for example by superimposing color shadings or other visual indicia on a representation of a web page.

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.

Abstract: A network architecture with load balancing, fault tolerance and distributed querying comprises a plurality of front-end servers, a plurality of back-end servers, and a database. The front-end servers are coupled to a network to receive data requests from client devices. The front-end servers are each coupled to the plurality of back-end servers. The front-end servers handle data requests at a macro level and divide the request into sub-requests that are sent to the plurality of back-end servers. The back-end servers are coupled to the database to retrieve data. Each data request is distributed across the plurality of back-end servers according to workload. The front-end servers are fault tolerant in that they can respond to a request for data without all of the back-end servers being responsive or providing data.

Abstract: Objects on a web page are associated with stored records indicating historical object usage. Associations between objects and records take into account discrepancies in object identifiers resulting from authorial edits and/or differences in browser assignment of object identifiers. An object having an object identifier that differs from that of a stored record by not more than a predetermined tolerance value, and that has other indicia that match the stored record, is considered to match the stored record. Reports are generated quantifying web page object usage, for example by superimposing color shadings or other visual indicia on a representation of a web page.