Server-Side Pre-Rendering for Ad Content Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for displaying pages with ads result in slow load times and are vulnerable to ad blockers, leading to decreased user engagement and lost revenue for publishers, as they rely on dynamic JavaScript calls that increase data costs and latency.
Innovation Solution
Generating and serving pre-rendered pages that incorporate ad content and third-party verification tags directly, reducing the need for dynamic calls and improving load times while preventing ad blockers from interfering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dynamic JavaScript calls are used to load ads from ad servers, then ads can be displayed in predetermined locations, but page load time increases and user experience deteriorates
Solution Approach 1:
The patent pre-loads ad content and third-party verification tags into the page before it is served to the client. By performing the ad loading action in advance on the server side, the ads are already available when the page is delivered, eliminating the need for subsequent dynamic JavaScript calls and reducing page load time.
Solution Approach 2:
The patent extracts the ad loading process from the client-side JavaScript execution and moves it to the server-side page generation phase. This separation removes the dependency on client-side dynamic calls and ad blockers, ensuring ads are loaded reliably without impacting user experience.
2Adaptability or versatility
If dynamic JavaScript calls are used to load ads, then ads can be dynamically served, but ad blockers can interfere and prevent ad loading
Solution Approach 1:
The patent introduces an intermediary process on the server side that handles ad content retrieval and embedding before page delivery. This intermediary approach bypasses client-side ad blockers by completing the ad loading process server-side, while still maintaining the ability to dynamically serve appropriate ads based on user context.
3Reliability
If multiple ad calls are made from client, then ad impressions can be generated, but data costs increase for mobile users
Solution Approach 1:
The patent merges multiple ad loading operations into a single server-side process. Instead of making separate JavaScript calls for each ad from the client, all ad content is retrieved and embedded in one batch during page generation, reducing the total number of network requests and data consumption for mobile users.
4Reliability
If dynamic JavaScript ad calls are used, then ads can be loaded, but page performance slows down
Solution Approach 1:
The patent performs ad content retrieval and page assembly in advance on the server side before the page is sent to the client. This preliminary action eliminates the need for time-consuming JavaScript execution and multiple network requests at the client side, significantly improving page rendering performance.
Data Source
AI summary
An identifier associated with a page request is received. Publisher content that corresponds to the identifier is obtained. A content element that is associated with a target group with which the page request is associated is dynamically determined. An at least partially pre-rendered page that incorporates corresponding code to include content associated with the dynamically determined content element along with the publisher content is generated. The at least partially pre-rendered page is provided in response to the page request.