Cross-Domain Tracking via Beacon Match-ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mechanisms, such as cookies, face limitations in tracking user activities across different internet domains due to restricted access within the same domain, making it difficult to manage and analyze cross-domain user interactions effectively.
Innovation Solution
Implementing a beacon system that includes a Match-ID, which is a unique identifier provided to client devices across domains, allowing content servers to annotate logs and track user activities across multiple domains by linking requests to a beacon server, enabling cross-domain activity tracking and analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cookies are used for tracking user activities, then tracking within the same domain is enabled, but tracking across different domains is restricted
Solution Approach 1:
The patent introduces a domain visitor identifier ( Match-ID) as an intermediary tracking mechanism that operates independently of domain-specific cookies. This Match-ID is embedded in beacons and can be recognized across multiple domains, serving as a mediator that bridges the tracking gap between different domains while maintaining the reliability of user activity tracking.
2Measurement precision
If domain-specific tracking mechanisms are used, then tracking precision within a domain is maintained, but cross-domain user activity analysis becomes difficult
Solution Approach 1:
The patent creates a universal tracking identifier (Match-ID) that serves multiple functions: it can be used within a single domain like a cookie, but also functions across multiple domains to track user journeys. This multi-functional identifier prevents information loss by maintaining consistent user identification regardless of domain boundaries, enabling comprehensive cross-domain user behavior analysis.
3Ease of manufacture
If traditional cookie-based tracking is implemented, then implementation simplicity is maintained, but cross-domain tracking effectiveness is reduced
Solution Approach 1:
The patent segments the tracking functionality into two parts: domain-specific cookies for local tracking and cross-domain beacons with Match-ID for broader tracking. This segmentation allows the system to maintain the simplicity of cookie-based tracking within domains while adding cross-domain capability through beacons, thus improving cross-domain tracking effectiveness without completely redesigning the existing tracking infrastructure.
Data Source
AI summary
A device, system, and method are directed towards managing and tracking of cross-domain user activities through use of a beacon. As a user of a client device requests content from different domain services managed by a common entity, they may receive a Uniform Resource Locator (URL) to a beacon in at least one of the different domains. In one embodiment, the beacon is a single pixel image. The client device may also receive a Match-ID. A beacon server in one of the other domains may receive the request for the beacon, and store in a domain log the Match-ID, and other information about the client device, which domain service provided the URL, and/or other related user activities. The different domain logs may then be employed for use in searching for matching Match-IDs, joining common user or client device activities, and for tracking other cross-domain user activities.