Migrate to tracio.ai
Move off any device fingerprinting provider with about half an hour of integration work and a day or two of parallel running. tracio.ai is not a drop-in endpoint swap: you install our SDK, switch server-side reads to webhooks, and visitor IDs start fresh.
Why Teams Switch to tracio.ai
Migrating From
FingerprintJS Pro
~133 signals
Castle
an undisclosed number of signals
SEON
an undisclosed number of signals
reCAPTCHA
no published signals
Migration Steps
Five steps from your current provider to tracio.ai. About 30 minutes of integration work, plus a day or two of parallel running before you cut over.
Create Your tracio.ai Account
2 minutesSign up and get your API key. Your Free plan includes 2,500 free API calls — enough to run a complete parallel comparison against your current provider.
Install the tracio.ai SDK
5 minutesAdd @tracio/sdk alongside your existing fingerprinting SDK. This is a code change, not an endpoint swap — tracio.ai ships its own client and its own result shape. Running both at once lets you compare on production traffic without disrupting it.
npm install @tracio/sdk
Switch Server-Side Reads to Webhooks
15 minutesIdentification results are pushed to your server as signed webhooks the moment a visitor is identified, so most integrations retire their polling loop entirely. If you still need to read a visit after the fact, the Server API answers by requestId from the Pro plan up. Either way the payload is our own flat camelCase document, so you map the fields once.
// Before (competitor) — poll by requestId
const resp = await fetch("https://api.competitor.io/events/" + requestId, {
headers: { "Auth-API-Key": COMPETITOR_API_KEY }
});
// After (tracio.ai) — receive a signed webhook per identification
app.post("/webhook/tracio", (req, res) => {
// verify req.headers["x-tracio-signature"], then act on req.body
const event = req.body; // { requestId, visitorId, bot, decision, ... }
res.status(200).send("OK");
});Run Parallel Comparison
24-48 hoursRun both SDKs simultaneously for 24-48 hours. Visitor IDs will not match between providers — each is computed from a different database — so compare what actually matters: whether the same physical device is recognized consistently across visits, and how the bot verdicts line up on your traffic.
Cut Over to tracio.ai
10 minutesRemove the old SDK and keep your webhook handler as the server-side source of truth. There is no downtime — both SDKs run side by side until you drop the old one. Returning visitors start fresh in our database, so map them to your existing accounts with linkedId. If anything goes wrong, the rollback path is simply reinstalling the old SDK.
Ready to Switch?
Create your free account and start the migration. Our team is available to help with the webhook handler and the parallel run.