Configuring resources
The Dashboard allows you to manage all the resources and settings that govern how your Fingerprint implementation operates.
API keys
API keys are necessary for your Fingerprint setup. Primarily to be able to identify visitors and generate visitor IDs, but also interact with other Fingerprint APIs and features.
To manage API keys, go to Dashboard > API keys.
| Keys | Description |
|---|---|
| Public | Used to make client-side requests to identify visitors and generate the visitor ID. Used in the browser or in mobile apps. |
| Server API | Used to make server-side requests to the Fingerprint Server API to securely obtain visitor and request information. |
| Management API | Used to access the Management API, allowing management of dashboard resources. |
| Sealed Client Results | Used to enable Sealed Client Results to encrypt client-side payloads. |
| Proxy | Used to authenticate with third-party proxy integrations which allow you to evade ad blockers. |
API key monitoring
For public and server API keys, you can click on Details to view monitoring information about an API key.
On this page you can view when was the key last used, by which library version, and on what origin domains or mobile applications.
You can view request usage and server-side latency charts:
- Request usage chart shows incoming identification requests using this API key.
- Success - Successful requests with response
HTTP 200 - Throttled - Requests going over configured RPS limit and were responded with
HTTP 429 - Restricted - Requests filtered out by request filtering rules or exceeding workspace/environment limits and were responded with
HTTP 403
- Success - Successful requests with response
- Server-side latency chart shows percentiles for average time for processing identification requests. Does not include client-side signal collection latency.
Request filtering
Request filtering is a feature that enables you to filter out unwanted identification requests using specific rules. On the Dashboard, you can manage filtering rules by adjusting which events should be allowed or denied.
To learn more information, see request filtering.
To manage webhooks, go to Dashboard > Security.
Webhooks
Webhooks allow you to receive an HTTP request to your server with Fingerprint results for every identification event the moment it happens. On the Dashboard, you can manage webhooks and monitor their activity.
To learn more information, see webhooks.
To manage webhooks, go to Dashboard > Webhooks.
Custom subdomains
By using a custom subdomain, Fingerprint cookies are treated as "first-party", which increases identification accuracy while also allows you to avoid ad blockers. On the Dashboard, you can register your subdomains and manage their certificates.
To learn more information, see Custom subdomain setup.
To manage subdomains, go to Settings > Subdomains.
Proxy integrations
Proxy integrations are an alternative to custom subdomains, they allow you to proxy requests to Fingerprint through your own domain. Our cookies are treated as "first-party", which increased identification accuracy while allowing you to avoid ad blockers. On the Dashboard, you can setup proxy integrations and monitor their status and activity.
To learn more information, see Evading ad blockers with proxy integrations.
To manage proxy integrations, go to Dashboard > Libraries & integrations
Suspect Score
Suspect Score is an easy way to integrate Smart Signals into your fraud protection workflow. It is a weighted representation of all Smart Signals present in the payload that helps identify suspicious activity. On the Dashboard, you can configure the weights for suspect scoring by adjusting for each detected Smart Signal.
To learn more information, see Suspect Score.
To manage suspect score weights, go to Dashboard > Smart Signals > Suspect Score
Updated 12 days ago