Declarative Page Tracking for TV Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional analytics tracking techniques are ill-suited for apps that provide content pages without page-specific imperative code, such as Apple TV apps, as they require complex and error-prone coding to access page-specific information, making page tracking inefficient and undesirable.
Innovation Solution
Implementing declarative page tracking using tracking tags within declarative pages to specify analytics tracking parameters, allowing page-generic imperative code to access and send page-specific information to analytics systems, reducing the need for extensive coding and simplifying the process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If conventional imperative code is used for analytics tracking in apps with declarative pages, then page-specific information can be accessed, but the coding becomes complex and error-prone
Solution Approach 1:
The patent introduces a mediator component that bridges the declarative page markup and the analytics system. This mediator automatically extracts page-specific information from the declarative code and formats it for analytics tracking, eliminating the need for complex imperative code while maintaining tracking accuracy.
Solution Approach 2:
The declarative page code is enhanced to include built-in tracking capabilities that automatically capture and report page-specific information. The pages themselves serve their own tracking needs through embedded attributes and events in the declarative markup, without requiring external imperative code to intervene.
2Productivity
If page-specific imperative code is implemented for each page, then tracking efficiency improves, but the maintenance burden and error potential increase
Solution Approach 1:
The patent creates a universal tracking framework that works across all declarative pages in the app. A single set of analytics configuration and event handlers can track multiple page types by leveraging the common structure of declarative markup, eliminating the need for separate imperative code for each page while maintaining efficient tracking.
Solution Approach 2:
The tracking functionality is segmented into distinct, reusable components: page configuration attributes, event definitions, and analytics reporting mechanisms. This segmentation allows the system to efficiently process tracking data from different pages through standardized routines without requiring complete imperative code implementations for each page type.
3Ease of operation
If declarative code without imperative code is used, then app simplicity is maintained, but page tracking capability is lost
Solution Approach 1:
The patent merges analytics tracking functionality directly into the declarative page markup by incorporating tracking attributes and event handlers within the same declarative code structure. This integration allows the app to maintain its simplicity and declarative nature while simultaneously capturing comprehensive tracking information without requiring separate imperative code files or complex configurations.
Data Source
AI summary
Techniques for tracking pages accessed by an app executed to display multiple pages on a display. A computing device loads the app and present content from the app on a display. The computing device is configured to display individual pages of the app using declarative code specifying appearances of the pages. The computing device is configured to respond to events using page-generic imperative code. The computing device renders a page on the display using the declarative code of the page and identifies a tracking tag in the declarative code of the page. Based on identifying the tracking tag, the computing device sends a message to an analytics system identifying a page access.