For enhanced Fraud Prevention it is necessary to synchronise advertiser rejection data with Publishers. This allows for more accurate data points and much increased transparency between Advertisers and Publishers. 

It is particular useful in situations when:

• Lead Gen (Email Addresses are evaluated)
• Phone Numbers (Phone Numbers are evaluated for fraud)
• Appsflyer P360 Fraud Rejections
• Advertiser uses a different Fraud Prevention Software than the Publisher
• Agency / Network is not the exclusive Traffic Source of the Advertiser

1. Benefits for the Advertiser implementing a Fraud Database

• The Fraud Database is provided at no costs the Advertiser
• Known Fraudulent Users / IPs / Device IDs / Phone Numbers are already blocked at Click Level
• Improved Campaign Efficiency (e.g. already converted users do not have to be sent to the same campaign)
• No false positives as the data is 100% based on Advertiser Data input.
• Fully Privacy friendly solution that is compatible with GDPR / COPPA
• Automatic Rejection Reason Syncing with partners

2. Benefits for the Publisher 

• Automatic Fraud Checks at Click Level before sending Users to the Advertiser
• No False Positives as this is 100% Advertiser Data Based 
• Automatic Rejection Reason Syncing if a Conversion gets rejected at a later stage
• Improved Reputation with the Advertiser / Campaign Scaling 
• It works across all industries including LeadGen, eCommerce, Mobile Apps etc.

3. Technical Solution / Implementation

To avoid false flaggings we implemented a Advertiser Specific Fraud Database that considers the Advertisers flagged IPs, Device IDs, Domains, Phone Numbers, Emails, Domains and more. This can be based on the Advertiser's chosen Fraud Solution or his own custom solution.

Cryptographic Hashing Algorithm:

Cryptographic hashing is a process that takes an input, such as a piece of data or a message, and applies a mathematical algorithm to it to produce a fixed-size output, called a hash value or hash code. This hash value is unique to the input data, meaning that even a slight change in the input will produce a completely different hash value. In our case 24metrics uses the secure SHA-256 algorithm. 

IP-Address: 227.11.8.1

SHA-256 IP-Address: 793ec082c6d4d8a9c569b68c2199569ebc6ab72f94e27e5532a253f03bc110e9

Response Time: 16.666µs

Fraud Database Hashing Diagram

The CodeBase for the Hashing Algorithm is made open source and the goal is to establish an open standard in the industry. For more information / implementation please contact support@24metrics.com