Question 1

How does the Passkey Telemetry SDK integrate with my existing authentication?

Accepted Answer

The SDK is completely agnostic to your authentication implementation. Whether you use Ping Identity, ForgeRock, Okta, Auth0 or a custom solution, the integration works the same way:Include our JavaScript/TypeScript SDK in your frontendAdd tracking calls at key authentication points (login start, passkey creation, errors, success)Optionally integrate backend events for advanced metricsZero performance impact: The SDK sends events via non-blocking, fire-and-forget API calls - your authentication flow never waits for our backend. Even if our API is slow or unavailable, events can be queued locally and retried in the background.Data privacy: We only collect UUID-based telemetry with no PII, no passwords, no biometric data. GDPR compliant with EU data centers.

Question 2

What data does the SDK collect, and is it GDPR compliant?

Accepted Answer

The SDK collects UUID-based authentication telemetry only:No PII: No emails, no passwords, no biometric dataTechnical events only: Passkey creation attempts, login success rates, browser capabilities, device types, error codesAuthenticator detection: iCloud Keychain, Google Password Manager, etc. (no credential data)Compliance & Security:EU data centers (AWS Frankfurt)Encrypted at rest (AES-256) and in transit (TLS 1.3)ISO 27001 and SOC 2 Type II certifiedGDPR compliant with Data Processing Agreements (DPAs) availableYou maintain full control: UUIDs are generated and owned by you. We never have access to user identities or authentication credentials.

Question 3

Can I start with just frontend tracking and add backend later?

Accepted Answer

Yes. Most customers start with frontend-only tracking, which provides 80-90% of the value:Authentication success ratesError classification (implicit vs explicit aborts)Funnel analysis and drop-off trackingDevice/OS breakdownsUser-level debugging with UUID searchBackend integration adds advanced capabilities like historical credential analysis, cross-device attribution, and backend-only events (e.g., fraud checks). You can enable backend tracking anytime without disrupting frontend analytics.

Question 4

How does the SDK handle high-traffic events like peak shopping seasons?

Accepted Answer

The SDK is built for enterprise scale. We process millions of events per day for our customers and have stress-tested for +100M logins/month. All tracking calls are fire-and-forget (non-blocking), so even if our backend experiences latency, your authentication flow is unaffected. We auto-scale on AWS, and events are queued with retry logic. If you're concerned about traffic spikes, we can discuss sampling rates or gradual rollouts.

Question 5

What frontend frameworks do you support?

Accepted Answer

Web frameworks: JavaScript, TypeScript, React, Next.js, Angular, Vue, and SvelteMobile SDKs: Swift (iOS) and Kotlin (Android)The core SDK is framework-agnostic. If you use a custom stack, you can integrate via vanilla JavaScript. For unique setups (React Native, Flutter), we can build custom integrations during the early access phase.

Question 6

How long does it take to integrate the Passkey Telemetry SDK?

Accepted Answer

Frontend-only integration: 2-3 weeks totalWeek 1: Setup (SDK installation, tracking key events like login start, passkey creation, errors)Week 2: Testing in non-production environmentWeek 3: Production rollout with gradual percentage (e.g., 10% traffic)Backend integration (optional) adds 1-2 weeks for advanced metrics. Compared to building your own analytics (2-3 weeks per report + continuous maintenance), the SDK is significantly faster and requires zero ongoing engineering effort.

Question 7

Can I roll out the SDK to specific user cohorts first?

Accepted Answer

Yes. Most customers start with:1-2 specific apps to validate integrationPercentage-based rollout (10% → 25% → 50% → 100%)Specific user cohorts or device typesThe SDK supports feature flags and custom properties (e.g. user segments), so you can filter dashboards by segment, device type or any custom dimension. This phased approach minimizes risk and allows you to validate analytics before global deployment.

Question 8

What if I need custom dashboards or metrics not available out-of-the-box?

Accepted Answer

The SDK supports custom events and custom properties, allowing you to track business-specific flows:Checkout authenticationAccount recovery flowsHigh-value transaction authenticationIn-store vs. online authenticationWe provide template dashboards (authentication success rate, funnel analysis, error classification), but you can create custom views by filtering on any tracked property. During early access, we co-develop custom dashboards with you based on your specific needs.

Question 9

How does the SDK handle errors and edge cases?

Accepted Answer

The SDK automatically classifies +100 passkey error types:iOS 17.4 conditional UI bugAndroid cross-device authentication failuresWindows Hello issuesThird-party password manager compatibility problemsImplicit vs explicit abort detection: We distinguish technical failures (system errors) from user cancellations, giving you clarity on whether issues are implementation bugs or user behavior.Unclassified errors are flagged for review. We continuously update error patterns as new OS versions or authenticators are released. If you encounter a new error, we'll add it to the classification engine within 48 hours.

Question 10

Can I export data?

Accepted Answer

Yes. The SDK provides data export via API.

Question 11

How does the SDK improve passkey adoption rates?

Accepted Answer

Visibility drives adoption. Organizations using our analytics achieve 50-80% passkey adoption vs. 5-10% without it. Why? Because you can identify and fix friction points.The SDK enables data-driven iteration: A/B test UI changes, monitor adoption by cohort and measure impact of each optimization. This process-mining approach to authentication is unique.

Question 12

What's the ROI of the Passkey Telemetry SDK?

Accepted Answer

The ROI depends on your authentication volume and passkey maturity:Cost Savings:Password reset costs can exceed six figures/month at enterprise scale and improving success rates by 20% saves $200k-$400k/yearOrganizations reduced password recovery by 10-20%, cutting call center volume (a top-3 support driver for most enterprises)Revenue Protection:Black Friday auth failures can cost millions. A 5% improvement in the error rate can save $500k-$1MImproving login success from 80% to 95% directly increases revenueEngineering Efficiency:Building your own analytics takes 2-3 weeks per report + ongoing maintenanceThe SDK replaces that with a flat fee, paying for itself if you avoid 1 week of engineering per month

