Detailed report columns
Column definitions for detailed reports across all channels and services. Each row in a detailed report represents one message, call, or service request.
Columns are grouped into: common columns that apply across channels and services, columns shared across messaging channels, and channel-specific or service-specific additions. The columns offered depend on the channels and services the report covers, and you then choose whether the report contains all of those columns or only the ones you select.
For how to create and configure detailed reports, see Detailed reports.
Common columns [#common-columns]
These columns apply broadly across channels and services. Which of them appear in a given export depends on the columns selected when the report is created, and the default selection differs by channel. For the Columns option, see Detailed reports.
| 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, Number Lookup) |
| Traffic source | Source of the traffic (for example, API, Other, Moments/Flow, Broadcast) |
| To | Recipient phone number, email address, or WebRTC identity |
| Bulk ID | Identifier for the batch the message or request belongs to |
| Message ID | Unique identifier for the individual message or request |
| Send at | Time the request was submitted to the Infobip platform, or when a Journey was launched |
| Done at | Time the message or request reached a final status |
| Status | Delivery or request outcome (for example, DELIVERED, REJECTED). See Response status and error codes. |
| Reason | Detailed status code (for example, DELIVERED_TO_HANDSET, UNDELIVERABLE_NOT_DELIVERED). See Response status and error codes. |
| Error group | High-level error category (for example, No Errors, Handset errors). 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 |
| Communication name | Campaign, Journey (Moments flow), or Broadcast name, if applicable |
| Communication ID | Identifier of the Campaign, Journey (Moments flow), or Broadcast, if applicable |
| Communication scheduled for | Scheduled time of the Campaign, Journey (Moments flow), or Broadcast, if applicable. Shows Immediate when the communication was not scheduled. |
| Communication start date | Start date of the Campaign, Journey (Moments flow), or Broadcast, if applicable |
| Communication template | Template used in the Campaign, Journey (Moments flow), or Broadcast, if applicable |
| Purchase price | Price charged per message or per second, depending on the channel. Visible only if your role grants access to financial data. |
| Purchase currency | Billing currency. Visible only if your role grants access to financial data. |
| Charged amount | Total amount charged for the message or request. 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.
Messaging channel columns [#messaging-channel-columns]
These columns are shared across messaging channels rather than belonging to any single one. They do not apply to platform services (Number Lookup, Email Validation, and Mobile Identity). The Applies to column shows where each one is available by default.
| Column | Description | Applies to |
|---|---|---|
| Application ID | Multitenant application identifier | All messaging channels |
| Entity ID | Multitenant entity identifier | All messaging channels |
| From | Sender ID, phone number, or domain | All messaging channels |
| Direction | Traffic direction: INBOUND or OUTBOUND | All messaging channels |
| Campaign reference | External campaign reference identifier, if set | All messaging channels |
| Data payload | Custom metadata attached to a message (callbackData in the API). See Data payload. | All messaging channels |
| Seen at | Time the recipient's device reported the message as seen. Recipients can turn off read receipts, so this column can be blank even when the message was read. For the aggregate Seen metric, see Engagement metrics. | Available by default in Facebook Messenger, In-App, Live Chat, Mobile Push, RCS, Viber, and WhatsApp reports |
NOTEA report can also contain columns that exist only for your account. These are generated from the keys in the Data payload column, so their names depend on the metadata you attach to your messages.
Channel-specific columns
SMS and MMS [#sms-mms]
| Column | Description |
|---|---|
| Sender type | Type of sender address used. For the values, see Sender types in the Messaging metrics reference. |
| Message type | SMS message type (for example, Standard SMS, Concatenated SMS) |
| Message length | Total character length of the message |
| Messages count | Number of SMS parts for concatenated messages |
| Network name | Destination mobile operator |
| Country name | Destination country |
| Country prefix | Country dialing prefix of the destination |
| 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 of the original destination network. The MCC is always three digits, followed by an MNC of two or three digits depending on the MCC. |
| Principal entity ID | India DLT Principal Entity ID registered for the sender. See India DLT registration. |
Email [#email]
| Column | Description |
|---|---|
| Subject | Email subject line |
| Opens | Total number of times the email was opened |
| Device type | Device type of the recipient at time of open (for example, desktop, mobile) |
| Device name | Device name of the recipient at time of open |
| Client OS | Operating system of the recipient at time of open |
| Total clicks | Total number of link clicks including repeat clicks |
| Click date and time | Timestamp of each link click |
| First click date and time | Timestamp of the first link click |
| Last click date and time | Timestamp of the most recent link click |
| City | City of the recipient at time of open, based on IP geolocation |
| Country | Country of the recipient at time of open |
| Complaint on | Timestamp when a spam complaint was filed, if applicable |
| Browser link | Online version link for the email, if enabled |
WhatsApp [#whatsapp]
| Column | Description |
|---|---|
| Template name | Name of the WhatsApp template used |
| Template ID | Identifier of the WhatsApp template used |
| Template category | Template category: MARKETING, AUTHENTICATION, or UTILITY |
RCS [#rcs]
| Column | Description |
|---|---|
| Network name | Destination mobile operator |
| Country name | Destination country |
| Traffic type | Additional traffic categorization, often blank. For the values, see Traffic types by channel in the Billing data reference, which covers WhatsApp, RCS, and Viber Business Messages. This column is available by default in RCS reports. |
OTT channels [#ott-channels]
Viber Business Messages, Viber Bots, Apple Messages for Business, Facebook Messenger, Telegram, Instagram (Instagram Direct Messaging), Kakao (Kakao Alim Talk, Kakao Brand Message, Kakao Sangdam), LINE (LINE Official Account, LINE Official Notifications), and Zalo (Zalo Notification Services, Zalo Follower) reports draw on the common columns and messaging channel columns listed above, but coverage varies by channel. Some OTT reports contain only a few of those columns, and some channels add their own columns, such as engagement timestamps and click counts.
Voice and Video [#voice-video]
Voice and Video reports contain the common columns listed above plus the following. Many columns apply only to specific Voice and Video features; noted in the description where applicable.
Call identification and routing [#call-identification-and-routing]
| Column | Description |
|---|---|
| Feature | Voice and Video feature used (for example, IVR, Number Masking, Click-to-Call, SIP trunking) |
| Direction | Call direction: INBOUND or OUTBOUND |
| From (caller ID) | Caller's phone number or WebRTC identity |
| Forwarded to | Phone number to which the call was forwarded. Applicable for IVR call forwarding. |
| Answered by | Phone number that answered a forwarded call. Applicable for IVR call forwarding. |
| Number of retries | Number of retry attempts if retry was configured. Applicable for Voice messages, Click-to-Call, and outbound IVR. |
| Call identifier | Unique identifier for the full call, covering both inbound and outbound legs |
| Correlation identifier | Unique identifier that correlates related call legs |
| Dialog ID | Dialog identifier. See Calls for details. |
| Calls configuration ID | Identifier of the Calls Configuration used by the application that placed the call. See Calls for details. |
Call timing [#call-timing]
| Column | Description |
|---|---|
| Start time | Time when the call started ringing or was initiated |
| Answered time | Time when the call was answered |
| End time | Time when the call ended |
| Duration | Total call duration in seconds |
| Charged duration | Billed call duration after the billing model is applied (for example, 60/60 rounding) |
| Billing model | Billing interval applied to the call (for example, 1/1, 15/15, 60/60) |
| Price per second | Price charged per second for the call |
Geography [#geography]
| Column | Description |
|---|---|
| Country name | Destination country |
| Country prefix | Destination country dialing prefix |
| Network name | Destination network (for example, Germany Landline, WebRTC) |
| Sender country name | Caller's country name, if applicable |
| Sender country prefix | Caller's country dialing prefix, if applicable |
| Sender network name | Caller's network name, if applicable |
SIP trunking [#sip-trunking]
| Column | Description |
|---|---|
| Client IP address | IP address of the Voice platform. Applicable for SIP trunking. |
| From SIP | Caller's phone number for SIP trunk outbound calls |
| To SIP | Destination phone number for SIP trunk outbound calls |
| External call identifier | Unique call identifier for SIP trunk outbound calls |
| SIP trunk ID | ID of the SIP trunk used |
| SIP trunk name | Name of the SIP trunk used |
| SIP trunk type | SIP trunk type (for example, Static, Registered, PROVIDER) |
| SIP trunk provider type | SIP trunk provider type (for example, FRESHWORKS) |
IVR [#ivr]
| Column | Description |
|---|---|
| IVR scenario name | IVR API scenario name, if applicable |
| Text | Text used for text-to-speech synthesis, if applicable |
| Response code | DTMF code entered by the end user. Empty if the user did not press anything, and null if the user did not reach a Collect action in the IVR. |
| IVR responses | DTMF response codes entered by the end user, as a JSON object |
| IVR mapped responses | Meaning of DTMF codes as defined by the client (for example, DTMF "1" mapped to "positive feedback") |
| Spoken input | Full text spoken by the user as a JSON object, when using the Capture option in an IVR |
| Matched spoken input | Key phrases that matched the user's spoken input as a JSON object, when using the Capture option in an IVR |
Communication (Journeys, Moments flows, and Broadcast) [#communication]
Voice and Video reports carry the same communication columns as every other channel. For Communication name, Communication ID, Communication scheduled for, Communication start date, and Communication template, see Common columns.
Video [#video]
| Column | Description |
|---|---|
| Video | Whether the call included video. Values: true or false. |
| From display name | Display name of the caller for video calls |
| To display name | Display name of the recipient for video calls |
| From device | Caller's device for video calls |
| To device | Recipient's device for video calls |
Mobile Push and In-App Messages [#mobile-push]
| Column | Description |
|---|---|
| Application code | Identifier of the mobile application profile that sent the message. See Mobile application profile. |
| Last entered time | Time when the user last entered a geofenced area, if applicable |
| Area ID | Identifier of the geofenced area, if applicable |
| Area name | Name of the geofenced area, if applicable |
Service columns
Mobile Identity [#mobile-identity]
Mobile Identity reports contain the common columns listed above plus the following.
| Column | Description | Applies to |
|---|---|---|
| Data payload | Service response as a JSON object. Unrelated to the Data payload column in messaging reports, which carries custom metadata. | All Mobile Identity requests |
attributeName | Name of the identity attribute checked | National identity number |
consentGranted | Whether user consent was granted for the check | National identity number, SIM Swap |
period | Number of days checked for SIM swap activity | SIM Swap |
result | Outcome of the identity check (for example, MATCHED, true, false) | National identity number, SIM Swap |
Number Lookup [#number-lookup]
Number Lookup reports contain the common columns listed above plus the following.
Network and country columns [#network-country-columns]
| Column | Description |
|---|---|
| Network name | Mobile operator identified by the lookup |
| Country name | Country identified by the lookup |
| Country prefix | Country dialing prefix identified by the lookup |
HLR columns [#hlr-columns]
These columns come from HLR lookup. Whether they appear at all depends on the HLR lookup configuration applied to the request, so a report that covers requests made without HLR lookup may omit them or leave them blank.
The platform treats these columns as a single group. The Group column below tells you which part of the lookup each value describes: the subscriber, the subscriber's original (home) network, the network a number was ported to, or the network the subscriber was roaming on.
| Column | Group | Description |
|---|---|---|
| IMSI | Subscriber | International Mobile Subscriber Identity: unique identifier for the subscriber's SIM |
| Serving MSC | Subscriber | Mobile Switching Center serving the subscriber at the time of the lookup |
| Serving HLR | Subscriber | Home Location Register of the subscriber |
| Is number OK | Subscriber | Whether the number is valid and reachable |
| Original network name | Original | Name of the subscriber's home mobile network |
| Original country name | Original | Country of the subscriber's home network |
| Original country prefix | Original | Dialing prefix of the subscriber's home network country |
| Original country code | Original | Country code of the subscriber's home network, where available |
| Original MCC | Original | Mobile Country Code of the subscriber's home network |
| Original MNC | Original | Mobile Network Code of the subscriber's home network |
| Original MCC MNC | Original | Combined Mobile Country Code and Mobile Network Code of the subscriber's home network. The MCC is always three digits, followed by an MNC of two or three digits depending on the MCC. |
| Is ported | Ported | Whether the number has been ported to another network |
| Ported network name | Ported | Network the number was ported to |
| Ported country name | Ported | Country of the network the number was ported to |
| Ported country prefix | Ported | Dialing prefix of the ported network country |
| Ported country code | Ported | Country code of the ported network, where available |
| Is roaming | Roaming | Whether the subscriber was roaming at the time of the lookup |
| Roaming network name | Roaming | Network the subscriber was roaming on at the time of the lookup |
| Roaming country name | Roaming | Country the subscriber was roaming in |
| Roaming country prefix | Roaming | Dialing prefix of the roaming country |
| Roaming country code | Roaming | Country code of the roaming country, where available |
| Roaming MCC MNC | Roaming | Combined Mobile Country Code and Mobile Network Code of the roaming network |
Email Validation [#email-validation]
Email Validation reports contain the common columns listed above plus the following. For a worked example of these values, see Email validation over Broadcast.
| Column | Values | Description |
|---|---|---|
| Email address | — | The email address that was validated |
| Did you mean (suggestion) | — | A similar alternate address that may be valid, offered when the submitted address may contain an error |
| Mailbox valid | Yes, No, Unknown | Whether the email address is valid and able to receive messages |
| Syntax valid | Yes, No | Whether the email address has correct syntax. When No, a suggested correction may be included. |
| Catch all | Yes, No | Whether the domain is a catch-all server. Catch-all servers accept all addresses for the domain regardless of whether they exist, so a Yes result does not confirm the address is valid. |
| Disposable address | Yes, No | Whether the email address is a temporary address that may expire |
| Rolebased address | Yes, No | Whether the email address is a mailing group rather than an individual mailbox (for example, support@example.com) |
| Reason | INBOX_FULL, UNEXPECTED_FAILURE, THROTTLED, TIMED_OUT, TEMP_REJECTION, UNABLE_TO_CONNECT | Additional detail when Mailbox valid is Unknown. null when Mailbox valid is Yes or No. |
| Detailed reasons | known_hardbounce, mailbox_full, disposable_address, and similar | Specific explanation of why the address received its Mailbox valid status. Provided when Mailbox valid is No or Unknown. |
| Risk | Low, Medium, High, Unknown | Likelihood that sending to the address will bounce and damage your sender reputation |
NOTEThe Email Validation export contains two columns named Reason, and they hold different values. The first, in the delivery status block directly after Status, is the request status code described in Common columns. The second, directly after Rolebased address, is the validation reason described above. Because they share a name, select them by position rather than by name: with the default column selection, the status Reason is the 8th column and the validation Reason is the 19th.
Was this page helpful?