Certified Server-Side Partner Plug-Ins for Analytics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web analytics systems require significant investment and delay due to re-tagging for real-time data collection, which hampers sales cycles and increases costs for partners and co-customers.
Innovation Solution
The implementation of analytics plug-ins, such as web-beacon plug-ins and server-side partner plug-ins, which are certified to comply with specific criteria, allowing them to integrate with core analytics components while respecting privacy and data integrity, enabling partners to collect data without re-tagging and ensuring data quality and privacy protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If partners use their own web-beacon to collect real-time data, then data collection capability is improved, but implementation cost and time increase significantly due to re-tagging requirements
Solution Approach 1:
The analytics provider's core JavaScript file acts as an intermediary that enables partners to collect real-time data without direct re-tagging. The partner plug-in code integrates with this core file, allowing data to flow from the vendor's website through the analytics provider to the partner, eliminating the need for partners to implement their own separate web-beacons while maintaining real-time data collection capability.
Solution Approach 2:
The core JavaScript file serves multiple functions simultaneously: it enables the analytics provider to collect data for the vendor while also providing a platform for partner plug-ins to collect data for their own analytical purposes. This multi-functionality allows partners to access real-time data through the existing analytics infrastructure rather than requiring separate implementation.
2Reliability
If partners implement re-tagging for real-time data collection, then data access is improved, but implementation cost increases
Solution Approach 1:
The partner plug-in code is merged with the analytics provider's core JavaScript file, combining the vendor's analytics requirements with the partner's data collection needs into a single integrated solution. This merging eliminates the need for separate re-tagging implementations while providing both the vendor and partner with their required data access capabilities.
Solution Approach 2:
The core JavaScript file serves as an intermediary layer that provides data access to both the analytics provider and partner plug-ins. Instead of partners directly implementing web-beacons on vendor websites, they access data through this intermediary layer, significantly reducing implementation costs while maintaining full data access capability.
3Reliability
If multiple web-beacons are used for data collection, then data coverage is improved, but system complexity increases
Solution Approach 1:
The analytics system is segmented into distinct functional components: the vendor's website, the analytics provider's core JavaScript file, and partner-specific plug-in code. Each component has a specific responsibility, and they interact through defined interfaces. This segmentation allows comprehensive data coverage while managing complexity through clear separation of concerns.
Solution Approach 2:
The core JavaScript file provides a universal platform that handles data collection for multiple purposes simultaneously. Partner plug-ins are designed to work within this universal framework, allowing comprehensive data coverage across different partner needs without requiring separate complex systems for each data collection objective.
Data Source
AI summary
Tools and techniques are provided to allow partners of analytics providers and others who use web-beacons to submit plug-ins for scrutiny, and for the plug-in to either be refused or else to be certified for use in a core JavaScript file, data engine, or similar component. Analytics providers and others may also write plug-ins. Certified plug-ins are executed in response to page loads, visitor clicks, and other visitor and programmatic actions at a website that has been tagged by the analytics provider's web-beacon, without requiring re-tagging of the website with a separate web-beacon for the partner. This allows the partner to obtain analytics data by piggybacking on the analytics provider, without re-tagging, and without compromising the availability and accuracy of the analytics data already being gathered. To be certified, web-beacon plug-ins must satisfy specific criteria as to their privacy protection, size, behavior, namespace, and the like.