Event Stream Data Collection via Server-Side Schema Application
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web analytics face challenges in controlling data collection, security, and latency due to third-party code integration for clickstream data, leading to inefficient data replication and potential malicious attacks.
Innovation Solution
Implementing a method to collect and distribute event stream data in real-time by applying a schema to incomplete metadata records, reducing data transmission, eliminating third-party code from client applications, and maintaining data serialization on a server platform for efficient data distribution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party code is integrated into client applications to collect clickstream data, then data collection capability is improved, but security vulnerability and latency increase
Solution Approach 1:
The patent extracts the data collection functionality from third-party code embedded in client applications and consolidates it into a centralized server platform. The client application now contains only native code that collects event stream data and sends it to the server, eliminating the security vulnerabilities associated with third-party code execution while preserving data collection capabilities through the centralized platform.
2Adaptability or versatility
If multiple third parties provide code for placement on the website, then data collection coverage is improved, but latency and navigation speed deteriorate
Solution Approach 1:
The patent merges multiple data collection functions into a single centralized server platform that receives event stream data from the client application. Instead of executing multiple third-party code snippets that each perform data collection, the system uses one native code implementation that sends comprehensive event data to the server, where multiple third parties can access the same data stream without adding latency to the client-side execution.
3Adaptability or versatility
If third parties independently collect data from the website, then data accessibility is improved, but data replication and latency increase
Solution Approach 1:
The patent introduces a centralized server platform as an intermediary between the client application and multiple third parties. The server receives event stream data once from the client and then distributes it to multiple third parties according to their data requests. This eliminates the need for each third party to independently collect data from the client, thereby reducing redundant data replication and the associated latency while maintaining data accessibility for all third parties.
Data Source
AI summary
As a user navigates a website and/or mobile application, events may be captured. Example events include user interactions, return of information from services, and recommendation calls. Event stream data associated with the event may be collected once and provided to a server platform via a streaming data service. The event stream data may be converted to an appropriate structure for storage at the server platform by applying a schema. The schema applied may take advantage of a format in which the event stream data is captured at the client application. This enables the client application to provide minimal data to the server platform (e.g., an incomplete record) and the server platform to complete the record according to the schema. The event stream data may be saved internally within a database of the server platform, and distributed to one or more third parties in a compatible format.