CTRLK

Shared components

Reports and insights

|

View as Markdown

Reports and insights give you visibility into how your SMS traffic performs across delivery, performance, and cost. Use them to understand whether messages reach recipients, track conversion rates, and identify performance issues.

Infobip provides SMS reporting through the web interface and programmatic APIs, supporting both manual analysis and automated monitoring. SMS reporting options include:

  • Cross-channel analytics: Aggregated performance data across channels
  • Event-driven notifications: Real-time lifecycle events pushed to your systems
  • Message-level records: Per-message delivery confirmation and troubleshooting


SMS reporting options [#sms-reporting-options]

The following table summarizes the available reporting options for SMS.

Reporting optionScopeAccess patternLimitsPrimary use
Cross-channel analytics
Metrics API
Cross-channel (SMS, WhatsApp, RCS, Email, Viber)Pull-based, on demandBased on requested time intervalAnalyze aggregated performance at scale, build dashboards, compare trends
Event-driven notifications
Subscriptions Management API
Cross-channel (includes SMS)Push-based, event-drivenEvent triggeredTrigger workflows, synchronize systems, receive lifecycle events in real time
SMS delivery reports
Delivery reports API
SMS-onlyPull-basedLast 48 hours, max 1,000 per request, consumed on retrievalConfirm whether specific messages were delivered
SMS message logs
Message logs API
SMS-onlyPull-basedLast 48 hours, max 1,000 per requestTroubleshoot and audit individual messages


Cross-channel analytics for SMS [#cross-channel-analytics]

Use the Metrics API to retrieve aggregated SMS performance data across defined time intervals. For SMS traffic, the Metrics API provides:

  • Delivery rates and message counts
  • Failure counts and error breakdowns
  • Engagement metrics (for example, click tracking where enabled)
  • Traffic distribution by sender, destination, or country
  • Cost indicators

See the Metrics API reference for available endpoints, supported filters, and response formats.



Event-driven notifications for SMS [#event-driven-notifications]

Use Subscriptions to receive real-time SMS lifecycle events pushed directly to your webhook endpoints. For SMS, subscriptions can deliver events such as:

  • Message delivered
  • Message failed
  • Message sent
  • URL click events (when tracking is enabled)
  • Inbound SMS received

You can configure subscriptions through either method:

  • Subscriptions Management API: Create, update, and manage subscriptions programmatically. Use this method for automated environments, CI/CD pipelines, and multi-account setups.
  • Web interface: Configure subscriptions interactively by defining the event type, delivery endpoint, authentication method, and filtering parameters.

See Subscriptions management for setup instructions, or explore the Subscriptions Management API for programmatic configuration.



Message-level records for SMS [#message-level-records]

Message-level endpoints provide short-term, per-message visibility for outbound SMS traffic. They are designed for operational confirmation and troubleshooting, not for aggregated performance analysis.

NOTE

Message-level records are limited to the last 48 hours and a maximum of 1,000 records per request. Delivery reports are consumed on retrieval. For longer retention and aggregated data, use the Metrics API instead.

Use message-level reporting when you need to verify delivery outcomes for specific messages or investigate failures at a granular level.

For webhook configuration, payload details, retry cycles, and polling setup, see Send and track.




Related pages

Troubleshooting SMS
Diagnose delivery inconsistencies, cost issues, and reporting problems.

Subscriptions management
Set up event-driven notifications for SMS delivery events.

Send SMS in Infobip solutions
Choose a sending method and start generating traffic.