Yandex Cloud Notification Service pricing policy
What goes into the cost of using Cloud Notification Service
When using Cloud Notification Service, you are charged for the following:
- Processing push notification sending events (for both mobile and browser notifications).
- Processing registration requests and supporting the registration of individual sender names for SMS text messaging with Beeline, MegaFon, MTS, and T2.
- Processing text message notification sending events within Russia.
Note
By default, Cloud Notification Service has limits on sending notifications. For more information, see Yandex Cloud Notification Service quotas and limits.
All prices below do not include VAT.
Push notification sending events
Push notifications are sent to both mobile platforms, such as Google Android and Apple iOS, and to browsers through WebPush.
Mobile and browser push notifications are added up when billing.
Cost calculation example
Let’s assume 1,500 push notifications were processed as sent to mobile and 700 more, to browser, over a month.
This means the total billable events are 1,500 + 700 = 2,200. The first 1,000 events are free of charge. For the rest 1,200, you will pay:
(1,500 + 700 - 1,000) / 1,000 × $0.825000 = 1,200 / 1,000 × $0.825000 = $0.99
$0.99: Total cost of sending 2,200 push notifications per month.
Where:
- 1,500: Mobile push notifications.
- 700: In-browser push notifications.
- 1,000: Non-billable events.
- $0.825000: The cost of processing 1,000 CNS push notification events, from 1,000 to 500,000 notifications per month.
Registering individual sender names
With an individual sender name, one can process text message notification sending events on behalf of a user other than Yandex Cloud (shared sender). The name is registered with Russian mobile operators: Beeline, MegaFon, MTS, and T2.
Registering an individual sender name is billed monthly, until such a name is unregistered upon the customer’s request.
The monthly cost is fixed and does not depend on the number of days of use, processed notifications, or sent text messages. This amount will be charged to you even if no notifications were sent.
Cost calculation example
Let’s assume you registered an individual sender name for processing text message sending events on January 20, and then unregistered it on March 5.
This means three months are billable: January, February, and March.
Cost calculation of using a registered name:
$83.333320 × 3 = $250.00
Total: $250.00
Where:
- $83.333320: Cost of registering a CNS sender name for 1 month.
- 3: Number of months.
Text message notification sending events
You can only send text messages across Russia. You pay for each processed message sending event. A message over 140 B (160 Latin characters or 70 Cyrillic characters) is broken down into a few parts, each of which is billable.
The cost of processing an event depends on the text message’s type: whether it is a commercial, authentication, service, or transaction message. All text messages are considered commercial by default. If you want your messages billed as another event type, you need to create a template first. Currently, to do this, you need to send examples of your messages to our support
For some operators, billing may be done in packages. The cost of such packages is calculated individually for each subscriber that gets text messages. See the cost calculation example below for more information.
Sandbox messages (those sent when the text message notification channel is in the Sandbox status) are charged as per the relevant pricing.
Cost calculation example
Let’s assume that, under a shared sender name, there are 100 messages sent to MTS subscribers, and 100 more, to Beeline subscribers (out of those, 30 were sent to the same subscriber, and 70 more, to different subscribers), for processing.
Since you do not have any registered templates, all events are deemed commercial.
Cost of processing 100 events (for MTS subscribers):
$0.044583 × 100 = $4.46
Where:
- $0.044583 is the cost of processing one advertising event for MTS subscribers, up to 400,000 in number.
- 100: Number of notifications.
Cost of processing 70 events (for different Beeline subscribers):
$0.064583 × 70 = $4.52
Where:
- $0.064583: Cost of processing one advertising event for Beeline subscribers, up to two events per subscriber.
- 70: Number of notifications.
Cost of processing 30 events (for a one Beeline subscriber):
Processing of the first event: $0.064583.
Processing of the second event: $0.064583.
When processing the third event, the package is activated. The cost of a package of 3 to 5 events per subscriber: $0.157500. The forth and fifth events are included in this package.
When processing the sixth event, the package is activated. The cost of a package of 6 to 10 events per subscriber: $0.116833.
When processing the eleventh event, the package is activated. The cost of a package of 11 to 20 events per subscriber: $0.223000.
Starting from the 21st event, each event is billed at this price: $0.063833.
Total cost of processing 30 events for a single subscriber:
$0.064583 × 2 + $0.157500 + $0.116833 + $0.223000 + $0.063833 × 10 = $1.26
Total cost of processing all 200 text message sending events:
$4.46 + $4.52 + $1.26 = $10.24
Total: $10.24
Where:
- $4.46: Cost of 100 messages for MTS subscribers.
- $4.52: Cost of 70 messages for different Beeline subscribers.
- $1.26: Cost of 30 messages for a single Beeline subscriber.
Prices for the Russia region
Note
Yandex Cloud resources are priced differently in different regions. For more information about the available regions, see Regions.
Your payment currency is determined by your contracting legal entity. For more information on creating an account, see Registering an account in Yandex Cloud.
You are charged for push notifications sent to mobile devices and through browsers. The cost for sending text messages depends on the mobile network provider and message type.
Note
If you want to send more notifications, contact our support