When incorporating Trustfull, it's important to determine the acceptable response time from your system. While you have control over certain aspects of this timeframe, external factors may also influence it.
The subsequent sections provide a clear understanding of timeouts, their functionality within Trustfull, and the impact they can have on the results you observe. It is crucial to closely monitor your results during the initial days and make any necessary adjustments to optimize outcomes. If you have any questions, feel free to reach out to our team at Trustfull at any point in time.
In Trustfull's API-based service, response time refers to the total available time for processing and responding to a request. This includes the time it takes for your request to reach our servers, be processed and answered, and for the response to return back to your server.
Within Trustfull's system, the response time consists of two main components:
- Network: This refers to the delay in communication over the network when interacting with our APIs.
- Enrichment: This is the time required to gather all the necessary data values for the Data Enrichment process. Please note that response times may vary as Trustfull does not have control over third-party servers and data sources.
Fine-tuning your enrichment time is a vital aspect of achieving optimal outcomes with Trustfull.
By extending the enrichment time, you can enhance the accuracy of our data enrichment process. A minor increase at lower values can boost the hit rate by 10–20%. However, at higher levels, an increase may only yield a single additional checked service.
You have the flexibility to set different enrichment times for various scenarios. For instance, if you integrate Trustfull across multiple touchpoints, you can perform checks during the registration, login, and purchase stages.
By increasing the enrichment time during high-risk interactions like registration and purchase, you can ensure the highest level of security for both you and your customers. On the other hand, keeping the enrichment time low for less risky touchpoints, such as login, will guarantee a smooth and frictionless experience.
The following tables provide an overview of the expected outcomes for different data enrichment timeout settings, with an accuracy rate greater than 70%:
|< 7000ms||Image analysis|
|< 2500 ms||Facebook, Instagram, Facebook|
|< 2000 ms||Office365, Linkedin, Skype|
|< 1500 ms||WhatsApp, Telegram, Amazon, Google, Twitter|
|< 1000 ms||Data Breaches, Portability, Carrier|
|< 7000 ms||Image analysis|
|< 3000 ms||Linkedin, Apple, Flipkart|
|< 2500 ms|
|< 2000 ms||eBay, Instagram, Paypal, Google, Skype|
|< 1500 ms||Amazon, Twitter, Pinterest|
|< 1000 ms||Office365, Disney+, Deliverability, WordPress, WordPress, Deliveroo, Gravatar, Hubspot, Spotify, Data Breaches, Company, Disposable, Domain lookup|
|< 1500 ms||Blacklist Check|
|< 1000 ms||VPN Check, Geolocation, Connection Type, Company|
|< 2000 ms||Device Price|
|< 1500 ms||Hardware info|
|< 1500 ms||Validity|
|< 1000 ms||Genderization|
|< 1500ms||Emulator Detection, Time on page, Page scroll|
|< 1000ms||Language, Topics, Plugins, Fingerprint, Incognito mode, Page Referrer, Timezone|
Updated about 1 month ago