Event Code Validation for Advertising Metrics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current tracking metrics for mobile devices are insufficient to accurately monitor interactive events related to advertisements, leading to inaccurate data and hindered productivity in targeted and viral marketing efforts, particularly due to mismatched interactive capabilities between devices and content providers.

Innovation Solution

A system and method for validating metrics and event codes associated with interactive events on mobile devices, involving a server that analyzes action and event codes for consistency with predetermined format and substance rules to ensure accurate tracking and verification of advertising interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional tracking mechanisms are used to monitor advertising interactions on mobile devices, then basic tracking data can be collected, but the data accuracy and reliability deteriorate due to mismatched interactive capabilities between devices and content providers

Engineering Contradiction:
Improvetracking data accuracyVSAvoidcompatibility between devices and content
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary validation of event codes against a schema definition before processing tracking data. The schema is established in advance with the advertising content, specifying which interactive events should be tracked. This preliminary setup ensures that only compatible and expected events are validated, preventing accuracy issues from mismatched device capabilities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation layer between the mobile device and the tracking system. The event code schema acts as a mediator that translates diverse device interactive capabilities into a standardized, validated format. This intermediary schema validation ensures compatibility while maintaining data accuracy by filtering and standardizing events before they enter the tracking system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If comprehensive tracking of all interactive events is implemented, then more marketing insights are available, but the system complexity and data verification burden increase significantly

Engineering Contradiction:
Improvemarketing data completenessVSAvoidtracking system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The tracking system is segmented into distinct functional components: event code generation on the device, schema validation on the server, and metric calculation based on validated events. The schema itself is segmented into specific event type definitions. This segmentation allows comprehensive tracking while managing complexity by separating validation logic from data collection and analysis.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The event code schema serves multiple functions simultaneously: it defines which events to track, validates incoming event codes, and structures the data for analysis. This multi-functional schema approach enables comprehensive tracking without proportionally increasing system complexity, as one component (the schema) performs multiple critical roles.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If event codes are validated against predetermined rules, then data reliability improves, but the processing time and computational resources increase

Engineering Contradiction:
Improvetracking data validityVSAvoidvalidation processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs partial validation by checking event codes against the schema definition - validating only the necessary structural and format requirements rather than exhaustive verification of all possible event attributes. This partial validation approach maintains data reliability while minimizing processing time by focusing only on critical validation checks.

Inventive Principle:
Principle #16Partial or excessive action

4Object-affected harmful factors

If detailed validation of event code format and substance is performed, then fraudulent data is prevented, but the ease of operation and implementation decreases

Engineering Contradiction:
Improvefraudulent tracking dataVSAvoidsystem implementation simplicity
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The system implements self-service validation where the schema definition automatically validates event codes against its own structure and rules. The validation logic is embedded in the schema itself, allowing the system to self-verify data integrity without requiring external manual verification processes. This automated self-validation prevents fraudulent data while maintaining implementation simplicity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8694371B2System and method for validating metrics associated with interactive events related to advertising
Publication Date: 2014.04.08 MALIKIE INNOVATIONS LTD
  • US8694371B2 patent drawing
  • US8694371B2 patent drawing
  • US8694371B2 patent drawing

AI summary

A method is provided for validating advertising metrics which relate to tracking of interactive events performed by electronic devices. A metric report with an event code that indicative of at least one interactive event performed by an electronic device associated with the network is received. The format of the event code is analyzed to determine whether the event code is consistent with predetermined format rules and the substance of information conveyed by the event code is analyzed to determine whether the event code is consistent with predetermined substance rules. If the event code is determined to be consistent with the predetermined format rules and the predetermined substance rules, the event code is accepted as valid. Otherwise, the event code is identified as being invalid.