← Files FingerprintARCHIVED FILE
skills/fingerprint-vue/SKILL.md
2.37 KB · Oct 3, 2026 · 06:27 UTC
---
name: fingerprint-vue
description: Integrate Fingerprint device identification into a Vue 3 (or Nuxt) app — initialize the agent and get the visitor's visitor_id and event_id.
---
# Fingerprint — Vue
Integrate Fingerprint into a Vue 3 app to identify visitors: register the plugin once at startup,
then ask it for the visitor's `visitor_id` and a single-use `event_id` wherever you need it (on
mount, or on an action like login or checkout).
> Docs: https://docs.fingerprint.com/docs/vuejs · JS Agent v4: https://docs.fingerprint.com/reference/js-agent-v4
## Package
`@fingerprint/vue` — install the latest version. (Nuxt uses the same package, registered
client-side. For plain HTML or an unsupported framework, use `@fingerprint/agent` instead.)
## Env var
- `FINGERPRINT_PUBLIC_API_KEY` — the public key, safe to ship to the browser.
> Bundlers only expose prefixed vars to client code — map the key to the bundler's convention:
> - Vite: `VITE_FINGERPRINT_PUBLIC_API_KEY` → `import.meta.env.VITE_...`
> - Vue CLI: `VUE_APP_FINGERPRINT_PUBLIC_API_KEY` → `process.env.VUE_APP_...`
> Never expose `FINGERPRINT_SECRET_API_KEY` to the frontend.
## Steps
1. **Install** `@fingerprint/vue`.
2. **Initialize once at the app root.** Register `FingerprintPlugin` with `app.use(...)`, passing
the public key and region (`us` | `eu` | `ap`, matching the workspace). See `snippets/plugin.js`.
3. **Get the identification where you need it.** Use the `useVisitorData` composable. For
identify-on-demand pass `{ immediate: false }` and call `getData()` on the action you care
about; it returns `{ visitor_id, event_id, ... }`. See `snippets/use-visitor-data.vue`.
4. **Verify it works.** Disable your ad blocker, run the dev server, trigger the call, and confirm
a `visitor_id` is logged in the browser console (or that the event appears on the dashboard
Events page).
## Notes
- Region must match the workspace (`us` | `eu` | `ap`).
- Register the plugin once at the app root; don't re-instantiate per component. Don't block the UI
on identification — handle the composable's `isLoading` / `error` state.
- **Production:** protect the agent from ad blockers with a custom subdomain or proxy —
https://docs.fingerprint.com/docs/protecting-the-javascript-agent-from-adblockers.
- Don't use legacy `@fingerprintjs/fingerprintjs-pro`, `FingerprintJS.load()`, or `scriptUrlPattern`.
SHA-256: fef0c319c9301839939426399584c31fce122282a0d78fef7fe1434a294cfe66