Error Handling & Permissions
Analytics Permissions
| Permission | ID | Description |
|---|
ANALYTICS_BASE | 1085 | Gate for all analytics views |
FEATURE_NEW_ANALYTICS_TAB | 1125 | New analytics dashboard |
FEATURE_LIVE_ANALYTICS_DASHBOARD | 1128 | Live analytics dashboard access |
FEATURE_MULTI_ACCOUNT_ANALYTICS | 1130 | Multi-account (cross-account) analytics |
FEATURE_LIVE_STREAM | 1104 | Required alongside ANALYTICS_BASE for live |
FEATURE_END_USER_REPORTS | 1096 | End-user level reporting |
Common Errors
| Error Code | Cause | Resolution |
|---|
INVALID_KS | Expired or malformed session | Generate a new KS |
SERVICE_FORBIDDEN | KS role lacks ANALYTICS_BASE | Assign analytics permissions to the role |
REPORT_NOT_FOUND | Invalid reportType value | Use a valid integer ID from Report Types Reference |
INVALID_PARAMS | Missing required filter fields | Include fromDate and toDate at minimum |
Reports Microservice Errors
The Reports Microservice returns HTTP status codes. A report/serve call with statusOnly: true returns {"status": "pending"}, {"status": "in_progress"}, or {"status": "completed"}. If generation fails, the status response includes an error message.
- Session Guide —
appId:<name> KS privilege tags analytics per-application; userId ties analytics to a user
- AppTokens — Scoped tokens for analytics-only access
- Player Embed — Player v7 fires ~45 playback events that feed analytics automatically
- Upload & Ingestion —
baseEntry.exportToCsv for bulk content export
- Webhooks — Trigger automated reporting on content events
- Distribution — Distribution status tracking via analytics reports