Communication report columns
Column definitions for communication reports. Each row in a communication report represents one message or service request scoped to a specific Journey (Moments flow) or campaign.
Columns are predefined; the report always includes the full set of columns listed below.
For how to create and configure communication reports, see Communication reports.
Columns
| Column | Description |
|---|---|
| Account name | Infobip account name associated with the traffic |
| User name | User who initiated the traffic. Blank if traffic was sent over the API. |
| Service name | Communication channel or service used (for example, SMS, WhatsApp, Email) |
| Traffic source | Source of the traffic (for example, API, Other, Moments/Flow, Broadcast) |
| Communication name | Campaign or Journey (Moments flow) name |
| Communication scheduled for | Scheduled time of the Journey (Moments flow) or campaign, if applicable |
| Communication start date | Start date of the Journey (Moments flow) or campaign, if applicable |
| Communication template | Template used in the Journey (Moments flow) or campaign, if applicable |
| From | Sender ID, phone number, or domain |
| To | Recipient phone number or address |
| Message ID | Unique identifier for the individual message |
| Bulk ID | Identifier for the batch the message belongs to |
| Send at | Time the request was submitted to the Infobip platform |
| Done at | Time the request reached a final status |
| Status | Delivery outcome (for example, DELIVERED, REJECTED). See Response status and error codes. |
| Reason | Detailed status code (for example, DELIVERED_TO_HANDSET). See Response status and error codes. |
| Error group | High-level error category. See Response status and error codes. |
| Error name | Detailed error description. See Response status and error codes. |
| Action | Recommended action based on the status or error, if applicable |
| Country prefix | Country dialing prefix of the destination |
| Country name | Destination country |
| Network name | Destination mobile operator |
| Original MCC | Mobile Country Code of the original destination network |
| Original MNC | Mobile Network Code of the original destination network |
| Original MCC MNC | Combined Mobile Country Code and Mobile Network Code |
| Message type | Message type (for example, Standard SMS, Concatenated SMS). SMS only. |
| SMS type | SMS encoding type. SMS only. |
| Text | Message text content. Applicable for messaging channels only; blank for service requests. |
| Message length | Total character length of the message. SMS only. |
| Messages count | Number of SMS parts for concatenated messages. SMS only. |
| Clicks | Total number of link clicks. Requires shortened URLs with tracking enabled. |
| Paired message ID | Identifier pairing related messages, if applicable |
| Data payload | Custom metadata attached to the message request, if provided. See Data payload. |
| Purchase price | Price charged per message or per second, depending on the channel. Visible only if your role grants access to financial data. |
NOTEFor billing and cost analysis, use Financial reports or the Billing Usage API. Both follow the same monthly cycles, currency format, and billing structure as your invoices. For definitions of the fields used in Financial reports and the Billing Usage API, see Cost fields in the Billing data reference.
Was this page helpful?