Client-Side Scout Component for RTB Ad Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current online video advertising systems, particularly Real-Time Bidding (RTB) platforms, face limitations in providing flexible control over ad events, inadequate tracking and measurement capabilities, and lack of interactive user experiences, which restricts advertisers' ability to target specific viewers and collect rich interaction data.

Innovation Solution

The introduction of a client-side component called Scout, which operates as an interface between publishers and advertisers, enabling flexible tracking of ad events, providing interactive features like overlays and feedback buttons, and facilitating on-the-fly ad decisioning, along with a Companion component for dynamic companion ad management, to enhance RTB transactions and measurement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If advertisement exchanges aggregate advertisement space supply from various websites, then the inventory size increases, but the ability to target specific viewers deteriorates

Engineering Contradiction:
Improveinventory sizeVSAvoidability to target specific viewers
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent segments the advertising system into multiple independent components: Scout components deployed on client devices for local decision-making and tracking, Companion components for ad delivery, and Exchange components for transaction management. This segmentation allows the system to maintain large aggregated inventory while enabling precise local targeting decisions based on user context and device information.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Scout component acts as an intermediary between the user's device and the advertisement exchange. It collects device information, user preferences, and contextual data locally, then uses this information to make intelligent bidding decisions and select appropriate advertisements from the aggregated inventory, thereby maintaining targeting precision despite the large scale of the exchange.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If Real-Time Bidding systems use server-side auction, then the control over ad events is centralized, but the tracking and measurement capabilities become inadequate

Engineering Contradiction:
Improvecentralized controlVSAvoidtracking and measurement capabilities
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent divides the tracking and measurement functions across multiple segments: the Scout component on client devices performs local event tracking and data collection, while the Exchange component performs centralized auction management. This distributed segmentation enables both centralized control and precise local measurement of ad events.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Scout component continuously collects feedback information about user interactions, device state, and ad performance, then uses this feedback to adjust bidding strategies and improve targeting in real-time. This feedback loop enhances measurement precision by capturing actual user behavior data at the point of interaction.

Inventive Principle:
Principle #23Feedback

3Device complexity

If traditional advertising systems provide basic ad delivery, then the system simplicity is maintained, but the interactive user experiences are lacking

Engineering Contradiction:
Improvesystem simplicityVSAvoidinteractive user experiences
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The Scout component enables the client device to autonomously perform complex functions including ad selection, bidding decisions, and interaction tracking without requiring complex server-side processing for each user action. This self-service capability delivers rich interactive experiences while maintaining relative system simplicity by pushing intelligence to the edge.

Inventive Principle:
Principle #25Self-service

4Loss of information

If advertisers want to collect rich interaction data, then the data collection capability improves, but the system complexity increases

Engineering Contradiction:
Improvedata collection capabilityVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The Scout component serves as an intermediary that collects rich interaction data locally at the client device, including user behavior, device characteristics, and contextual information. By performing data collection at the source, the system captures comprehensive information without requiring complex centralized data gathering infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments data collection responsibilities to the Scout component on client devices, which handles local data gathering and preliminary processing. This segmentation allows rich data collection while maintaining system simplicity by distributing the complexity to edge components rather than centralizing it.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10003838B2Client-side scout and companion in a real-time bidding advertisement system
Publication Date: 2018.06.19 YAHOO AD TECH LLC
  • US10003838B2 patent drawing
  • US10003838B2 patent drawing
  • US10003838B2 patent drawing

AI summary

A client-side component in a real-time bidding (RTB) system for video advertisements configures the client device to, in response to a request for a video advertisement sent by the client device to the real-time bidding system, receive a first set of information associated with the video advertisement, parse the received first set of information to obtain the video advertisement and associated pixel firing information, provide the video advertisement to a video player on the client device, and fire a first pixel upon occurrence of a first predefined event associated with the video advertisement.