Skip to main content
Fingerprint JS agent v3.6.0 or later is required. Fingerprint Akamai Proxy Integration is responsible for proxying identification and agent-download requests between your website and Fingerprint through your Akamai infrastructure. The integration consists of a set of property rules you need to add to your Akamai property configuration. The property rules template is available on GitHub.
Limitations and expectations

​
Limited to Enterprise plan

Support for the Akamai Proxy Integration is provided only to customers on the Enterprise Plan. Other customers are encouraged to use Custom subdomain setup or Cloudflare Proxy Integration.

​
Manual updates occasionally required

The underlying data contract in the identification logic can change to keep up with browser and device releases. Using the Akamai Proxy Integration might require occasional manual updates on your side. Ignoring these updates will lead to lower accuracy or service disruption.

​
The benefits of using the Akamai Proxy Integration

  • Significant increase in accuracy in browsers with strict privacy features such as Safari or Firefox.
  • Cookies are now recognized as “first-party.” This means they can live longer in the browser and extend the lifetime of visitor IDs.
  • Ad blockers will not block our Fingerprint JS agent from loading. Attempts to connect to an external URL will be stopped by most ad blockers while attempts to connect to the same site URL will be allowed.
  • Ad blockers will not block our identification requests since they are sent to the specific path or subdomain that belongs to the same site.
  • Insight and control over the identification requests that can be combined with other Akamai features like property rules and traffic reports.
  • With the Akamai Proxy Integration, you can manage unlimited subdomains and paths and provide Fingerprint services to all your customers at any scale while benefiting from all the 1st-party integration improvements.
  • Cookie security: Akamai Proxy Integration drops all the cookies sent from the origin website. The source is open-source so this behavior can be transparently verified and audited.
  • Easy to meet compliance and auditing requirements.

​
Integration setup overview

  1. Issue a proxy secret in the Fingerprint Dashboard.
  2. Create path variables used by the Akamai property rules and client agent configuration on your website or mobile app.
  3. Install and configure the integration in your Akamai account. You have 2 options:
    1. Using Terraform (recommended).
    2. Using Akamai Property Manager API.
Finally, configure the Fingerprint JavaScript agent on your website or client application.

​
Step 1: Issue a Fingerprint proxy secret

Issue a Fingerprint proxy secret to authenticate requests from your Akamai infrastructure.
  1. Go to the Fingerprint dashboard and select your workspace.
  2. In the left menu, navigate to API keys.
  3. Click Create Proxy Key.
  4. Give it a name, for example, Akamai proxy integration.
  5. Optionally, you can choose an environment for the proxy secret.
    1. By default, the proxy secret works for all environments in your workspace.
    2. A proxy secret scoped to a specific environment can only authenticate identification requests made with a public API key from the same environment.
  6. Click Create API Key.
You will use the proxy secret value in the following step, so store it somewhere safe. You cannot retrieve the secret later.

​
Step 2: Create path variables

Set the path variables you will use throughout your property configuration and the JavaScript agent configuration on your website. These values are arbitrary. Just decide what your values are and write them down somewhere. In this guide, we will use readable values corresponding to the variable names to make it easier to follow: 
FPJS_INTEGRATION_PATH="FPJS_INTEGRATION_PATH"
FPJS_AGENT_PATH="FPJS_AGENT_PATH"
FPJS_RESULT_PATH="FPJS_RESULT_PATH"
However, your values used in production should look more like random strings: 
FPJS_INTEGRATION_PATH="ore54guier"
FPJS_AGENT_PATH="vbcnkxb654"
FPJS_RESULT_PATH="5yt489hgfj"
That is because ad blockers might automatically block requests from any URL containing fingerprint-related terms like “fingerprint”, “fpjs”, “track”, etc. Random strings are the safest. So whenever you see a value like FPJS_INTEGRATION_PATH in this guide, you should use your random value instead.

​
Step 3: Install and configure the integration in your Akamai property

You can choose from two available installation methods. If you manage your infrastructure as code using Terraform, you can use the Fingerprint Akamai proxy integration Terraform module. This installation method does not include any mechanism for automatic updates. The proxy function code is updated every time you run terraform apply. If you prefer the Terraform installation method, continue with Install Akamai proxy integration using Terraform, then come back to this page to configure the Fingerprint JavaScript agent on your website.

​
Using Akamai Property Manager API

If you don’t use Terraform to manage your infrastructure, you can deploy the integration using Akamai Property Manager API. This installation method does not include any mechanism for automatic updates. You will need to manually repeat the deployment process every time you update the integration. If you prefer the Akamai Property Manager API installation method, continue with Install Akamai proxy integration using Akamai Property Manager API, then come back to this page to configure the Fingerprint JavaScript agent on your website.
Note: Usage of Origin IP Access Control List rule
  • To support IPv6 origins, the integration uses the Origin IP Access Control List rule.
  • Without additional configuration, this results in a warning in Akamai Control Center: “You have Origin IP Access Control List enabled in a rule in your property. You should also enable Tiered Distribution in either the same rule or a parent rule. This will better support caching on edge servers.”
  • This warning is expected and means the integration is working. We recommend following the recommendation in the warning and enabling Tiered Distribution in your property rules. See the Akamai documentation for Origin IP ACL for more details.

​
Configure Fingerprint Pro Agent

  1. Use the random path variables created in deployment steps according to your deployment method to construct the scriptUrlPattern (agent download) and endpoint (get result) URLs.
  2. Configure the Fingerprint JS Agent on your website accordingly:
import * as FingerprintJS from '@fingerprintjs/fingerprintjs-pro'

// Initialize the agent at application startup.
const fpPromise = FingerprintJS.load({
apiKey: 'PUBLIC_API_KEY',
scriptUrlPattern: [
    'https://yourwebsite.com/FPJS_INTEGRATION_PATH/FPJS_AGENT_PATH?apiKey=<apiKey>&version=<version>&loaderVersion=<loaderVersion>',
    FingerprintJS.defaultScriptUrlPattern, // Fallback to default CDN in case of error
  ],
  endpoint: [
    'https://yourwebsite.com/FPJS_INTEGRATION_PATH/FPJS_RESULT_PATH?region=us',
    FingerprintJS.defaultEndpoint // Fallback to default endpoint in case of error
  ],
});
Parameter URL nuances
  • Note that the import url for the CDN installation method and scriptUrlPattern used by NPM packages are similar but different and cannot be used interchangeably.
  • Pay attention to differences in query parameters:
    • Pass region to the endpoint parameters in the following format: ?region=eu. The value needs to reflect the region of you application.
    • Leave thescriptUrlParam parameter as displayed here: ?apiKey=<apiKey>&version=<version>&loaderVersion=<loaderVersion>. The apiKey version and loaderVersion parameters will be replaced by the values in the NPM package automatically. Do not alter them manually.
If everything is configured correctly, you should receive the latest Fingerprint client-side script and the identification result through your Akamai integration. If you have any questions, reach out to our support team.

​
Monitoring the integration

Go to Dashboard > SDKs & integrations > Akamai to see the status of your integration. Here you can monitor:
  • If the integration is up to date.
  • How many identification requests are coming through the integration (and how many are not).
  • The error rate of proxied identification requests (caused by missing or incorrect proxy secret).
The information on the status page is cached so allow a few minutes for the latest data points to be reflected.