Client-Generated Click Identifiers for Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for reducing latency in online network traffic, particularly when tracking clicks on content items like advertisements, introduce delays due to the need for client devices to send requests to click servers and receive redirects before navigating to landing pages, especially in low-bandwidth connections.
Innovation Solution
The system generates a click identifier at the client device upon interaction with a content item and transmits it to a click server using an asynchronous request, while simultaneously navigating to the landing page, thereby avoiding the latency caused by waiting for server responses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the client device sends a request to the click server and waits for a redirect before navigating to the landing page, then the click tracking is accurate, but the latency increases and load times are delayed
Solution Approach 1:
The client device generates the click identifier locally before navigating to the landing page, and transmits it via an asynchronous beacon request. This preliminary action eliminates the need to wait for server confirmation before proceeding to the landing page, thus reducing latency while maintaining tracking accuracy.
Solution Approach 2:
The click tracking function is extracted from the synchronous navigation flow and implemented as an asynchronous beacon request. This separates the tracking operation from the critical navigation path, allowing the landing page to load without waiting for click tracking confirmation, thereby resolving the contradiction between reliable tracking and low latency.
2Loss of time
If the client device transmits the click identifier asynchronously while simultaneously navigating to the landing page, then the latency is reduced, but the complexity of coordinating multiple requests increases
Solution Approach 1:
The beacon interface acts as an intermediary mechanism that simplifies asynchronous communication. The client device uses the beacon interface to transmit the click identifier independently of the navigation request, eliminating the need for complex coordination logic while maintaining low latency.
3Ease of manufacture
If the system uses traditional synchronous click tracking methods, then the implementation is simple, but the load times are delayed especially in low-bandwidth environments
Solution Approach 1:
The navigation to the landing page continues without interruption while the click identifier is transmitted asynchronously via beacon. This continuous execution of useful actions (navigation and tracking) simultaneously resolves the contradiction between simple implementation and fast load times.
Data Source
AI summary
Systems and methods of reducing latency in online network traffic are provided. The system can include a processor and a memory couple to the processor. The memory stores computer-executable instructions, which when executed by the processor, cause the processor to identify an indication of an interaction with a content item presented within a content slot of an information resource, generate a click identifier that uniquely identifies the interaction, transmit a first request comprising a click resource link including the click identifier to a click server, and transmit a second request to access the landing page of the content item independent of transmitting the first request. The second request comprises a generated resource link that identifies a resource identifier of the landing page of the content item and the click identifier.