Client-Side Ad Visibility Tracking via Draw-Count Metrics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current online advertising methods rely on HTTP requests to track advertisement views, which fail to accurately determine if advertisements are displayed in a visible area of client device screens, leading to potential fraudulent activity and incorrect payment to advertisers.

Innovation Solution

Implementing client-side code that uses window-draw-count properties, transparent pixel images, and document-draw-count metrics to determine if an advertisement is visible within a client application, ensuring accurate view-counts by assessing screen, window, and document drawing operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If HTTP requests are used to track advertisement views, then the tracking process is simple, but the accuracy of determining whether advertisements are actually visible is poor

Engineering Contradiction:
Improvetracking process complexityVSAvoidadvertisement visibility accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent introduces an intermediary measurement mechanism (transparent pixel images and draw-count properties) between the advertisement delivery system and the visibility determination system. This intermediary layer tracks drawing operations and visibility states without complicating the core HTTP-based advertisement delivery process, thereby maintaining simplicity while improving measurement accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical/simple HTTP request counting method with a more sophisticated measurement system that leverages browser rendering mechanics (draw-count properties and transparent pixel detection). This substitution transitions from a purely network-based tracking approach to one that incorporates client-side rendering information, improving accuracy without significantly increasing overall system complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of manufacture

If simple HTTP request counting is used, then implementation is easy, but fraudulent activity cannot be detected

Engineering Contradiction:
Improveimplementation easeVSAvoidanti-fraud capability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent implements preliminary tracking by embedding transparent pixel images and draw-count measurement mechanisms before advertisement delivery. This preliminary setup captures visibility information at the source, enabling fraud detection before compensation is triggered, while maintaining ease of implementation through straightforward integration into existing advertisement workflows.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If comprehensive visibility tracking is implemented, then measurement accuracy improves, but system complexity increases

Engineering Contradiction:
Improvevisibility measurement accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent enables the browser and advertisement elements to self-report visibility information through automatic tracking of draw-count properties and transparent pixel detection. This self-service mechanism eliminates the need for complex external monitoring systems, as the visibility data is generated and reported automatically by the components themselves, maintaining relative system simplicity while achieving comprehensive measurement accuracy.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9805377B2Unified content visibility
Publication Date: 2017.10.31 COMSCORE INC
  • US9805377B2 patent drawing
  • US9805377B2 patent drawing
  • US9805377B2 patent drawing

AI summary

Methods, systems, and computer-readable media for determining the visibility of downloaded objects, such as electronic advertisements, on a client device screen comprise consulting one or more draw-count properties associated with the advertisement, such as screen-draw-count, window-draw-count, or document-draw-count properties; and determining whether the advertisement was likely visible based on the one or more draw-count properties. A plurality of objects, such as transparent pixel images may also be placed on or around the advertisement and their draw-counts compared. If only some of the transparent pixel images have non-zero draw-counts, then it may be inferred that only a portion of the advertisement was visible on the client device screen.