Browser Tab Clickstream Tracking via Unique Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional clickstream tracking techniques fail to accurately account for activity across multiple browser tabs, leading to inaccuracies and omissions in user behavior analysis, which can compromise the quality of analytics and security measures such as fraud prevention and user authentication.
Innovation Solution
A system that tracks each browser tab using a unique tab identifier stored in an event log, allowing for accurate tracking and analysis of user behavior across multiple tabs, including timestamps, URLs, and clickstream data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional clickstream tracking techniques are used, then the implementation is simple, but the accuracy of user behavior analysis deteriorates due to inability to account for activity across multiple browser tabs
Solution Approach 1:
The patent segments the browsing session into multiple tab-specific tracking streams by assigning unique identifiers to each tab. This allows the system to separately track and analyze user behavior in each tab while maintaining overall session context, thereby improving measurement precision without requiring a complete redesign of the tracking architecture.
Solution Approach 2:
The patent introduces tab identifiers and event logs as intermediary data structures that mediate between the browser tabs and the analysis system. These intermediaries carry tab-specific information through the system, enabling accurate attribution of events to specific tabs while keeping the overall system architecture relatively simple.
2Reliability
If tab-specific tracking is implemented, then the accuracy of distinguishing legitimate and fraudulent activity improves, but the complexity of data storage and management increases
Solution Approach 1:
The event log is segmented into tab-specific event streams, with each event record containing a tab identifier. This segmentation allows the system to reliably trace user actions to specific tabs while maintaining a unified storage structure, improving security analysis reliability without proportionally increasing storage complexity.
Solution Approach 2:
The event log structure is designed to be universal, handling both tab-specific events and overall session events in a unified format. This multi-functional design allows the same storage mechanism to serve multiple purposes: tracking individual tab behavior, analyzing cross-tab patterns, and maintaining session context, thereby improving reliability without linearly increasing management complexity.
3Loss of information
If comprehensive clickstream data is collected across all tabs, then the quality of analytics improves, but the amount of data storage requirements increase
Solution Approach 1:
The patent merges tab-specific event data with overall session context in a unified event log. By combining these data streams with proper tab identifier attribution, the system achieves complete clickstream data collection without requiring separate storage systems for each tab, thereby improving information completeness while controlling storage volume through efficient data consolidation.
Data Source
AI summary
System and methods track events associated with web browser activity along with corresponding browser tab identifiers. A web page is loaded in a browser tab based on a request to a Uniform Resource Locator (URL). A time is identified, and it is determined that a predetermined time interval has elapsed. A storage mechanism is queried to determine whether an event log stored to the storage mechanism contains a stored tab identifier for the browser tab. If the tab identifier is not stored to the event log, then a tab identifier is stored to the event log, mapped to the time and the URL. If the event log contains the stored tab identifier for the tab, then the event log is updated to include the time mapped to the tab identifier. The URL may also be updated if applicable. The event log is transmitted to a server computer for further analysis.