Question 13

How does this compare to building our own analytics?

Accepted Answer

Most organizations try to build their own analytics using tracking databases, Google Analytics or custom dashboards. The challenges:Time: Organizations report dedicating 2-3 weeks setting up each report. Some run manual database queries once a week.Maintenance: Reports break when you add new passkey features (e.g., conditional create). Keeping dashboards up-to-date is ongoing work.Expertise: Passkey-specific analytics require deep WebAuthn knowledge (implicit vs explicit aborts, authenticator detection, cross-device flows). Building this in-house takes months.Blind spots: "We have higher error rates and we have no idea why." Generic analytics don't capture passkey-specific errors (iOS 17.4 bugs, Android edge cases).The SDK is pre-configured, always up-to-date and requires zero maintenance.

Question 14

Can the SDK help us debug specific user complaints?

Accepted Answer

Yes—this is a top use case. One customer reported: "It took someone in a to do a screen recording for us to figure out what was wrong."With the SDK:Search by UUID, email, or timestampSee the full event stream with all errorsIdentify device/OS, authenticator, and exact failure pointExport to support team or engineeringThis eliminates the need for manual log parsing or user screen recordings.

Question 15

Is the SDK secure for production use?

Accepted Answer

Yes. The SDK is already used in production by customers handling millions of authentications per month.All data encrypted at rest (AES-256) and in transit (TLS 1.3)ISO 27001 and SOC 2 Type II certifiedAnnual penetration testing and continuous security monitoringOnly tracks authentication telemetry (UUIDs, device metadata, errors)—no PII, no passwords, no biometric dataYour authentication flow remains completely isolated from our analytics pipeline.

Question 16

How does the SDK handle vendor onboarding and security reviews?

Accepted Answer

We provide a pre-built security questionnaire covering ISO 27001, SOC 2 Type II, GDPR, data residency, encryption, and penetration testing.Why it's faster: Because the SDK is frontend-only initially, it's treated as a client-side JavaScript library (similar to Google Analytics), which simplifies security approval.For backend integration, we provide additional documentation on API authentication, data flow diagrams and DPAs.

Question 17

Can we host the analytics platform in our own infrastructure?

Accepted Answer

Not initially. The SDK is SaaS-only to simplify deployment and ensure you always have the latest error classifications and dashboard updates.However, for enterprises with strict data residency requirements, we can discuss on-premise deployments during the early access phase.Why most customers prefer SaaS:Eliminates maintenance overheadAutomatic updates with new iOS/Android error patternsAlways up-to-date with latest passkey features

Question 18

What data residency options do you offer?

Accepted Answer

EU by default: All data is stored in EU data centers (AWS Frankfurt), complying with GDPR and EU data sovereignty laws.For customers requiring US or APAC data residency, we can configure region-specific deployments. Data never leaves the configured region.We provide Data Processing Agreements (DPAs) to document data handling practices.

Question 19

How do you ensure the SDK doesn't impact our authentication performance?

Accepted Answer

Zero performance impact guaranteed:All SDK calls are fire-and-forget (non-blocking). Your authentication flow never waits for our backendEvents queued locally and retried in background if our API is slow/unavailableEven during peak traffic (e.g. Black Friday), the SDK has zero impact on your authentication success rate or user experience.

Get Visibility into your Passkey Implementation

PROVEN RESULTS

Visibility, faster Debugging, higher Adoption

Authentication Success Rate

Faster Time to Resolution

Passkey Adoption

KEY FEATURES

See the Passkey Telemetry SDK in Action

Authentication Success Rate

Error Classification Console

Funnel Analysis Views

User Process Search

Device Analytics

Authenticator Detection

REAL-WORLD IMPACT

How Organizations use the SDK

Telecom: Debugging iOS Failures

Government: Conditional Create Adoption

E-Commerce: Optimizing Enrollment Funnels

Financial Services: Reducing Auth Support Costs

BUILD VS BUY

Why choose Corbado vs. building your own Analytics?

Corbado Telemetry SDK

Build Your Own

Authentication Success Rate Monitoring

Error Classification & Tracking

Funnel Analysis & Drop-off Tracking

Implementation Time

User-Level Debugging

FREQUENTLY ASKED QUESTIONS

Your Questions, answered

Technical Integration

How does the Passkey Telemetry SDK integrate with my existing authentication?

What data does the SDK collect, and is it GDPR compliant?

Can I start with just frontend tracking and add backend later?

How does the SDK handle high-traffic events like peak shopping seasons?

What frontend frameworks do you support?

Implementation & Rollout

How long does it take to integrate the Passkey Telemetry SDK?

Can I roll out the SDK to specific user cohorts first?

What if I need custom dashboards or metrics not available out-of-the-box?

How does the SDK handle errors and edge cases?

Can I export data?

Business Case & ROI

How does the SDK improve passkey adoption rates?

What's the ROI of the Passkey Telemetry SDK?

How does this compare to building our own analytics?

Can the SDK help us debug specific user complaints?

Security & Compliance

Is the SDK secure for production use?

How does the SDK handle vendor onboarding and security reviews?

Can we host the analytics platform in our own infrastructure?

What data residency options do you offer?

How do you ensure the SDK doesn't impact our authentication performance?

Make your passkey project a success

How to successfully introduce Passkeys?

Passkey Analytics - Get Data & Insights from Passkey Auth

How to Get High Passkey Adoption in Creation Flows

How to Get High Passkey Adoption in Login Flows

Get Early Access to the SDK