Embedded Host-Guest Monitoring for Nested Content Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for verifying compliance of nested content loaded onto webpages or applications from external servers lack comprehensive data collection, leading to incomplete verification of execution sessions, especially regarding brand safety, visibility, and fraud detection.
Innovation Solution
A system that employs both host monitoring code embedded in the webpage or application and guest monitoring code in the nested content to collect and combine session data, providing a comprehensive view of the execution session by aggregating data from different contexts, and initiating actions based on compliance with serving rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If only guest monitoring code is used in nested content, then implementation is simple, but data collection is incomplete leading to poor verification accuracy
Solution Approach 1:
The monitoring system is segmented into two distinct components: host monitoring code embedded in the main webpage/application and guest monitoring code embedded in the nested content. Each segment collects data from its specific context, with the host monitoring code capturing host environment data and the guest monitoring code capturing nested content execution data. This segmentation allows comprehensive data collection while maintaining implementation simplicity for each individual component.
Solution Approach 2:
The guest monitoring code is nested within the nested content (iframe), which itself is nested within the host webpage. This nested structure allows the monitoring system to operate at multiple levels - the host monitoring code operates at the parent level while the guest monitoring code operates within the nested iframe context, enabling collection of data that would be inaccessible to a single-level monitoring approach.
2Quantity of substance
If host monitoring code is embedded in webpage, then extensive session data can be collected from beginning, but data from guest monitoring code becomes unavailable to host code
Solution Approach 1:
A server acts as an intermediary that receives data from both the host monitoring code and the guest monitoring code separately. The server combines these data sources to create a unified view of the execution session. This intermediary approach allows both monitoring codes to operate independently in their respective contexts while ensuring that data from both sources is preserved and integrated, preventing information loss that would occur if direct access between host and guest codes was attempted.
3Reliability
If comprehensive data collection is implemented using both monitoring codes, then verification of brand safety and fraud detection improves, but system complexity increases
Solution Approach 1:
The monitoring system is divided into specialized segments: host monitoring code for collecting host environment data and guest monitoring code for collecting nested content execution data. Each segment focuses on specific verification aspects, allowing comprehensive brand safety and fraud detection through combined data while keeping individual implementation tasks manageable and less complex.
Data Source
AI summary
A computerized method of content verification comprising using a server for receiving a first data from a host monitoring code embedded in a webpage or an application loaded from a content server and executed by a client device, the host monitoring code is executed by the client device during an execution of the webpage or the application which further embeds nesting element(s) for loading nested content from nested content server(s), the first data is indicative of the execution, receiving a second data indicative of the execution from a guest monitoring code embedded in the nested content, combining the first data and second data for compliance verification of the execution with one or more rules associated with the nested content and initiating action(s) according to the verification. Wherein the first data is not available to the guest monitoring code and the second data is not available to the host monitoring code.