This guide provides best practices and tips for using IPQS Proxy Detection & IP Reputation service. Solve issues like click fraud, fake accounts, fraudulent orders, low quality users, application fraud, geo bypassing, ATO, UGC spam, and much more.
IPQS cultivates the most accurate and up-to-date data for IP intelligence and reputation scoring. Unlike other providers, IPQS gathers data directly from our proprietary honeypots, traps, crawlers, and thousands of live sites opted into our threat intelligence network. False-positives are minimized by only using fresh data and scanning billions of IP addresses every day. New threats are detected every second, so even the latest compromised IP addresses are unable to harm your business.
The following API inputs greatly improve scoring and the overall user experience while analyzing clicks, users, and transactions with IPQS:
Example Request with Recommended Starting Options
Please replace "user_agent" and "user_language" with the appropriate values.
PRO-TIP: Populating the "user_agent" data point can improve scoring by over 20%. Please make sure the full user agent string is passed, such as: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36".
Customize IPQS scoring engines to better fit your audience based on how strictly we score IP addresses and the threshold to determine active proxy connections. The following settings are available to adjust scoring:
If you experience any results that are not satisfactory, please contact us and include the IP addresses and any other relevant data for the requests. We will examine these results and optimize your account's scoring settings. Once your account has received a settings optimization, all future requests will provide much more accurate analysis. Out of the box settings tend to work for 90% of clients, so if you find our default settings are a good fit then optimization is not necessary.
IPQS Postback API allows requests to be marked as converted and for past data to be retrieved by associating a unique identifier. For example, it's possible to pull the last request that matched a userID, transactionID, or similar tracking variable.
Postback Example to Retrieve Latest Request by UserID
To perform this request, please make sure your initial API request passed a valid "userID" value (or any variable of your choice) and that this variable name is set on your custom tracking variables.
The easiest way to determine if the IP address is high risk is to analyze the following data points:
Upgrading your account immediately improves detection for abusive IP addresses and residential proxies, which are today's biggest threats. Premium plans and above have access to exclusive blacklists and IP intelligence data, while Enterprise plans include enhanced residential proxy detection and protection with Fraud Fusion™.
If you have additional information such as user & transaction data, then we strongly recommend passing that data with your API request. These features are extensions of the base Proxy Detection & IP Intelligence API and do not consume an additional usage credit.
PRO-TIP: Phone Reputation and Address Validation can be bundled into one check with IPQS User & Transaction Scoring API.