Oracle International Corporation

Blue Kai, Inc.

David Scott Gardner

David Abraham Wiener

Dossel Obrian Reid, Jr

John Patrick Connelly

Dossel Obrian Reid

The disclosure is directed to approaches for combining server-side decisions based on user attributes and/or demographics with client-side decisions based on expressed or implied user interests determined based on the contents of a web page being visited by the user. A server is responsive to an occurrence of an operation of a client device at the web page. Processing steps determine particular executable web page content to send to the client device (e.g., where the particular executable web page content is determined in response to a particular client-side operation). The web page is rendered with the aforementioned executable web page content. Server-side processing receives messages that are emitted conditionally, based on the occurrence of a user event. An event log message comprises a portion of the web page, such as a string, indicating or implying user interest. A targeted advertisement is presented to the user based on the user interest.

Evaluating page content to determine user interest

Embodiments are directed towards employing a plurality of tag states to control tag suspension based on an asynchronous process that proactively monitors tag performance, response times, privacy safeguards, and latency. Tags may be in one of multiple states. Tags in a NORMAL state or a FLAGGED state may be enabled for deployment, and tags in a SUSPENSION A state or a SUSPENSION B state may be blocked from deployment. A tag's state may change based on monitoring the tag's latency to determine if latent events occur. Tag latency may be asynchronously monitored independent of web page requests or requests to execute an application. For example, if latent events occur, then the tag's state may change from NORMAL to FLAGGED, and if non-latent events occur, then the tag's state may change from FLAGGED to NORMAL.

Tag latency monitoring and control system for enhanced web page performance

Embodiments are directed towards employing a plurality of tag states to control tag suspension based on an asynchronous process that proactively monitors tag performance, response times, and latency. Tags may be in one of multiple states. Tags in a NORMAL state or a FLAGGED state may be enabled for deployment, and tags in a SUSPENSION A state or a SUSPENSION B state may be blocked from deployment. A tag's state may change based on monitoring the tag's latency to determine if latent events occur. Tag latency may be asynchronously monitored independent of web page requests. If latent events occur, then the tag's state may change from NORMAL to FLAGGED, from FLAGGED to SUSPENSION A, or from SUSPENSION B to SUSPENSION_A. If non-latent events occur, then the tag's state may change from SUSPENSION B to FLAGGED or from FLAGGED to NORMAL, while a tag's state may change from SUSPENSION_A to SUSPENSION_B after a predetermined time period.

A system, method, and computer program product for reducing web page load latency by scheduling sets of successive outgoing HTTP calls. Some embodiments commence upon receiving from a requesting client device, a request for content of a web page, wherein the content comprises two or more portions of dynamic content. Operations are performed to determine that the two or more portions of dynamic content are to be processed separately. A scheduling script to be executed by the requestor is generated and sent to the client device. The scheduling script comprises instructions to process a first subset of the two or more dynamic portions of content and also comprises instructions to process a second subset of the two or more portions of dynamic content. The scheduling script, when executed by requesting client device, causes the first subset of dynamic content and the second subset of dynamic content to be processed separately.

Reducing web page load latency by scheduling sets of successive outgoing HTTP calls

Embodiments are directed towards employing a plurality of tag states to control tag suspension based on an asynchronous process that proactively monitors tag performance, response times, and latency. Tags may be in one of multiple states. Tags in a NORMAL state or a FLAGGED state may be enabled for deployment, and tags in a SUSPENSION_A state or a SUSPENSION_B state may be blocked from deployment. A tag's state may change based on monitoring the tag's latency to determine if latent events occur. Tag latency may be asynchronously monitored independent of web page requests. If latent events occur, then the tag's state may change from NORMAL to FLAGGED, from FLAGGED to SUSPENSION_A, or from SUSPENSION_B to SUSPENSION_A. If non-latent events occur, then the tag's state may change from SUSPENSION_B to FLAGGED or from FLAGGED to NORMAL, while a tag's state may change from SUSPENSION_A to SUSPENSION_B after a predetermined time period.

Growing community of inventors

San Jose, CA, United States of America

David Scott Gardner