Troubleshooting

Fix common Device Identification SDK errors: CORS issues, API key validation, signal collection timeouts, and confidence drops

Common Issues

SDK not loading

Ensure your API key is correct and the endpoint URL is accessible. Check browser console for CORS errors.

// Check for errors
try {
  const tracio = await Tracio.load({ apiKey: 'your-key' });
} catch (e) {
  console.error('tracio.ai load error:', e.message);
}

CORS errors

If you see CORS errors in the browser console, ensure your server allows requests from your domain. For enterprise deployments, configure your reverse proxy:

# nginx
add_header Access-Control-Allow-Origin "https://your-app.com";
add_header Access-Control-Allow-Methods "GET, POST, OPTIONS";
add_header Access-Control-Allow-Headers "Authorization, Content-Type";

Low confidence scores

Low confidence scores typically indicate significant signal changes. This is expected after:

• Major browser updates (e.g., Chrome 120 to Chrome 121)
• OS updates that change rendering behavior
• GPU driver updates
• New monitor or resolution change

The system will adapt within 2-3 visits as the matching engine learns the new signal baseline.

Bot detection false positives

If legitimate users are being flagged as bots, check:

• Browser extensions that modify navigator.webdriver or other WebDriver properties
• Corporate security software that injects scripts into pages
• Accessibility tools that hook into browser APIs

Review the bot.type field to understand which detector was triggered and adjust your policy.

High latency

If response times exceed 200ms:

• Check your network latency to the API endpoint
• Consider using the region closest to your users (EU or US)
• Contact support if latency persists