Identity Conversion Metrics

Measure anonymous-to-identified user conversion to evaluate identity merge and login capture effectiveness.

Audience: Product and lifecycle teams optimizing authentication and identity capture flows.

Critical: Identity conversion endpoint: GET /api/v1/analytics/identity/conversion-metrics.

Journeys Client Public API Reference: Event Types

Who This Page Is For

Use this page when your KPI includes converting anonymous traffic into identified user profiles and you need to quantify that transition over time.

Quick Start (2-5 Minutes)

Load identity conversion metrics

Get baseline anonymous-to-identified conversion indicators.

GET /api/v1/analytics/identity/conversion-metrics?days=30&siteId=SITE_ID

Cross-check identify flow

Validate identify events are sent immediately after authentication.

POST /api/v1/public/sites/:siteKey/users/identify

Compare periods

Track conversion movement after auth UX changes.

Run same query over consecutive release windows.

Segment by site

Use site filter for site-specific identity diagnostics.

GET /api/v1/analytics/identity/conversion-metrics?siteId=SITE_ID&days=90

Tie to funnel outcomes

Correlate identity conversion with funnel and revenue results.

Compare with Funnel V2 by running signup/login funnel steps in journey mode.

Identity conversion endpoint

GET /api/v1/analytics/identity/conversion-metrics

Required Fields / Minimum Payload

Field	Required	Type	Used by events	Description
`days`	Optional	`number`	identity conversion endpoint	Lookback window for conversion metrics.
`siteId`	Optional	`uuid`	identity conversion endpoint	Site-level scoping for targeted diagnosis.
`Authorization`	Required	`Bearer token`	identity conversion endpoint	Authenticated analytics access.

Event or Endpoint Decision Matrix

Scenario	Use This	Why
Need identity capture KPI baseline	/analytics/identity/conversion-metrics	Dedicated identity conversion summary endpoint.
Need to improve merge quality	/public/sites/:siteKey/users/identify integration audit	Identify call timing is core to merge success.
Need user-type conversion context	/analytics/funnels/:siteId?steps=user_signup,user_login,product_view,purchase&mode=journey	Measures authenticated onboarding progression with strict journey grouping.
Need long-window trend	conversion-metrics with days=90	Smoother trend analysis for low-frequency events.
Need per-site diagnosis	conversion-metrics with siteId	Isolates problematic site implementations.

Common Errors and Fixes

Identity conversion rate unexpectedly low

Cause: identify calls missing on login/register flow.

Fix: Trigger identify immediately after successful auth.

Metrics fluctuate after deployment

Cause: Session/visitor identifier handling changed in frontend.

Fix: Validate visitor and user ID continuity across auth boundary.

Site-level metric differs from org-level expectation

Cause: siteId filter omitted or wrong site used.

Fix: Use explicit siteId for local diagnostics.

No visible impact after auth UX improvements

Cause: Insufficient observation window or low traffic sample.

Fix: Use longer period and compare equivalent traffic cohorts.

Production Checklist

Identify API call is part of mandatory post-auth flow.Required
Identity conversion KPI is monitored after auth-related releases.Required
siteId-scoped diagnostics are available for multi-site teams.Required
Identity conversion is correlated with funnel and revenue outcomes.Required
ID continuity assumptions are documented for frontend teams.Required