Notifications in the panel
Where to see notifications, how to mark them as read, and how to choose what the panel tells you about.
The panel tells a user about events that concern them: an automation rule fired, an offer reached its cap, access changed, the license is about to expire, a backup was not created. Notifications are shown only inside the panel, under the bell icon in the header. They are not sent to Telegram yet.
The bell and the list
The Notifications («Уведомления») button with a bell icon is on the right side of the page header. For the owner and admin it sits to the left of the Admin panel («Админ-панель») button. On a phone it is in the header, before the button with the role abbreviation.
- The number on the icon is how many notifications are unread. At 100 and above, “99+” is shown instead of the number.
- Clicking it opens the list: on a computer, under the button; on a phone, at the bottom of the screen.
- At the top of the list there is the line “Unread: 3” («Непрочитанных: 3») or “No unread” («Непрочитанных нет») and the Mark all as read («Прочитать все») button.
- Notifications are grouped by day: “Today” («Сегодня»), “Yesterday” («Вчера»), then a date, for example “October 12” («12 октября»).
- Each notification has a title, a text and a time by the browser clock: “just now” («только что»), “5 min ago” («5 мин назад»), “2 h ago” («2 ч назад»), “yesterday at 14:05” («вчера в 14:05»), “October 12 at 14:05” («12 октября в 14:05»).
- An unread notification is shown in bold and marked with a dot on the right. The icon on the left shows importance: a regular message, a warning or an important one.
- The list loads 20 notifications at a time. The Show more («Показать ещё») button loads the next ones.
The number on the icon updates once a minute while the tab is open and visible, and also when you go to another page of the panel and when you return to the tab. If new notifications arrive while the list is open, the line “There are new notifications.” («Есть новые уведомления.») appears at the top with a Show («Показать») button.
Clicking a notification opens the related page and closes the list: for example, a campaign, the Automation rules section («Автоматические правила») or the Settings → Backups («Настройки → Резервные копии») tab. For notifications without a link, such as “Your access has changed” («Ваш доступ изменён»), clicking only marks them as read.
Read and unread
- A notification becomes read when you click it.
- The Mark all as read button marks unread notifications as read. While all of them are on the screen, only those are marked: a notification that has just arrived and is not yet shown in the list stays unread. If there are no unread notifications on the screen and the list is shown in full, the button marks nothing — it shows the new ones. If some unread notifications remain on the next pages of the list, all of them are marked.
- Read notifications stay in the list without highlighting until the storage limits apply.
- You cannot make a notification unread again.
The read mark is stored on the server: a notification read on one device is read on the others too.
Settings
- Click My profile («Мой профиль») at the bottom of the left menu. The Notification settings («Настройки уведомлений») link at the bottom of the notification list opens the same block.
- In the Notifications block, turn Receive notifications («Получать уведомления») on or off.
- Click a group to expand it: Campaigns and traffic («Кампании и трафик»), Access and security («Доступ и безопасность») or Installation («Установка»).
- Toggle the notification kinds you need.
Changes are saved right away; there is no separate save button.
| Setting | What it does |
|---|---|
| Receive notifications | The master switch. While it is off, new notifications are not created. Notifications already received stay in the list |
| Kind switch | Turns one notification kind on and off. Next to the group name you see how many kinds are on: “5 of 6 on” («включено 5 из 6») |
- With the master switch off, the bell is crossed out and the list shows the line “Notifications are off: new ones do not arrive.” («Уведомления выключены: новые не приходят.») with a Configure («Настроить») button.
- While the master switch is off, the kind switches are inactive. The choice of kinds you made earlier is kept and applies again after you turn it back on.
- Settings show only the kinds available to your role.
- By default all kinds are on except Backup created («Резервная копия создана»).
- The panel does not report later on an event that was skipped because of a switch. The exception is what is still relevant: backups and updates from the last 24 hours, the license term, an unavailable backup encryption key and problems with background services. Such a notification may appear within 6 hours after you turn the switch on.
Notification kinds
Campaigns and traffic
| Kind | Description in settings | Available to |
|---|---|---|
| Automation rule triggered («Автоправило сработало») | “The rule paused campaigns or recorded a trigger in the log.” | Owner, admin, team lead, media buyer |
| Automation rule not running («Автоправило не выполняется») | “The rule was turned off after an error or cannot run.” | Owner, admin, team lead, media buyer |
| Offer cap reached («Лимит оффера исчерпан») | “The offer reached its click cap for the period or its daily sales cap.” | Owner, admin, team lead, media buyer |
| Offer or landing page not responding («Оффер или лендинг не отвечает») | “The campaign page check stopped passing or passes again.” | Owner, admin, team lead, media buyer |
| Domain in the blocklist registry («Домен в реестре блокировок») | “Your domain got into the registry or a domain in a stream was replaced with a reserve one.” | Owner, admin, team lead, media buyer |
| Report export («Выгрузка отчёта») | “A background export is ready or failed.” | All roles |
Access and security
| Kind | Description in settings | Available to |
|---|---|---|
| Your access changed («Изменён ваш доступ») | “An admin changed your role, team lead or available sections.” | All roles |
| Access granted to you («Вам открыли доступ») | “A campaign, offer or landing page was shared with you.” | All roles except financier |
| Password changed by an admin («Пароль изменён администратором») | “An admin set a new password for you.” | All roles |
Installation
| Kind | Description in settings | Available to |
|---|---|---|
| License («Лицензия») | “The term is ending, the license has expired or it cannot be verified.” | Owner, admin |
| Backup not created («Резервная копия не создана») | “A backup was not created, a scheduled one was skipped or old backups were not deleted.” | Installation owner |
| Backup created | “Every successful backup, scheduled or manual.” | Installation owner. Off by default |
| Tracker updates («Обновления трекера») | “A new version is out, an update was installed or canceled.” | Installation owner |
| Reverse proxy nodes («Реверс-прокси ноды») | “A node is unavailable, domains were moved to a reserve node, a node was connected.” | Owner, admin |
| Postbacks not delivered («Постбеки не доставляются») | “Sends of postbacks or events end with an error.” | Owner, admin |
| Background services («Фоновые службы») | “The IP2Proxy database or currency rates are not updating, or spend is not being applied.” | Owner, admin |
One kind covers several notifications: which ones exactly is shown in the “Kind” column of the tables in When a notification appears. For example, the Backup not created switch also controls the notifications about the outcome of a restore and about an unavailable encryption key.
Designers get Report export and the three kinds of the Access and security group. Financiers get Report export, Your access changed and Password changed by an admin. For who counts as the installation owner, see Installation owner. If there is no account with that login, nobody receives notifications about backups and updates.
Who receives a notification
The role determines which kinds a user can receive. A specific event goes to the people who can see what it is about.
| Event | Who receives it |
|---|---|
| An automation rule triggered, was turned off or is not running | The author of the rule. The team lead the author is assigned to — if the team lead has the Automation rules section open and all the rule's campaigns are available to them. The owner and admin get notifications only about their own rules |
| An offer reached its cap | Owners, admins and team leads. A media buyer — for their own offer and for an offer shared with them |
| A campaign's offer or landing page is not responding; a domain in a stream was replaced | Owners and admins. The team lead or media buyer who owns the campaign. The team lead its owner is assigned to. Team leads and media buyers the campaign is shared with |
| A domain got into the blocklist registry | Owners, admins and team leads. A media buyer — for domains from the groups opened to them |
| Report export, access change, new password | The person it concerns |
| Access to a campaign was granted | The team lead, media buyer or designer added to the access list |
| Access to an offer or landing page was granted | The media buyer who was granted access |
| A copy of an offer was created | The user the copy was created for |
| License, nodes, postbacks, currency rates, spend | Owners and admins |
| Backups, updates, IP2Proxy database | Installation owner |
A user with a restriction by campaign groups receives notifications about a campaign only if its group is allowed to them.
The author receives the “Automation rule … turned off” («Автоправило … выключено») notification as long as the kind is available to them: for example, when the Automation rules or Campaigns («Кампании») section is switched to View («Просмотр»), or a campaign of the rule no longer belongs to them. If the author was given No access («Нет доступа») for the section, had a report field forbidden, or had their role changed to designer or financier, only their team lead receives the notification.
When a notification appears
Automation rules, exports, access, password, the blocklist registry and nodes report an event right away. The tracker checks the license, offer caps and page checks once a minute, and backups, updates, send queues and background services every 5 minutes.
Campaigns and traffic
| Notification title | Kind | When it appears |
|---|---|---|
| “Automation rule … triggered” («Автоправило … сработало») | Automation rule triggered | After every trigger that paused campaigns. For a rule that only writes to the log — no more than once an hour |
| “Automation rule … turned off” | Automation rule not running | The tracker turned the rule off: the author's access to the rule's campaigns or to the section changed, or the rule's settings no longer fit |
| “Automation rule … not running” («Автоправило … не выполняется») | Automation rule not running | The rule check failed; the rule stays on. No more than once a day |
| “Offer … reached its click cap” («Оффер … набрал лимит кликов») | Offer cap reached | The click cap for the period is reached. Once per period; for a “per hour” cap — once a day. A cap that was raised and reached again in the same period gives a new message |
| “Offer … reached its daily sales cap” («Оффер … набрал дневной лимит продаж») | Offer cap reached | The daily sales cap is reached. Once a day; after the cap is raised — once more when the new one is reached |
| “Offer … is not responding” («Не отвечает оффер …»), “Landing page … is not responding” («Не отвечает лендинг …») | Offer or landing page not responding | The campaign's HTTP monitoring showed an error for the page in two checks in a row |
| “Offer … is responding again” («Снова отвечает оффер …»), “Landing page … is responding again” («Снова отвечает лендинг …») | Offer or landing page not responding | The page that was reported has been responding in every check for half an hour |
| “Domain … got into the blocklist registry” («Домен … попал в реестр блокировок») | Domain in the blocklist registry | A blocklist registry check found the domain. Several domains from one check arrive as one notification: “Domains in the blocklist registry: 5” («Домены в реестре блокировок: 5») |
| “Blocked domain replaced in a stream” («В потоке заменён заблокированный домен»), “Blocked domain replaced in streams” («В потоках заменён заблокированный домен») | Domain in the blocklist registry | The tracker replaced a blocked domain with a reserve one in one or more streams |
| “Report export is ready” («Выгрузка отчёта готова»), “Report export failed” («Выгрузка отчёта не удалась») | Report export | A background CSV export finished |
Access and security
| Notification title | Kind | When it appears |
|---|---|---|
| “Your access has changed” | Your access changed | The owner or an admin changed your role, team lead or permissions |
| “You were granted access to campaign …” («Вам открыли доступ к кампании …»), “You were granted access to offer …” («Вам открыли доступ к офферу …»), “You were granted access to landing page …” («Вам открыли доступ к лендингу …») | Access granted to you | You were added to the access list. The text gives the login of the person who granted access |
| “Offer … was copied for you” («Вам скопировали оффер …») | Access granted to you | A copy of an offer was created for you |
| “An admin set a new password for you” («Администратор задал вам новый пароль») | Password changed by an admin | The password was set in the Team («Команда») section — see Editing a user and resetting the password |
Installation
| Notification title | Kind | When it appears |
|---|---|---|
| “License expires in … days” («Лицензия заканчивается через … дн.»), “License expires tomorrow” («Лицензия заканчивается завтра»), “License expires today” («Лицензия заканчивается сегодня») | License | Three times: when 7 days, 3 days and 1 day are left until the end of the term. The first two notifications give the number of days, the third says “tomorrow” or “today” |
| “License has expired” («Лицензия закончилась») | License | Right after the term ends |
| “The license cannot be verified” («Лицензию не удаётся проверить»), “The license is not valid” («Лицензия не действует») | License | The license check has been failing for more than 15 minutes. One notification per problem: while it lasts, the notification is not repeated |
| “License is active again” («Лицензия снова активна») | License | Once, after a message that the license expired or cannot be verified |
| “Backup not created” | Backup not created | The backup ended with an error. The text gives the storage server and the reason |
| “Scheduled backup skipped” («Копия по расписанию пропущена») | Backup not created | A scheduled run was skipped |
| “Old backups not deleted” («Старые копии не удалены») | Backup not created | The backup was created, but the cleanup under the retention rule was not done |
| “Backup encryption key unavailable” («Ключ шифрования копий недоступен») | Backup not created | The key on the server is damaged; backups are not created. Once a day until the key is replaced |
| “Restore from backup completed” («Восстановление из копии выполнено»), “Restore canceled” («Восстановление отменено»), “Manual restore required” («Нужно ручное восстановление»), “Restore from backup failed” («Восстановление из копии не выполнено») | Backup not created | The outcome of an in-place restore |
| “Backup created” | Backup created | After every successful backup. The text gives the storage server and the time in UTC |
| “Update … available” («Доступно обновление …») | Tracker updates | An update check in the panel found a new version. Once for each version |
| “Update … installed” («Обновление … установлено»), “Update … not installed” («Обновление … не установлено») | Tracker updates | The outcome of installing an update |
| “Node … unavailable” («Нода … недоступна»), for a node without a name — “Reverse proxy node unavailable” («Реверс-прокси нода недоступна») | Reverse proxy nodes | The node is not responding. The text gives the outcome: the domains were moved to a reserve node, moved partially, there is no reserve, or the node had no domains. While the move is not finished or there is no reserve, the notification repeats no more than once an hour |
| “Node … connected” («Нода … подключена»), “Node … could not be connected” («Ноду … не удалось подключить»); for a node without a name — “Reverse proxy node connected” («Реверс-прокси нода подключена»), “Reverse proxy node could not be connected” («Реверс-прокси ноду не удалось подключить») | Reverse proxy nodes | The outcome of connecting a node |
| “Postbacks not delivered” («Постбеки не доставляются»), “Facebook events not delivered” («События Facebook не доставляются»), “Conversions not recorded” («Конверсии не записываются») | Postbacks not delivered | The number of failed sends grew. No more than once every 6 hours for each queue. The notification opens Logs («Логи») on the Event delivery («Доставка событий») tab — see Event delivery log |
| “IP2Proxy database not updating” («Не обновляется база IP2Proxy») | Background services | The IP2Proxy database has not updated for 48 hours. Once a day |
| “Currency rates not updating” («Не обновляются курсы валют») | Background services | Currency rates have not updated for 24 hours. Once a day |
| “Spend not applied” («Расходы не применяются») | Background services | Spend from the extension was received but has not been applied for 30 minutes. Once a day |
The intervals “once an hour”, “once every 6 hours” and “once a day” are counted by UTC calendar hours and days, not from the previous notification: at the boundary of an interval, two notifications can arrive one after the other. The daily sales cap is counted by days in the offer's time zone.
The panel does not report retroactively on events that happened before notifications appeared on the installation. For backups and updates, events from the last 24 hours are taken into account.
Closed sections
If the owner or an admin chose No access for a section for a user in the Permissions window («Права»), notifications of that section do not reach the user and are not shown in their settings.
| What is closed | Which kinds are unavailable |
|---|---|
| The Automation rules, Campaigns or Reports («Отчёты») section, or at least one report field is forbidden | Automation rule triggered, Automation rule not running |
| The Offers («Офферы») section | Offer cap reached |
| The Campaigns section | Offer or landing page not responding |
| The Domains («Домены») section | Domain in the blocklist registry |
| The Reports section | Report export |
The “Access granted to you” notification does not arrive if the section with that campaign, offer or landing page is closed to the recipient. The restrictions do not apply to the owner and admin.
Limits
- Each user keeps no more than the last 300 notifications, for no longer than 90 days. Extra and old ones are deleted automatically, once an hour.
- The icon shows up to 99 unread notifications, beyond that — “99+”.
- One event — one notification: a repeat of the same event does not create a second one.
- Notifications are personal. They are not available via an API token: the request is refused with code
403. For a full-access token the refusal text is “Notifications are available only in the panel” («Уведомления доступны только в панели»). - In Log in as mode, notifications and their settings can only be viewed. The list shows the line “You are logged in as another user: their notifications can only be viewed.” («Вы вошли как другой пользователь: его уведомления можно только смотреть.»), and the profile shows “In Log in as mode, notification settings can only be viewed.” («В режиме «Войти как» настройки уведомлений можно только посмотреть.») Notifications that only the installation owner receives — about backups, updates and the IP2Proxy database — are absent in this mode from both the list and the counter.
- When the license is inactive, notifications are closed together with the panel. License messages are still created then and become visible after renewal.
- The text of notifications contains no amounts, metric values, IP addresses or lead data.
- The time in a notification's text is in the time zone from your profile, without it — in UTC. The time a backup was created is always in UTC.
- Telegram is not connected: notifications exist only in the panel.
What you do not get notifications about
- Every click, lead and conversion. Notifications report state and outcomes, not the flow of events.
- Revoked access: only new access is reported.
- Changing your own password in the profile.
- Changes you made to your own account.
If something went wrong
The bell is crossed out
The Receive notifications master switch is off, so new notifications are not created. Open My profile and turn it on.
The kind you need is not in the settings
The kind is not provided for your role, or the section is closed in your permissions — see Notification kinds and Closed sections. Only the installation owner sees the kinds about backups and updates.
A notification did not arrive
- Check the master switch and the switch of the kind you need in My profile.
- Check the Who receives a notification table: the event may not concern your campaigns, offers or domains.
- A second notification is not created for an event that was already reported. Some events have a minimum interval — see When a notification appears.
- Notifications about backups, updates, send queues and background services appear with a delay of up to 5 minutes.
Failed to load notifications.
The panel shows “Failed to load notifications.” («Не удалось загрузить уведомления.»): it did not receive the list. Click Retry («Повторить»). If that does not help, reload the page.
Failed to save. Try again.
The panel shows “Failed to save. Try again.” («Не удалось сохранить. Попробуйте ещё раз.»): the setting was not saved and the switch returned to its previous position. Toggle it again.