Browser-Specific Tracking Tag Selection for Legacy Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Websites face challenges in determining the success of user experience and sales conversions due to compatibility issues between older and newer web browsers, leading to errors and performance problems caused by mismatched tracking tags.
Innovation Solution
The system determines the version of a web browser and deploys either a modern or legacy tracking tag to ensure optimal compatibility and performance, using a data management system that selects the appropriate version based on the browser's capabilities, maintaining different versions of the tracking tag for legacy and modern browsers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single modern tracking tag is deployed for all browsers, then analytics functionality is improved, but compatibility with legacy browsers deteriorates causing errors and performance issues
Solution Approach 1:
The patent implements different versions of tracking tags tailored to specific browser types. Modern browsers receive the full-featured tracking tag with advanced analytics capabilities, while legacy browsers receive a simplified version with reduced functionality. This local differentiation ensures each browser type receives the appropriate level of complexity, resolving the contradiction between advanced analytics and broad compatibility.
Solution Approach 2:
The tracking tag is segmented into multiple versions based on browser capabilities. The system divides the single tracking tag concept into distinct variants: a modern browser version with complete analytics features and a legacy browser version with essential functionality only. This segmentation allows the system to maintain reliable analytics where possible while ensuring compatibility where needed.
2Adaptability or versatility
If multiple versions of tracking tags are maintained for different browsers, then browser compatibility is improved, but system complexity increases
Solution Approach 1:
The patent introduces a browser detection intermediary that automatically identifies the user's browser type and selects the appropriate tracking tag version. This intermediary layer handles the complexity of version management by detecting browser capabilities and routing users to the correct tag version, thereby maintaining browser compatibility while shielding the system from the burden of manually managing multiple versions.
Solution Approach 2:
The system implements self-service through automatic browser detection and version selection. Rather than requiring manual configuration or user intervention to determine the appropriate tracking tag version, the system automatically detects the browser type and serves the correct version. This self-service mechanism reduces the operational complexity of managing multiple tracking tag versions.
3Measurement precision
If tracking tag version is determined manually, then accuracy is improved, but user experience deteriorates due to delays
Solution Approach 1:
The patent implements preliminary browser detection that occurs automatically as part of the page load process. The system performs browser version detection in advance by analyzing user agent strings or other browser identifiers before the tracking tag needs to execute. This preliminary action ensures accurate browser identification without adding noticeable delays to the user experience, as the detection is integrated into the initial page rendering sequence.
Data Source
AI summary
The subject technology receives, in a request, information related to a version of a web browser of a client device. The subject technology determines, using the information related to the version of the web browser, a version of a tracking tag to provide to the client device. The subject technology selects the version of the tracking tag from among different versions of the tracking tag, each version of the tracking tag comprising different code from code of other versions of the tracking tag. The subject technology receives the version of the tracking tag from cloud storage. The subject technology sends the version of the tracking tag to the client device.