Product adoption analytics
info
Applies to:
Applies partially to Platform, see additional analytics used in Platform.
How do our analytics work?
When you use our SDKs, they send telemetry data to our servers related to how the SDK is being used. We never collect personally identifiable information (PII) from scanned documents or cards in our analytics.
If you are using an on-device extraction SDK like BlinkID or BlinkCard, any PII data from a scanned document or card remains exclusively on the device where that SDK is used.
Which data is collected?
| Event Type | Description |
|---|---|
| SDK initialization | Product, platform, package name |
| Device info | User agent, screen size, GPU info, storage support (Web), anonymized IP address |
| Camera info | Camera permissions, available cameras, resolutions, facing direction, focus type |
| UX events | Camera started/closed, help displayed, timeouts, error messages shown |
| Scanning conditions | Device orientation changes, flashlight state |
| Errors | Non-fatal errors and crashes with stack traces |
A unique user ID is generated per device/browser and stored locally.
How does it work?
Analytics data is collected as packets which are:
- Batched locally - Events are accumulated and stored locally
- Sent at strategic points - Data is transmitted at key moments:
- Session initialization
- First frame processed
- Side/document scanned
- App moved to background
- Retried on failure - Failed transmissions are stored and retried later
The telemetry data is sent encrypted, and not in plain text.