Break down Sendsay campaigns by opens and clicks in chat
Connect Sendsay to the AI agent: subscribers, groups, segments, issues and triggers. The agent breaks down deliveries, opens and clicks and tidies up the base.
How the agent works with Sendsay
The agent calls Sendsay at a single JSON address, https://api.sendsay.ru/general/api/v100/json: the action name and the key travel in the request body, and there are no separate endpoints per section here. Through it the agent reads subscribers and their fields, groups and segments, issues and templates, trigger scenarios and statistics on deliveries, opens, clicks, unsubscribes and bounces, and out of that assembles the breakdown of an issue and the dynamics of the base over a period.
Campaign statistics are not final at the moment of sending: deliveries, opens and clicks keep being written in for hours and days after an issue, so the agent states the period the figures were taken for and does not pass a fresh issue off as a settled result. Unsubscribes and bounces it looks at separately from opens — they show not the design of the email but the state of the base, and they are what explains why deliverability drops from issue to issue.
On the write side the agent updates subscriber records and group membership, assembles an issue from a template and prepares an A/B test. The order here is always the same: first a test email for review, and only on your explicit confirmation a send to the live base; it never launches a campaign on its own. Before sending, the agent names the segment the issue goes to and the number of addresses in it, because an email that has gone out cannot be recalled.
Every call goes to a single JSON address, so the boundary is set not by a set of endpoints but by the action name in the request body: listing subscribers, exporting statistics and launching an issue differ only by that. Heavy selections come back as a deferred task — the agent queues it and picks the result up when it is ready instead of waiting for everything in one response. It holds the rate within ten requests per second, and when data or permissions fall short it says so directly instead of showing an empty table.
Integration scenarios
Breakdown of the latest campaign
The agent splits an issue by deliveries, opens, clicks and unsubscribes and shows which emails and links worked and which did not.
Order in the subscriber base
The agent reviews groups and segments, finds unsubscribed and long-inactive contacts and updates subscriber records from your data.
Preparing an issue and an A/B test
The agent assembles an issue from a template, sends a test email for review and shows the split test results once it has gone out.
Weekly campaign summary
On a schedule the agent sends a summary: deliverability, subscriber activity and growth of the base for the week against the previous one.
Check on trigger scenarios
The agent walks through the trigger scenarios, shows how many emails each one sent and how they were opened, and flags the ones that have long gone quiet.
Compare issues over a period
The agent pulls the statistics of every issue in the quarter into one table, compares opens, clicks and unsubscribes and shows which subjects and send days work best.
Sendsay examples
Доставлено 18 402 письма, открытий 31,7%, кликов 4,2%.
- Выпуск «Летняя коллекция» — отписок 0,3%, это норма для базы
- Из шести ссылок 71% кликов собрала одна — кнопка в первом экране
- Возвраты выросли до 1,8%: 214 адресов из группы «Импорт-2024»
How to connect
Before you connect
- A Sendsay account with owner access to system settings
- A free user slot on your plan
- A separate mailbox for the sublogin invite
- 1
In «Пользователи» add a sublogin
Account menu → «Настройки системы» → «Пользователи» → «Добавить пользователя»: name, login, email, password. The account owner cannot be issued an API key.
- 2
Give the «Менеджер» role, leave 2FA off
The «Менеджер» role covers subscribers, campaigns and automations. Never enable two-factor auth on this sublogin — requests with the key stop working.
- 3
In «Настройка пользователя» generate the key
User card → «Настройка пользователя» tab → «API-ключ» → «Сгенерировать ключ». The key is shown once: copy it immediately, a lost key can only be replaced.
- 4
Note the main login from the account menu
The account name is the main login shown in the account menu, not the sublogin's login. It is what goes into the API address.
FAQ
With the account name and an API key: create a separate sublogin under System settings, Users — the account owner is not issued a key — and in its card, on the User setup tab, click Generate key. The account name is the main login.
Subscribers and their fields, groups and segments, issues and templates, trigger scenarios and statistics on deliveries, opens, clicks, unsubscribes and bounces.
It can: update subscriber records and group membership, assemble issues, send test emails and launch a campaign. The agent sends only on your explicit confirmation, never on its own.
Most often two-factor authorization is enabled on the sublogin — requests by key do not run while it is on. The second case: the account field holds the sublogin instead of the main login.