Transaction Tracking System with ClickID Fraud Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Electronic advertising in the Internet marketplace faces challenges such as lack of technological competence among participants and different economic dynamics compared to physical advertising, necessitating improved tracking systems to address fraudulent activities and accurately record transactions.

Innovation Solution

The system tracks electronic commerce transactions by assigning a unique 'clickID' to each advertisement access, using pixel beacons or Web services for reporting transactions, and employs a security/fraud prevention module to validate and record transactions, ensuring accurate tracking and preventing fraudulent activities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If electronic advertising tracking is implemented, then transaction accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvetransaction accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces a tracking server as an intermediary component that mediates between advertisers, publishers, and consumers. This server handles the complex tracking operations, including generating unique identifiers, validating transactions, detecting fraud, and computing fees, thereby improving transaction accuracy without requiring complex client-side implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The tracking system is segmented into distinct functional modules within the tracking server: identifier generation module, transaction validation module, fraud detection module, and fee computation module. This segmentation allows each component to perform its specific function independently, improving overall system maintainability and accuracy while managing complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

2Reliability

If fraud detection mechanisms are added, then transaction reliability is improved, but processing time increases

Engineering Contradiction:
Improvetransaction reliabilityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining fraud detection criteria and validation rules in the tracking server before transactions occur. When a transaction is reported, the server quickly validates it against pre-established criteria rather than performing complex real-time analysis, thereby improving reliability while minimizing processing time delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The fraud detection system efficiently skips through and identifies fraudulent transactions by looking for obvious patterns and anomalies that violate established criteria. Valid transactions that pass quick preliminary checks are processed rapidly, while only suspicious transactions undergo more thorough investigation, thus maintaining high processing throughput while ensuring reliability.

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS10467666B2Methods and systems for tracking electronic commerce transactions
Publication Date: 2019.11.05 RAKUTEN GROUP INC
  • US10467666B2 patent drawing
  • US10467666B2 patent drawing
  • US10467666B2 patent drawing

AI summary

Systems and methods are disclosed for tracking user access to an advertisement and user transactions with an electronic commerce computer associated with the advertisement. In accordance with one aspect of the disclosed technology, a transaction tracking computer associates an identifier with each access (e.g., click) of an advertisement. Transactions that occur at the electronic commerce computer that are related to the advertisement will be reported to the transaction tracking server together with the identifier. In one embodiment, if the reported transaction is a duplicate of a previously reported transaction, then the reported transaction is determined to be invalid. In one embodiment, if the reported transaction occurs more than a predetermined amount of time after the time the identifier was initially generated, then the reported transaction will also be determined to be invalid.