Reporting
Reporting on customers, traffic (inbound and outbound) and suppliers
The Reports section of the SSG Administration Portal provides aggregated traffic, revenue, cost, delivery and latency reports for your instance. Use it to see how much traffic customers are sending, where it is going, which suppliers are carrying it, and how quickly it is being delivered.
Message-level Call Detail Records (CDRs) are documented separately: CDRs.
Related reporting elsewhere in the portal:
- Dashboard — live volumes, delivery state, revenue and cost widgets
- Customer Reporting tab — traffic by SMPP account for a single customer
- Billing > Reporting — billed versus actual volumes and invoiced revenue. See Billing
- Status > Message lookup — look up an individual message
- Management API traffic report — hourly or daily volumes for an SMPP account
Using reports
Most reports share the same controls.
Date range
Select the start and end dates for the period you want to analyse. The selected range is shown under the picker.
Volume reports default to a recent period. Delivery latency defaults to the current day.
Time zone
Choose the time zone used to interpret the date range and to group hourly/daily totals. The last time zone you selected is stored in your user preferences and reused the next time you open a report.
Granularity
Where shown, the H / D / W / M control groups the chart and table by hour, day, week or month. Day is the default.
Customer filter
Where shown, a customer drop-down limits the report to one customer. Leave it on All customers to include every customer.
Tables
Most reports show a chart and a table. Tables support:
- Excel — download the current result set (all pages)
- sorting, paging and, on many customer and supplier reports, grouping and a column menu
- footer totals for volume, delivered count, revenue, cost and margin
A delivery percentage (Del% or %) below 90% is highlighted so destinations or customers with poor delivery stand out.
Data used by reports
Most volume, country, customer, revenue and supplier reports are generated from aggregated traffic data. These aggregates are retained for at least five years by default.
The following reports read individual message records and are therefore limited to the message-record retention period (three months by default):
- Reports > Customers > Error
- Reports > Queued
- Reports > Delivery latency
- Reports > CDRs
See Data retention. Contact Support ([email protected]) if you need a different retention period.
Prices shown in reports come from the customer's pricing plan. Supplier costs come from routes.
MT and MO volume
Reports > MT and MO volume
Overall mobile-terminated (MT / outbound) and mobile-originated (MO / inbound) volume over the selected period.
The chart shows MT as columns and MO as a line. The table lists each interval:
| Column | Description |
|---|---|
| Date | Interval start (hour, day, week or month, according to granularity) |
| MT (all) | Outbound messages submitted by customers |
| MT (delivered) | Outbound messages that reached the delivered state |
| % | Delivered MT as a percentage of all MT |
| MO | Inbound messages |
| Total MT+MO | Combined volume |
An optional customer filter is available.
Countries
Reports > Countries
MT volume by destination country over the selected period.
The chart stacks volume by country over time. The table lists:
| Column | Description |
|---|---|
| Name | Destination country |
| Messages | MT volume |
| Delivered | Messages in the delivered state |
| Del% | Delivered as a percentage of messages |
Customers
Reports > Customers
MT and MO volume by customer over the selected period.
The chart stacks volume by customer over time. The table lists each customer with MT (all), MT (delivered), %, MO and Total MT+MO. Use the customer-name column filter to include or exclude customers.
The Customers section has further breakdowns.
Country
Reports > Customers > Country
MT volume by customer, service, SMPP account, system ID and destination country. Columns include Messages (MT), Delivered and Del%.
Country detail
Reports > Customers > Country > Country detail
The same breakdown as Country, with a Date column (one row per day) so you can see how a customer's traffic to a country changed during the period.
Network
Reports > Customers > Network
MT volume by customer, service, account, system ID, destination country and network, with delivered count and Del%.
Revenue
Reports > Customers > Revenue
MT volume with billed amounts from the customer's pricing plan, broken down by customer, service, account, system ID, country and network.
| Column | Description |
|---|---|
| Currency | Pricing-plan currency |
| Amount | Sum of message prices (revenue) |
| Messages (MT) | Volume |
| Delivered | Messages in the delivered state |
| Del% | Delivered as a percentage of messages |
Revenue detail
Reports > Customers > Revenue > Revenue detail
The same breakdown as Revenue, with PPM (average price per message: amount divided by volume) for the row.
Error
Reports > Customers > Error
MT volume by customer, service, account, system ID, country, delivery Status and Error.
Status values include Scheduled (0), Enroute (1), Delivered (2), Expired (3), Cancelled (4) and Undelivered (5). The Error value is normally the delivery error returned by the supplier SMSC.
Use this report to find which customers, destinations or accounts are generating failures. This report uses individual message records.
SMSC
Reports > Customers > SMSC
MT volume by customer, account, system ID, country, network and the supplier SMSC that carried the traffic.
| Column | Description |
|---|---|
| Enroute | Messages not yet in a final state |
| Undeliverable | Messages in a failed final state |
| Not delivered | Enroute plus failed (everything that is not delivered) |
| Delivered | Messages in the delivered state |
| Del% | Delivered as a percentage of total |
| Total | All messages in the row |
Margin
Reports > Customers > Margin
Revenue, supplier cost and margin for customer traffic, converted to the instance base currency.
| Column | Description |
|---|---|
| Customer / Account / System ID | Who submitted the traffic |
| Country / Network | Destination |
| Supplier / SMSC | Where the traffic was submitted |
| Revenue | Customer price, in base currency |
| Cost | Supplier cost, in base currency |
| Margin | Revenue minus cost |
| Volume | Message count |
Negative or zero margin is highlighted.
Suppliers
Reports > Suppliers
Volume and cost of MT SMS submitted to your suppliers. Filter by supplier using the drop-down (labelled as a customer filter on other reports).
Summary
Reports > Suppliers > Summary
Totals by supplier and SMSC for the period.
| Column | Description |
|---|---|
| Supplier / SMSC | Supplier connection that received the traffic |
| Currency | Cost currency from the supplier route |
| Cost | Sum of supplier costs |
| Messages | Volume submitted to that SMSC |
| Delivered | Messages in the delivered state |
| Del% | Delivered as a percentage of messages |
Cost totals are shown per currency.
Detail
Reports > Suppliers > Detail
The same figures as Summary, broken down by destination country and network, with optional hour/day/week/month granularity on the chart.
Queued
Reports > Queued
MT messages that have been accepted from customers but have not yet been submitted to a supplier SMSC.
| Column | Description |
|---|---|
| Customer / Service / System ID | Who submitted the messages |
| Country / Network | Destination |
| Total | Count of queued messages |
An empty table with No queued messages means every accepted message in the period has been submitted onward (or there was no traffic).
A large or growing queued volume can indicate a supplier connection problem, a routing gap, or throttling. Check Status > SMSCs and Routing. This report uses individual message records.
Delivery latency
Reports > Delivery latency
How long messages take to reach a final delivered state. Select a date range (defaults to today). Percentages are of all messages submitted in the interval, not only those that were delivered.
End-to-end delivery
Time from customer submit to the platform (ts_esme_submit) until the message is delivered (ts_completion):
- Delivered in under 5, 15, 45 and 60 seconds, and 60 seconds or more — each tile shows the percentage and the message count
- Distribution of messages delivered within 60 seconds
- Distribution of messages delivered within 15 minutes
SSG–SMSC–mobile delivery
Time from platform submit to the supplier (ts_submit) until delivery (ts_completion), plotted per SMSC for messages delivered within 60 seconds and within 15 minutes.
Live submit and delivery latency for the current day is also available under Status > Latency (submit) and Status > Latency (delivery). This report uses individual message records.
CDRs
Reports > CDRs and Reports > CDRs > Advanced
Download message-level records for a date/time range, customer, SMPP account, supplier or SMSC.
Use Reports > CDRs > Advanced for faster downloads. It supports customer, supplier and full (customer plus supplier) CDRs.
See CDRs for record types (completed, all, pending, failed) and field definitions.
CDRs can also be retrieved with the Management API.
Updated about 2 hours ago