Analysis
Planned margin, pricing gaps, and cost and revenue per message
The Analysis section of the SSG Administration Portal is for checking whether customer prices and supplier costs make commercial sense — before traffic is sent, and after it has been sent.
Use it to:
- compare the planned sell price with the route cost for each destination
- find destinations that carried traffic but had no customer price
- watch average, minimum and maximum cost, revenue and margin per message over time
Analysis is available on cloud SSG instances. It is not shown on SSGLite.
Related sections:
- Pricing — customer prices used as revenue
- Routes — supplier coverage and costs
- Reports — traffic volumes, delivery and customer margin
- Financial — total revenue, cost and profit over a period
- Billing — invoices and billed amounts
Planned margin versus actual trafficAnalysis > Margin by destination uses the prices and route costs that are configured now. The per-message charts and Financial use amounts already applied to traffic.
Using analysis
Date range
Missing prices and the per-message charts have a date-range picker. The selected range is shown under the picker.
Missing prices defaults to the last 7 days. The cost, revenue and margin charts default to the current day.
Margin by destination has no date range: it always shows the prices and costs that are in force now.
Tables and charts
Tables support search, sorting, paging and Excel download of the current result set (all pages).
The per-message charts plot one point per hour. Hours with no priced traffic are shown as a gap, not as zero.
Data used by analysis
| View | Source | Retention (default) |
|---|---|---|
| Margin by destination | Current pricing-plan prices and SMSC-group route costs | Current configuration |
| Missing prices | Individual completed outbound message records with no revenue | Message records: three months |
| Cost / Revenue / Margin per message | Hourly aggregated traffic | Aggregates: at least five years |
See Data retention. Contact Support ([email protected]) if you need a different retention period.
Customer prices come from the pricing plan on the service used by the SMPP account. Supplier costs come from routes on the SMSC group. Monetary amounts on the per-message charts are converted to the instance base currency.
Margin by destination
Analysis > Margin by destination
Planned sell price versus route cost for each destination on a service. Use this when you change a pricing plan or supplier costs, or when you want to find destinations that would lose money before customers send traffic there.
- Select a Service. The first service is selected automatically when the page opens.
- The Pricing plan and Routing profile for that service are shown. Open either to edit prices or routing.
- Optionally filter the table to one country.
A summary above the table shows how many destinations are listed, how many have a negative margin, and the lowest margin percentage.
Negative-margin rows are highlighted.
| Column | Description |
|---|---|
| Country / Network | Destination |
| Price | Customer price from the service's pricing plan (with currency) |
| SMSC Group | SMSC group that provides the route for that destination |
| Submit cost | Supplier cost on submit (with currency) |
| Deliv cost | Supplier cost on delivery |
| Margin | Sell price minus submit cost minus delivery cost, in the instance base currency |
| Margin % | Margin as a percentage of the sell price |
Click a Price to open Pricing > Plan prices for that plan and country. Click an SMSC Group to open Suppliers > Routes for that group and country.
This view does not use traffic. A destination with a healthy planned margin can still show a poor result in Financial if the price was missing at send time, or if a different route carried the traffic.
To reject submits that would make a negative margin, see Services.
Missing prices
Analysis > Missing prices
Completed outbound (MT) messages in the selected period that have no revenue — usually because the pricing plan has no price for that country or network.
When a customer has a monetary balance and no price can be found, the submit is rejected. Traffic can still complete without revenue when the account is post-pay, or when the price was missing at send time and the message was accepted.
| Column | Description |
|---|---|
| Pricing plan | Plan on the service used by the SMPP account |
| Customer / SMPP account | Who submitted the traffic |
| Country / Network | Destination that had no price |
| Messages | Count of completed outbound messages with no revenue |
| First seen / Last seen | Earliest and latest submit times in the period |
Click a Pricing plan to open Pricing > Plan prices for that plan and country so you can add the missing price. You can also use Pricing > Plan prices from the page.
Rows are ordered by message count. This view uses individual message records, so it is limited to the message-record retention period.
Cost per message
Analysis > Cost per message
Average, minimum and maximum supplier cost per message over time, from hourly aggregates.
Costs are converted to the instance base currency. Min and max are the lowest and highest route-level average in that hour — not the cheapest or most expensive single message.
The upper pane plots:
- Min. cost
- Max. cost
- Avg. (mean) — total cost divided by the number of messages that have a cost
The lower pane plots volume:
- Volume (total) — all attempts in the hour
- Volume (with cost) — attempts that have a supplier cost
A gap between the two volume series means some traffic in that hour had no route cost (for example a missing or ignored route).
Revenue per message
Analysis > Revenue per message
Average, minimum and maximum customer revenue per message over time, from hourly aggregates.
Revenue is converted to the instance base currency. Min and max are the lowest and highest route-level average in that hour.
The upper pane plots Min. revenue, Max. revenue and Avg. (mean) (total revenue divided by the number of messages that have revenue). The lower pane plots Volume (total) and Volume (with revenue).
A gap between the two volume series means some traffic in that hour had no customer price. Use Missing prices to see which destinations and accounts were affected.
Margin per message
Analysis > Margin per message
Average revenue minus average cost for the same hour, in the instance base currency, from hourly aggregates.
The upper pane plots:
- Avg. revenue
- Avg. cost
- Avg. margin — average revenue minus average cost
The lower pane plots Volume.
Hours with no priced traffic are shown as a gap. This is the realised unit margin on traffic that was sent, not the planned margin on Margin by destination.
For totals rather than per-message averages, use Financial.
Updated about 1 hour ago