Abstract: Configurations for providing a pushed based real-time analytics system are disclosed. The system incorporates a network and distributed database configured to stream real-time analytics data through multiple tiers. The real-time analytics data is routed/pushed through the system without requiring an additional requests from a front-end client. For instance, after the front-end client initiates a query with the real-time analytics system, a pipeline is opened to the front-end client and web site traffic data is pushed without requiring polling or other explicit requests from the front-end client. As incoming web site tracking data communications are received, the incoming web site tracking data communications are automatically routed and pushed through different tiers of the system. Real-time web site tracking data is automatically presented to the front-end client without requiring constant refreshing (which introduces latency) of a web browser or similar client application.

Abstract: A system and machine-implemented method for providing effectiveness indications for social networking activity including receiving a request to provide an effectiveness score, identifying a plurality of actions performed with respect to the social networking activity by one or more other users exposed to the social networking activity, determining the total number of unique users performing the action, calculating an activity score for the social networking activity based on the determined number of users, determining a number of the users exposed to the social networking activity, calculating an effectiveness score for the social networking activity based on the total activity score and the number of users exposed to the social networking activity, wherein the effectiveness score comprises calculating the effectiveness score at least in part based on a ratio of the activity score to the number of the users exposed to the to the social networking activity.

Abstract: Configurations for providing temporal based data string intern pools that reuse data strings and decrease unnecessary operations to memory. A data structure representing a string intern pool is allocated for a first time period and one or more strings associated with event data communications are stored in the data structure. To optimize memory usage, if a string associated with an event tracking data communication is located within the data structure, a pointer is then assigned to the string instead of storing the string in the data structure. In a second time period, a second data structure is allocated for another string intern pool and matching strings from event tracking data communications are assigned to pointers for existing strings in the second data structure. The first data structure is maintained during the second time period but no additional strings are written to the first data structure.

Abstract: Machine-implemented methods for validating a web site analytics configuration are provided. In one aspect, a method includes receiving, with a low latency web site traffic analytics and monitoring service, a registration for a web site, and sending an initial transmission to the registered web site, the transmission configured to generate a response transmission of web site traffic data to the analytics service. The method also includes outputting a notification indicating that the web site has been successfully registered with the analytics service when the traffic data is received by the analytics service, and outputting a notification indicating that the web site has not been successfully registered with the analytics service when the traffic data is not received by the analytics service. Systems, graphical user interfaces, and machine-readable media are also provided.

Abstract: Machine-implemented methods for reconfiguring a web site configuration are provided. In one aspect, a method includes acquiring low latency web site traffic data for a web site, and automatically modifying a layout or content of the web site or a web page on the web site based on information derived from the acquired low latency web site traffic data for the web site. Systems, graphical user interfaces, and machine-readable media are also provided.

Abstract: Machine-implemented methods for troubleshooting a web site analytics configuration are provided. In one aspect, a method includes acquiring low latency web site traffic data for a web page for a web site, and comparing the low latency web site traffic data with historical web site traffic data for the web page. The method also includes determining a difference between the low latency web site traffic data and the historical web site traffic data based on the comparison, and sending information on the difference between the low latency web site traffic data and the historical web site traffic data. Systems, graphical user interfaces, and machine-readable media are also provided.

Abstract: Configurations providing a configurable buffer for storing incoming event tracking data communications in a lossy manner are described. In one aspect, a server can utilize the configurable buffer for storing the incoming event tracking data communications. When the buffer becomes full, the server can transmit the accumulated tracking data communications in the configuration buffer as a batch transmission. The server can discard any new incoming requests once the buffer becomes full. Further, the server can replace data in the buffer with new incoming requests based on one or more criterion if the buffer is full. In some implementations, the server transmits the batch of the accumulated tracking data communications in the configurable buffer after a predetermined time has elapsed.

Abstract: Machine-implemented methods for providing information to a graphical user interface for displaying web site traffic information are provided. In one aspect, the method includes acquiring low latency web site traffic data for a web site, identifying at least one path taken by at least one visitor between a plurality of web pages for the web site based on the acquired low latency web site traffic data, and providing information for a graphical representation of the identified at least one path. Systems and machine-readable media are also provided.

