Publisher Ad Landing-Page Verification for Reliable Blocking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing advertisement distribution systems struggle to enforce publisher block requests effectively, particularly when advertisers fail to declare all landing pages associated with their advertisements, leading to ineligible ads being presented on publisher resources.
Innovation Solution
A system that combines declared and fetched network locations to create a composite set for enforcing publisher block requests, using a virtual machine to simulate user interactions and log actual landing pages, ensuring accurate blocking of ineligible advertisements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the system relies solely on declared landing pages provided by advertisers, then the device complexity is reduced, but the reliability of blocking ineligible advertisements deteriorates because advertisers may fail to declare all landing pages
Solution Approach 1:
The patent introduces a virtual machine as an intermediary component that automatically fetches and verifies landing pages. This virtual machine acts as a mediator between the advertisement distribution system and the advertiser-declared landing pages, automatically navigating to each declared landing page to verify its authenticity and collect additional landing pages through simulated user interactions, thereby resolving the contradiction between system simplicity and blocking reliability
Solution Approach 2:
The system performs preliminary actions by proactively fetching and verifying landing pages before advertisements are served to users. The virtual machine预先 (in advance) navigates to declared landing pages, verifies their legitimacy, and collects additional landing pages before the advertisement distribution process begins, ensuring that all landing pages are known and can be properly blocked if ineligible
2Reliability
If the system uses virtual machines to simulate user interactions and fetch additional landing pages, then the blocking reliability improves, but the device complexity and processing time increase
Solution Approach 1:
The virtual machine operates autonomously to fetch and verify landing pages without requiring manual intervention. It automatically simulates user interactions, navigates through redirects, and collects landing page information on its own, making the system self-sufficient in verifying advertisement destinations and reducing the need for complex manual verification processes
Solution Approach 2:
The system creates virtual copies of user browsers through virtual machines that simulate real user interactions. These virtual browser instances replicate user behavior to navigate advertisements and landing pages, allowing the system to verify landing pages without affecting actual users or requiring complex human verification processes
3Reliability
If the system fetches and verifies all possible landing pages before advertisement distribution, then the blocking reliability improves, but the processing time and productivity are reduced
Solution Approach 1:
The system performs landing page verification in advance before advertisement distribution begins. By pre-fetching and validating all landing pages associated with advertisements, the system ensures that blocking decisions can be made immediately when advertisements are requested, rather than delaying distribution to perform verification in real-time
Solution Approach 2:
The system performs more verification than strictly necessary by using virtual machines to simulate complete user interactions and fetch all possible landing pages through redirects. This excessive verification ensures comprehensive blocking reliability by catching all potential ineligible landing pages, even those that require multiple redirects to reach
Data Source
AI summary
Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for enforcing publisher content item block requests. In one aspect, a method includes receiving a set of declared network locations for a content item and rendering the content item. A request is initiated for a resource that is referenced by the content item, and network locations fetched in response to the request are logged. A composite set of network locations that includes the fetched network locations and declared network locations is generated. The composite set of network locations is used to enforce publisher block requests.


