SMSC SMS volume, delivery, and spend
SMSC SMS campaign report for clients
Reportkey reads the sent message history and spend summary from the smsc.ru API and builds a client report section: how many SMS went out, how many were delivered, what they cost and how delivery split by mobile operator, region and sender name.
Sign up, paste your SMSC API key on the integrations page and pick the account in a project. Your first report in 5 minutes.
- The SMSC key is entered once and reused across projects.
- Sent, delivered, spend and cost per SMS by week and month.
- SMS shares one report with ads and Metrica, plus AI insights and branding (not on every plan).
TL;DR
SMSC integration: paste the API key from your smsc.ru account settings once on the integrations page, pick the account in a project, and SMS volume, delivery and spend for the period reach the client on schedule as a link or PDF next to ads and website analytics.
An SMS campaign report from SMSC without history exports
SMSC (smsc.ru, known in Russian as SMS Tsentr) is an SMS gateway used by clinics, salons, delivery services, online stores and apps that confirm logins by code. Both promotions and service messages go through it. Reporting on this channel is awkward: the account has history and a balance but no monthly summary of volume, delivery and money that a client can read. Reportkey builds it for you. It reads sent message history and the spend summary through the SMSC API and turns them into a recurring report section.
Connecting SMSC with an API key
Create the key in your smsc.ru account settings, then paste it on the Reportkey integrations page. The connection is checked at once and saved as a shared account for every project. If you manage several clients, add one connection per SMSC account.
SMSC can restrict API calls to specific IP addresses. If that setting is on, add Reportkey addresses to the list. The key is used only to read history and statistics: nothing is sent and no balance is spent. If the key is deleted, the connection asks for a new one and project settings stay.
SMSC statistics: volume and spend
The summary method returns the number of SMS sent and the amount charged for a period. The first report block is built from them:
- SMS sent — billed messages per week or month.
- Spend — what SMSC charged for sending.
- Average cost per SMS — spend divided by count, useful when text length or the share of international numbers changes.
Spend is channel cost, not revenue or advertising results. Payback needs website or CRM data alongside it.
SMS delivery report by status
Message history includes, for each SMS, the send date, status code and name, error code, cost and part count. The delivery block shows delivered and undelivered messages, delivered share and cost per delivered SMS by day. Growing failures are a reason to clean the phone list: outdated numbers and typos burn money without results.
Delivery by operator and region
For every message SMSC identifies the country, operator, region and network code. The report groups delivery and cost by these fields and by sender name. You can spot a sudden drop in delivered share at one carrier or international sends costing more than expected. The sender name split separates service messages from promotions when they use different signatures.
What to keep in mind about SMS spend
Message count and billed parts differ for long texts. Delivery statuses update after sending, so fresh messages may still be in transit. Opens are not tracked, and clicks exist only for short links. SMSC rate-limits identical requests, so large histories load page by page.
SMS next to the website, calls and email
Add Yandex Metrica visits and goals tagged by short links to show what recipients did. If customers call after an SMS, connect Calltouch calls, and Roistat shows money by channel. The same business’s email channel fits a block from Unisender. Other messaging tools are on the email integrations page; see the freelancer demo report and pricing for the free trial and plans.
Metrics
What goes into the SMSC report
These are the metrics that the SMSC integration already brings into Reportkey reports.
SMS sent
Delivered
Delivery rate
Spend
Cost per SMS
What this integration adds to the report
SMS volume, delivery, and spend
Pricing
SMSC reporting: plans and free trial
14 days free, no card required. Prices and plan limits are on the pricing page.
Use cases
Why teams connect SMSC to Reportkey
Real reporting jobs, typical pain points, and the outcomes teams get from SMSC in client reports.
Pain points
- Accounting asks what SMS cost last month, and the marketer digs through payment history and splits the total between promotions by hand.
- The client says messages are not reaching subscribers of one carrier, yet nobody collects delivery status by operator on a regular basis.
- Long texts are billed as several parts, so the cost per message in the report never matches the figure in the contract.
SMSC
A clinic or salon chain sending appointment reminders
SMSC sends reminders and confirmations. Once a month the manager gets a report showing how many messages went out, the delivered share, the cost, and which carriers have the most failed deliveries.
SMSC
An online store running SMS promotions
Promotions go out by SMS and orders are tracked on the website. One document shows the volume and spend of an SMS campaign next to Yandex Metrica visits from short links, so you can tell whether the send paid off.
SMSC
An agency managing SMS for several clients
Each client has its own SMSC account and its own Reportkey project. The report goes out under the agency brand and replaces manual exports of message history into a spreadsheet.
Report preview
How SMSC appears inside the report
The report keeps the familiar Reportkey layout: source sections and period comparison.
Cards for SMS sent, delivered share, spend and average cost versus last month, followed by a delivery table by operator and region with message count, parts and cost.
How to connect
Three steps to the first report
Connect the account once, choose the reporting scope, and save the setup for recurring client reports.
01
Connect the account
Save the SMSC connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the SMSC account and mailings that should supply delivery, opens, and clicks to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ
Frequently asked questions
Short answers about how the integration works in Reportkey today.
What do I need to connect SMSC to Reportkey?
An API key created in your smsc.ru account settings. Paste it once on the integrations page and reuse it in any project. If IP restrictions for API access are enabled in SMSC, add Reportkey addresses to the allowed list, otherwise the service will reject requests.
Why does the SMS count differ from the number of parts?
A long message is split into several parts, each billed separately. SMSC history stores the part count per message, so the report shows both messages and parts. Average cost per SMS is spend for the period divided by the SMS count from the service summary.
Can I see SMS opens and clicks?
SMS opens are not tracked, because a phone does not tell the sender whether a message was read. Clicks are visible only through short links placed in the text, and on-site actions through web analytics tags on those links.
Why do some messages from the last day have no final status?
Carriers report delivery status some time after sending. Recent messages may still be in transit, so the delivered share for the final hours of a period is understated. Closed periods such as last week work best for regular reports.
Is the spend figure the campaign budget?
It is the amount SMSC charged for sending during the period. Account top-ups are not part of it, and it does not show the financial result of a send. Put website orders next to it to judge payback.
How often can the report be refreshed?
SMSC limits how often identical history and summary requests can be made and returns an error when calls come too fast. Reportkey loads history page by page, a thousand messages per request, sequentially. That is enough for daily, weekly and monthly reporting.
Related integrations
Often connected together
Working sources that teams usually add to the same report.
SMSC SMS campaign report for clients
Sign up, paste your SMSC API key on the integrations page and pick the account in a project. Your first report in 5 minutes.