JSPM – @fingerprintjs/fingerprintjs-pro@3.12.1

Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@fingerprintjs/fingerprintjs-pro) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Makes a website visitor identifier from a browser fingerprint. Unlike cookies and local storage, fingerprint stays the same in incognito/private mode and even when browser data is purged. Provides additional information and higher accuracy compared to Open Source FingerprintJS.

Quick start

Get a pro key:

Register a new PRO account at dashboard.fingerprint.com/signup (there is a free trial)
After registration go to the dashboard and select the created subscription
Go the "API Keys" page in the navigation side bar on the left side of the page
Copy a key with type "Public"

Install from NPM

npm i @fingerprintjs/fingerprintjs-pro
# or
yarn add @fingerprintjs/fingerprintjs-pro

import FingerprintJS from '@fingerprintjs/fingerprintjs-pro'

// Initialize an agent at application startup.
const fpPromise = FingerprintJS.load({ apiKey: 'your-pro-key' })

;(async () => {
  // Get the visitor identifier when you need it.
  const fp = await fpPromise
  const result = await fp.get()

  // This is the visitor identifier:
  const visitorId = result.visitorId
  console.log(visitorId)
})()

Run this code

Alternatively you can install from CDN

<script>
  // Initialize the agent at application startup.
  const fpPromise = import('https://fpjscdn.net/v3/your-pro-key')
    .then(FingerprintJS => FingerprintJS.load())

  // Get the visitor identifier when you need it.
  fpPromise
    .then(fp => fp.get())
    .then(result => {
      // This is the visitor identifier:
      const visitorId = result.visitorId
      console.log(visitorId)
    })
</script>

Note that you need to replace your-pro-key with a public API key from the dashboard.