Server-Side Ad Injection for Faster Page Loading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional web page loading is slow due to the client-side execution of ad scripts and interactions with multiple third-party servers, which can be blocked by ad blockers, and publishers face challenges in migrating away from content management systems (CMS) that integrate ad functions.
Innovation Solution
Implementing a system that composes and serves a quick-loading, user-specific web page by parsing publisher content, selecting and optimizing ads on the server side, and stripping out ad-related scripts, allowing for real-time optimization and A/B testing to enhance user experience and ad relevance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If ad scripts are executed on the client side to dynamically inject ads, then ad functionality is achieved, but page loading speed deteriorates
Solution Approach 1:
The patent inverts the conventional ad injection approach by moving ad script execution from the client side to the server side. The server executes ad scripts, retrieves ad content, and injects it into the HTML before sending it to the client. This inversion eliminates the need for client-side script execution during page loading, thereby improving page loading speed while maintaining ad functionality.
Solution Approach 2:
The patent implements preliminary action by pre-executing ad scripts and pre-injecting ad content into the HTML on the server side before the page is sent to the client. This ensures that all ad-related operations are completed in advance, eliminating delays during client-side execution and improving overall page loading speed.
2Adaptability or versatility
If third-party ad servers are called to dynamically inject ads, then ad relevance is improved, but the number of server interactions increases
Solution Approach 1:
The patent merges the ad serving functionality with the content management system by implementing a unified server-side ad injection mechanism. Instead of making separate calls to third-party ad servers, the system integrates ad selection and injection into the existing content delivery workflow, reducing the number of server interactions while maintaining ad relevance through server-side ad selection based on user data.
Solution Approach 2:
The patent introduces an intermediary ad server that consolidates multiple third-party ad server interactions into a single interface. The unified ad server receives ad requests, selects appropriate ads based on user data, and returns the selected ads to the content management system, thereby reducing the number of direct interactions with multiple third-party servers while maintaining ad relevance.
3Ease of operation
If ad blockers block calls to third-party servers, then user control is improved, but ad delivery is disrupted
Solution Approach 1:
The patent extracts ad-related script execution and ad content retrieval from the client side and relocates them to the server side. By removing ad scripts from the client-side HTML, the system eliminates the attack surface that ad blockers exploit, allowing ads to be delivered reliably through server-side injection while preserving user control over ad blocking functionality.
4Reliability
If publishers migrate away from CMS systems with integrated ad functions, then ad performance is improved, but operational complexity increases
Solution Approach 1:
The patent implements a universal server-side ad injection framework that can be integrated with existing CMS systems without requiring migration. The framework provides multi-functional capabilities including ad selection, ad injection, and ad performance tracking within a single server-side component, allowing publishers to improve ad performance while maintaining their existing CMS infrastructure and operational workflows.
Data Source
AI summary
A request for a page is received. A processor is used to provide an optimized version of the page at least in part by determining dynamically an optimized content element for the page based at least in part on a user attribute associated with the request and content performance data generated based at least in part on testing of alternative versions of the page with respect to other users having the user attribute. The provided optimized version of the page is selected from the alternative versions of the page based on the content performance data indicating that the selected version of the page is optimized for the other users having the user attribute.