The Logs section: overview and access
What the Logs section contains, how to open it, what each of the eight tabs shows, and how long the records are kept.
The Logs («Логи») section brings together click search, the postback and traffic logs, the user action log and the queue status. You use it to find a click or a lead, check whether a conversion went through, and find out who changed a setting. Owners and admins can see this section.
How to open the section
- Click the Admin panel («Админ-панель») icon button in the top right corner of the panel.
- Choose Logs.
The Clicks and leads («Клики и лиды») tab opens. The section address is https://panel.example.com/logs.
Other ways into the section:
- The quick-links bar at the top of any admin panel section — the Logs item.
- The Click, conversions and deliveries → («Клик, конверсии и доставки →») button in the click window in campaign statistics. It opens the card of this click.
- A direct link to a click card:
https://panel.example.com/logs?click=SUBID, whereSUBIDis the click's full subid. The link opens for the owner and admin.
Section tabs
| Tab | What it shows | Details |
|---|---|---|
| Clicks and leads | Click search by IP, subid or external_id over a period. Clicking a subid opens the click card with conversions and deliveries | Click and lead search, Click card |
| System log («Системный лог») | Tracker warnings and errors, blocklist registry and reverse proxy node events. Besides the text, an entry has a Level («Уровень») and a Context («Контекст») | System log |
| Postbacks | Incoming postbacks from affiliate networks and form data: postback accepted, click not found, repeated transaction, rejected by secret | Postbacks |
| S2S postbacks | The result of each attempt to send an S2S postback: campaign ID, recipient, subid, attempt number, and the response code or the failure reason. Messages about Facebook Conversions API events that were not sent because the pixel or the token was not found also go here. The status of S2S and CAPI sends and resending are on the Event delivery («Доставка событий») tab | S2S postbacks |
| Traffic («Трафик») | How each click on a campaign link was processed: the requested address, the chosen stream, the cloaking decision. Recording is turned on with the Log («Логировать») toggle; it is off by default | Traffic, Diagnostics: why a click went to the “white” |
| Audit log | Actions of users and API tokens that create, change, delete or run something. For each one — who, when, from which IP and with what result | Audit log: user action log |
| Event delivery | Conversion records, outgoing S2S postbacks and Facebook Conversions API events: status, number of attempts, result, and resending with the Retry («Повторить») button | Event delivery log and resending |
| Queue status («Состояние очередей») | A summary of the click intake and event delivery queues, refreshed every 10 seconds | The Queue status tab |
The System log, Postbacks, S2S postbacks and Traffic tabs work the same way: a Search («Поиск») field, a live button with auto-refresh every 3 seconds, and the Refresh («Обновить») and Clear («Очистить») buttons.
Who has access
| Role | Access |
|---|---|
| Owner («Владелец»), Admin («Администратор») | All eight tabs and all actions in them |
| Team lead («Тимлид Баеров»), Buyer («Баер»), Designer («Верстальщик») | There is no Admin panel button. At the direct address /logs the data does not load, and the tabs show “administrator rights required” («требуются права администратора») |
| Financier («Финансист») | Any panel address except reports redirects to the Reports («Отчёты») section |
For roles, see Team and roles.
Actions of users without access to the section also get into the Audit log. Only the owner and admin can read the log.
API access
The section's methods are available with an API token that has Full access («Полный доступ»). A token with Summary reports («Сводные отчёты») or Extension spend («Расходы расширения») access gets a 403 response with the code token_scope. The methods are described on Admin API: logs and diagnostics and Admin API: conversions and postback.
What is shared by the installation and what belongs to the workspace
| Data | Whose records you see |
|---|---|
| Clicks and leads, the click card, Event delivery, Audit log | Only your own workspace's |
| System log, Postbacks, S2S postbacks, Traffic | The whole installation's |
| Queue status | The Click intake («Приём кликов») table — the whole server; the Event delivery table — your own workspace |
The Clear button and the Log toggle apply to the whole installation. Cleared records cannot be restored.
Time in the logs
The time on all tabs is shown in your browser's time zone. The Time zone for new reports («Таймзона новых отчётов») field in the My profile («Мой профиль») window does not affect the section.
- Clicks and leads and Event delivery — the format
DD.MM.YYYY, HH:MM:SS, for example04.10.2026, 14:32:07. The time zone name is shown above the table: “Time: Europe/Warsaw” («Время: Europe/Warsaw»). - System log, Postbacks, S2S postbacks, Traffic and Audit log — the format
YYYY-MM-DD HH:MM:SS, for example2026-10-04 14:32:07. - Queue status — only the check time: “Checked: 14:32:07” («Проверено: 14:32:07»).
In the period fields on the Clicks and leads, Event delivery and Audit log tabs, the date and time are entered in the same time zone.
Two admins in different time zones will see different times for the same record.
Retention
| Data | How long it is kept |
|---|---|
| System log, Postbacks, S2S postbacks, Traffic | The last 2,000 records in each log. There is no time limit: old records are pushed out by new ones or deleted with the Clear button |
| Clicks, conversions and landing page click-throughs — the Clicks and leads tab | 18 months |
| Audit log | No limit until cleanup is configured. The cleanup period is from 7 to 3650 days, 90 by default |
| Event delivery | No retention limit is set. Audit log cleanup does not delete these records |
Audit log cleanup is configured in Settings → Retention («Настройки → Хранение») — see Data retention and audit log cleanup.
With heavy traffic, only the most recent clicks remain in the Traffic log. A click from the whole retention period can be found on the Clicks and leads tab.
When the license has expired
When the license is not active, the section is closed together with the whole panel: the “Tracker access closed” («Доступ к трекеру закрыт») screen opens instead. The section's API methods return 402 with the code license_required — see Expired license.
Clicks and incoming conversions keep being recorded, and outgoing events wait for the renewal. After the renewal, the section opens again, and the clicks from this period can be found by search. For details, see License expiry: what is closed and what keeps working.
FAQ
A media buyer does not see the Logs section
The section is open only to the owner and admin. There is no setting that opens it to other roles. A media buyer views clicks and conversions of their own campaigns on the Click log («Лог кликов») and Conversion log («Лог конверсий») tabs in the campaign statistics.
Where can I see whether a postback was sent to the source
On the Event delivery tab. Find the send by subid and check the State («Состояние») and Result («Результат») columns — see Event delivery log and resending.
The Traffic tab is empty
The traffic log is off by default. Turn on the Log toggle on this tab — see Turning on the traffic log.
Can I export a log to a file
There are no export buttons in the section. You can get the section's data through the Admin API.