Supplemental Analysis Module for Mobile Ad Engagement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for evaluating user engagement with mobile advertising are inaccurate and inefficient due to non-standardized event identification and human intervention, leading to subjective and incomplete data analysis.
Innovation Solution
Incorporating supplemental analysis modules into invitational content that operate on end-user devices to collect and standardize event data, allowing for objective and comprehensive user engagement reporting without interfering with existing systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If human operators review and infer conclusions from available data, then subjective analysis can be performed, but measurement precision and reliability deteriorate due to subjectivity and potential errors
Solution Approach 1:
The patent introduces an intermediary component - the supplemental analysis module with standardized event tagging system - that sits between the raw user engagement data and the human operator. This module automatically tags and categorizes events using standardized identifiers, providing objective, structured data to operators while eliminating subjectivity in the initial data processing stage. The standardized events serve as a mediator that translates diverse user interactions into consistent, analyzable formats.
2Adaptability or versatility
If different mobile advertising units generate differing sets of data, then customization to specific unit requirements is achieved, but comparison between different advertisements becomes difficult
Solution Approach 1:
The patent implements a universal standardized event tagging system that can be applied across all mobile advertising units regardless of their specific functions or content. The system defines a common set of event identifiers (such as CLICK, VIEW, IMPRESSION) that work universally across different ad units, campaigns, and platforms. This universal framework enables direct comparison between different advertisements while still allowing each unit to capture its specific engagement metrics through the same standardized lens.
Solution Approach 2:
The patent changes the parameter structure of event data by transforming diverse, unit-specific event descriptions into standardized event parameters with consistent identifiers, categories, and attributes. Instead of allowing each advertising unit to define its own proprietary event schemas, the system imposes a standardized parameter structure that includes event type, timestamp, user identifier, and engagement metrics. This parameter standardization enables apples-to-apples comparisons across different ad units while preserving the essential characteristics of each engagement event.
3Reliability
If a significant amount of human resources are allocated to data collection and analysis, then comprehensive review is possible, but productivity and efficiency deteriorate
Solution Approach 1:
The patent implements a self-service automated analysis system where the supplemental analysis module performs data collection, event tagging, categorization, and initial analysis without requiring extensive human intervention. The system automatically monitors user interactions, tags events with standardized identifiers, aggregates data by campaign and ad unit, and generates structured reports. This automation eliminates the need for manual data review while maintaining comprehensive analysis coverage, dramatically improving productivity without sacrificing reliability.
Data Source
AI summary
Method and arrangements are provided to generate supplemental analysis modules for items of invitational content, the modules including an event dictionary and event handlers. Such modules are configured to collect event information at an end user device associated with the operation of an item of invitational content, determine whether the event information corresponds to an entry in the event dictionary, and, upon determining that the event information corresponds to an entry, identify an event handler corresponding to the entry and routing the event information to the event handler, where the event handler is configured for generating an event message.


