Platform Analytics
LoginRadius Platform Analytics provides a comprehensive view of your API activity, helping you track request trends, analyze error responses, and evaluate performance. These insights are essential for maintaining a smooth customer experience, diagnosing issues, and planning growth.
Business Use Cases
- Incident Debugging: Identify when and why errors spiked for faster resolution.
- Campaign Tracking: Monitor request and sign-up spikes during launches.
- Security Monitoring: Spot suspicious login patterns via 401/403 trends.
- A/B Testing: Measure performance and error impact across test variants.
- Regional Planning: Analyze traffic timing for global infrastructure scaling.
- QA & Testing: Validate performance stability during development cycles.
- Compliance Reporting: Export metrics for SLA and audit documentation.
Analytics
You can leverage this section under the Console's Insight--> Platform Analytics. This section presents detailed analytics for:
- Request Count
- Response codes
- Performance
Select the period from the dropdown available in dashbaord and click Refresh to update the dashboard.
- Request Count
- Response Code
- Performance
This section of the Platform Analytics dashboard displays a time-based graph showing the number of API requests your LoginRadius application receives. The X-axis shows the time (hourly intervals), and the Y-axis indicates the Number of API requests. Color-coded areas represent counts for different categories of requests or endpoint-specific traffic.
By actively tracking request count trends, teams can make data-driven infrastructure, marketing, and product decisions to maintain uptime and drive engagement.
The Response Code section displays a time-based visualization of the HTTP status codes returned by LoginRadius APIs. It enables teams to detect anomalies, understand error trends, and ensure the platform is responding to requests as expected.
The chart is color-coded and grouped by HTTP response classes (2xx, 4xx, 5xx), helping you monitor the quality and reliability of your API traffic at a glance.
2xx – Success
| Code | Meaning |
|---|---|
| 200 OK | General success |
| 201 Created | New resource (e.g., user profile) successfully created |
| 204 No Content | Successful operation with no response body (e.g., delete request) |
4xx – Client Errors
| Code | Meaning |
|---|---|
| 400 Bad Request | Invalid parameters or payload |
| 401 Unauthorized | Invalid or missing credentials (e.g., expired SOTT or access token) |
| 403 Forbidden | Authenticated but no permission for the resource |
| 404 Not Found | The requested endpoint or resource doesn’t exist |
| 409 Conflict | Duplicate resource or conflict with existing state |
5xx – Server Errors
| Code | Meaning |
|---|---|
| 500 Internal Server Error | Unhandled error or temporary failure |
| 503 Service Unavailable | Server is temporarily overloaded or under maintenance |
Monitoring response codes regularly helps teams maintain service quality, enforce security policies, and reduce incident response time.
The Performance section visually represents the response times for key LoginRadius API endpoints. It helps teams monitor the efficiency of authentication and profile-related operations, identify performance bottlenecks, and maintain a responsive user experience.
Each tab represents a specific API function, showing its execution time (in milliseconds) across different time intervals.
API Endpoint Performance Tabs
| Endpoint | Description |
|---|---|
| Lookup Profile | Measures the time taken to fetch user profile details using UID, email, or phone identifiers. |
| Auth Profile | Displays the response time for authenticating user credentials, typically during login attempts. |
| Create Profile | Shows how long it takes to register a new user via traditional signup or social login. |
| Delete Profile | Tracks the time taken to permanently delete a user profile from your LoginRadius directory. |
| Modify Profile | Represents how quickly user data (e.g., name, email, preferences) is updated in the system. |
By monitoring these metrics regularly, businesses can maintain high service availability, reduce churn, and deliver a smoother user journey.
Exporting Analytics
Click the download icon on any chart to export the data as an image. This is useful for internal reports, stakeholder meetings, or audit trails.
Best Practices
- Set up alerts or regular checks on error trends.
- Monitor response time peaks after deployment or major feature releases.
- Regularly export analytics data for performance reviews.