Metrics and reporting
Metrics and reporting are Infobip platform features that enable you to track, analyze, and understand platform usage. In CPaaS X, reporting is scoped to applicationId and entityId, so you can view metrics per application or per customer entity instead of seeing only platform-wide aggregates.
How scoped reporting works [#how-scoped-reporting-works]
CPaaS X scopes metrics by applicationId and entityId. You can query at two levels:
Application-level reporting
Aggregated metrics across all entities within an application, including total message volumes, delivery rates, and success rates.
Entity-level reporting
Per-customer metrics showing exact usage, delivery rates, and performance. Each entity's data is completely isolated from other entities.
Why scoped metrics matter [#why-scoped-metrics-matter]
Scoped metrics provide three critical capabilities for multi-tenant platforms:
- Per-customer usage tracking: Know exactly how many messages each customer sent, across which channels, and at what delivery rate. Identify performance issues per entity.
- Customer self-service visibility: Give customers access to their own usage data without exposing other entities' data. Each customer sees only their own metrics and quota.
- Performance trend analysis: Track delivery rates, message volumes, and usage patterns over time per entity. Detect anomalies and optimize customer communication performance.
Where to view metrics [#where-to-view-metrics]
CPaaS X metrics and reporting can be accessed in three ways:
Use the Analyze section in the Infobip web interface to view metrics without writing code. Analyze supports filtering by applicationId and entityId for CPaaS X customers, so you can isolate metrics per entity.
- Cross-channel dashboards with delivery rates, failed messages, and engagement data (clicks, seen rates).
- Financial reports with application and entity dimensions for per-customer cost analysis.
- Recurring automated reports (daily, weekly, monthly) with export and sharing.
Best for: Non-technical users, quick checks, and financial reporting.
See Analyze.
Programmatic queries filtered by applicationId, entityId, and timeframe. Use APPLICATION_ID and ENTITY_ID as grouping dimensions to aggregate traffic data across tenants.
- Asynchronous query processing for large datasets.
- Aggregated traffic data across all channels (SMS, Email, WhatsApp, RCS, and more).
- Flexible aggregation by country, network, sender, status code, and custom dimensions.
Best for: Custom dashboards, automated reports, and programmatic cost attribution.
See Metrics API.
Real-time webhook notifications triggered by events across your communication flows. Subscriptions are scoped by applicationId and entityId using filters, so each entity receives only its own events through dedicated webhook endpoints.
- Supports 20+ channels including SMS, MMS, Email, WhatsApp, RCS, Viber, Voice, and more.
- Event types include delivery, clicks, seen, inbound messages, identity changes, and template updates.
- Filter by entity, application, user, or resource. A subscription triggers only when all filter conditions match.
- Manage subscriptions through the web interface (Developer tools > Subscriptions Management) or the Subscriptions API.
Best for: Live monitoring, immediate alerts, customer-facing event streams, and inbound message handling.
Applications and entities
Core concepts and data isolation.
Webhook subscriptions
Real-time delivery notifications per entity.
Secure your CPaaS X setup
Scope API keys for access control.