Abstract: Machine-implemented methods for providing information to a graphical user interface for displaying web site traffic information are provided. In one aspect, a method includes acquiring low latency web site traffic data for a web site and acquiring historical web site traffic data for the web site. The method also includes combining, into combined web site traffic data, the low latency web site traffic data for the web site with the historical web site traffic data for the web site, and providing the combined web site traffic data to a graphical user interface for display. Systems, graphical user interfaces, and machine-readable media are also provided.

Abstract: Machine-implemented methods for providing a graphical user interface for displaying web site traffic information are provided. In one aspect, a method includes acquiring low latency web site traffic data for a web site and historical web site traffic data for the web site, and calculating a historical average web site traffic value for the web site based on the historical web site traffic data. The method also includes comparing the low latency web site traffic data with the calculated historical average web site traffic value, and providing information on a variation in the low latency web site traffic data based on the comparison of the low latency web site traffic data with the calculated average web site traffic value. Systems and machine-readable media are also provided.

Abstract: Configurations for performing automated segmenting of tracking data included in an event tracking data communication over a rolling window of time are described. After an event tracking data communication is received associated with a time stamp, some configurations can segment the event tracking data communication according to one or more aggregation tables and store and/or update the included tracking data into one or more aggregation tables. In one aspect, a respective aggregation table corresponds to a predetermined period of time and includes corresponding event tracking data that is frequently searched/queried in reporting real-time analytics data. Some configurations continually sort the segments of tracking data within each of the aggregation tables to report the top segments of the tracking data from those aggregation tables in a real-time manner.

Abstract: Machine-implemented methods for providing information to a graphical user interface for displaying web site traffic information are provided. In one aspect, a method includes acquiring low latency web site traffic data for a web page, and providing the acquired low latency web site traffic data to a graphical user interface for display. The acquired low latency web site traffic data is configured to be displayed concurrently with a display of at least a portion of the web page. Systems, graphical user interfaces, and machine-readable media are also provided.

Abstract: Configurations for creating a customized query for aggregating the web site tracking data in order to provide a new query response stream for a real-time presentation of the web site tracking data are disclosed. The subject technology provides publisher-defined queries to existing queries that are applied to real-time analytics data. In some configurations, a new aggregation table is created according to the customized query. As incoming event tracking data communications are received, the event tracking data from the communications is continuously segmented and updated into the new aggregation table according to the customized query. The event tracking data from the new aggregation table is then pushed or delivered to a front-end client for presentation.

Abstract: Configurations of a multi-tiered system for receiving and reporting web site traffic data with low latency are described. The multi-tiered system can include a tier of collecting servers for receiving incoming event tracking data communications (e.g., HTTP requests for logging web page requests at corresponding web sites). A collecting server receiving an incoming communication determines a particular logging server in a lower tier to route the incoming communication. Upon receiving the incoming communication, the logging server processes the communication by 1) logging the communication to persistent storage, and 2) routing the communication to i) a tier of long-term storage servers and ii) a tier of short term storage and low-latency servers (i.e., real-time servers) for aggregating and reporting web site traffic data. Each real-time server can be configured to aggregate the web site tracking data for reporting to a publisher with low latency.

Abstract: Configurations for providing fine-grain locking of data structures for concurrent reading and writing into one or more data structures utilized by a real-time server. In one aspect, when an update is required to a portion of a data structure, the process enables locking of only that portion of the data structure to prevent other threads and/or processes from accessing the locked portion. Other threads or CPU processes can concurrently read and/or update non-locked portions of the data structure. Another aspect provides for determining whether an access to a portion of a data structure has occurred if the portion is locked and subsequently releasing the portion of the data structure if the access has occurred. In one aspect, the portion is release after a configurable predetermined period of time.

Abstract: Configurations providing a probabilistic ownership protocol for managing respective web property IDs (WPID) associated with incoming event tracking data communications are described. A server can determine whether an event tracking data communication with an associated WPID has an owner by checking a master ownership table. The server can register an intent to become an owner of the event tracking data communication if a minimum number of owner(s) is not met. The server then waits for a random period of time. After the random period of time, the server can check the master ownership table to determine whether the event tracking data communication has an owner or enough owners. The server can then register for ownership of the event tracking data communication by modifying the master ownership table if the event tracking data communication does not have an owner or enough owners.