Server-to-Server Tracking Event Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current event tracking systems for content providers face inaccuracies and discrepancies due to direct data reliance from client devices, leading to inconsistent performance reports across different content delivery services.
Innovation Solution
Integrating two server systems where a client device transmits events to a first server system for validation and reporting, which then sends consistent event messages to a second server system, offloading processing and enhancing data richness, thereby simplifying client device rendering logic and improving reporting accuracy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If tracking services rely on data directly from client devices to generate reports, then the system can operate with simpler architecture, but the data accuracy and reliability of performance reports deteriorate
Solution Approach 1:
The patent introduces a content delivery service server as an intermediary between the client device and the tracking service. The server receives events from the client device, validates them against stored provider data, and then forwards validated events to the tracking service. This intermediary layer ensures that only accurate, validated events are reported, resolving the contradiction by maintaining system simplicity while improving data accuracy through server-based validation.
2Adaptability or versatility
If multiple content delivery services are used to distribute content items, then the coverage and delivery capability improve, but the complexity of tracking and reporting performance across services increases
Solution Approach 1:
The patent implements a universal tracking approach where a single tracking service can aggregate performance data from multiple content delivery services. The server system validates events from various delivery services using common validation logic and stores provider data that can be referenced across different services. This allows one tracking system to handle multiple delivery services uniformly, improving coverage while managing complexity through standardization.
3Power
If client devices perform event validation and reporting logic, then the processing burden on servers is reduced, but the rendering logic complexity on client devices increases
Solution Approach 1:
The patent extracts the validation and reporting logic from the client device and relocates it to the content delivery service server. The client device simply transmits events to the server, which then performs validation against stored provider data and handles the reporting to tracking services. This extraction reduces client device complexity while giving servers the processing burden, resolving the contradiction by centralizing intelligent processing where it can be most effectively managed.
Data Source
AI summary
Techniques for integrating two server systems are provided. A first server system receives, from a first computing device, provider data generated by a third-party tracking service. The first server system stores association data that associates the provider data with one or more content items. After storing the association data, the first server system receives, from a second computing device, a message that includes a first identifier and that indicates an event and a content item. In response to receiving the message, the first server system determines whether to report the event to the third-party tracking service. If so, the first server system determines a second identifier based on the first identifier, retrieves, based on the association data and the content item, the provider data that is associated with the content item, and transmits, over a network to the third-party tracking service, the second identifier and the provider data.