Prefetching User Profile Data to Reduce Web Page Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional advertising systems face latency issues due to the inability to personalize web pages in real-time, as advertisers are only aware of user requests after the page is rendered, and retrieving user profile information from remote locations adds significant delay, which can lead to increased bounce rates and reduced conversion rates, especially for smaller experience providers lacking infrastructure for user tracking and data storage.
Innovation Solution
Sending a notification to the experience provider before a user arrives allows for prefetching and storing user profile information in a more accessible location, enabling customization of the web page experience without adding latency, even for providers without backend infrastructure or accumulated data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If profile information is retrieved from a remote data storage location after user arrival, then user profile data can be obtained for customization, but significant latency is added to the process
Solution Approach 1:
The system sends a notification to the experience provider before the user arrives at the resource, allowing the provider to retrieve and store profile information in advance. This preliminary action eliminates the latency that would otherwise occur when retrieving profile data from remote storage after user arrival, as the data is prepared and available locally when the user requests the resource.
2Adaptability or versatility
If web page customization is performed after user request, then personalized content can be delivered, but the time between ad click and content viewing increases
Solution Approach 1:
The experience provider receives a notification about the user's impending arrival and performs customization actions in advance by retrieving and storing relevant profile information locally. When the user requests the resource, the customized content can be delivered immediately without the delays associated with real-time data retrieval and processing.
3Device complexity
If profile information is stored in remote locations, then data can be centralized and managed, but retrieving and delivering this information becomes time-consuming
Solution Approach 1:
The system architecture allows profile information to be stored centrally in remote locations while enabling advance retrieval and local storage when a user's visit is anticipated. The notification mechanism triggers pre-fetching of profile data to the experience provider's local storage, so that when the user arrives, the information is immediately available without remote access delays.
Data Source
AI summary
Methods described herein include prefetching information for a future visitor to a webpage or other resource. Prefetching the information can allow a provider to customize the webpage or resource with reduced latency. The methods can include notifying an experience provider associated with an advertisement prior to the user requesting the webpage or other resource. The notification can provide identification information corresponding to the client device or user. The notification also indicates that the client device or a user is about to be directed to the webpage or other resource. The notification can allow for retrieval of profile information associated with the identification information prior to the direction of the client device to the webpage or other resource.