Интеграция с Unisender GO/en: различия между версиями
Материал из SmartPlayer
Новая страница: «Integration with Unisender GO» |
Новая страница: «== '''Description of the Situation''' == To expand the capabilities of the SmartPlayer platform for sending == '''Differences Between Unisender and Unisender GO''' == '''Unisender''' is a marketing service for email campaigns. It includes a wide range of marketing tools — subscriber list management, A/B testing, segmentation, subscription form creation, and distribution via not only email but also SMS and Viber.<br> '''Unisender GO''' is a transport layer...» |
||
| Строка 1: | Строка 1: | ||
== '''Description of the Situation''' == | |||
== ''' | To expand the capabilities of the SmartPlayer platform for sending | ||
== '''Differences Between Unisender and Unisender GO''' == | |||
== ''' | '''Unisender''' is a marketing service for email campaigns. It includes a wide range of marketing tools — subscriber list management, A/B testing, segmentation, subscription form creation, and distribution via not only email but also SMS and Viber.<br> | ||
'''Unisender''' | '''Unisender GO''' is a transport layer for sending emails, which requires integration by a developer or system administrator. It is a set of API methods and SMTP servers that only send messages, but do so cost-effectively and efficiently, providing highly detailed information for each individual message. | ||
'''Unisender | == '''Action Algorithm''' == | ||
== ''' | # The first step to creating a connection via Unisender GO is to connect to the server. | ||
# | # Next, you need to go to the server application following the path: <code>/home/smartplayer/smartplayer/backend/app/config</code>. | ||
# | # After that, the user needs to create a configuration file named "local.js" in .json format, where the connection parameters for Unisender GO are specified. Two types of parameters are used: host (server address) and key (access key). | ||
# | # Run the CLI command: ''./cli.js test send-mail''. | ||
# | # Send a test email. | ||
# | == '''Additional Information''' == | ||
== ''' | If this article does not help you use the functionality as intended or if you still have questions after reading it, you can raise them in the "Discussions" section at the top of the page. | ||
[[File:Обсуждение_интеграции.png|thumb|center| Example of the "Discussions" tab on the wiki page |800px]] | |||
[[File:Обсуждение_интеграции.png|thumb|center| | Additional information can also be found on the page [[How users interact with the "Discussions" section]]. | ||
Текущая версия от 10:26, 14 июля 2025
Description of the Situation
To expand the capabilities of the SmartPlayer platform for sending
Differences Between Unisender and Unisender GO
Unisender is a marketing service for email campaigns. It includes a wide range of marketing tools — subscriber list management, A/B testing, segmentation, subscription form creation, and distribution via not only email but also SMS and Viber.
Unisender GO is a transport layer for sending emails, which requires integration by a developer or system administrator. It is a set of API methods and SMTP servers that only send messages, but do so cost-effectively and efficiently, providing highly detailed information for each individual message.
Action Algorithm
- The first step to creating a connection via Unisender GO is to connect to the server.
- Next, you need to go to the server application following the path:
/home/smartplayer/smartplayer/backend/app/config. - After that, the user needs to create a configuration file named "local.js" in .json format, where the connection parameters for Unisender GO are specified. Two types of parameters are used: host (server address) and key (access key).
- Run the CLI command: ./cli.js test send-mail.
- Send a test email.
Additional Information
If this article does not help you use the functionality as intended or if you still have questions after reading it, you can raise them in the "Discussions" section at the top of the page.
Additional information can also be found on the page How users interact with the "Discussions" section.
