Abstract: A method to automatically classify video content retrieved over the Internet and, in particular, to determine whether a candidate video is an instance of a source video. The method begins by sampling static image frames from each of the candidate video and the source video. Based on the sampled static image frames, a set of static image frames in the candidate video that match a corresponding set of static image frames in the source video are then identified. Metadata associated with the sets of matching static image frames are then compared to determine how closely a temporal order of the set of static image frames in the candidate video matches the temporal order of the set of static image frames in the source video. Based on a measure of temporal order match, a classification is then applied to the candidate video to complete the method.

Abstract: One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.

Abstract: The techniques disclosed herein facilitate online audience targeting based on brand and product interest/enthusiasm as determined by a measurement metric that is a function of one of more (and preferably all) of the following: recency data, frequency data, intensity data, consumption data, site data, meta data related to given videos, data, and other demographic data.

Abstract: A choice-based ad unit format wherein a user chooses his or her pre-roll ad or can choose to wait for the main content to load. Once the video advertisement selected loads, the user can then choose to skip the ad or view the entire ad experience. Preferably, the ad viewing experience is integrated with a site to enable the ad unit to have unlimited access to in-stream inventory that is otherwise available from the site.

Abstract: This disclosure describes methods and systems to quantify and understand the behavior and consumption patterns of audiences with respect to Internet video and rich media applications. In operation, an end user video player or a rich media application (such as an interactive advertisement built with Flash or other method) is instrumented to capture data. The data is collected by a service provider and made available for viewing by customers of a video experience and rich media behavior measurement service.

Abstract: This disclosure describes methods and systems to quantify and understand the behavior and consumption patterns of audiences with respect to Internet video and rich media applications. In operation, an end user video player or a rich media application (such as an interactive advertisement built with Flash or other method) is instrumented to capture data. The data is collected by a service provider and made available for viewing by customers of a video experience and rich media behavior measurement service.

Abstract: One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated. If the application is able to write to a local file system, usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server. The usage information tracked comprises “features,” “faults” and “failures” of the application, independent of platform, location, and number of deployed application instances.

Abstract: One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated. If the application is able to write to a local file system, usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server. The usage information tracked comprises “features,” “faults” and “failures” of the application, independent of platform, location, and number of deployed application instances.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. Preferably, an application under test is one of: application software, a script-enabled web application, or a rich Internet application (RIA). During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated, typically in one of two ways. If the application is able to write to a local file system (in the user's machine), usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server.

Abstract: A method and system for approximating the viewing time of a video posted on a website of a plurality of websites on the Internet is disclosed herein. The method and system is able to approximate the viewing time of the online video by a visitor computer and transmit the information to a compiling server.

Abstract: A method and system for approximating the viewing time of a video posted on a website of a plurality of websites on the Internet is disclosed herein. The method and system is able to approximate the viewing time of the online video by a visitor computer and transmit the information to a compiling server.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. Preferably, an application under test is one of: application software, a script-enabled web application, or a rich Internet application (RIA). During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated, typically in one of two ways. If the application is able to write to a local file system (in the user's machine), usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server.