License expiry: what is closed and what keeps working
What happens to the panel, the API, traffic and outgoing events when the license stops being valid, and what changes after renewal.
When the license is inactive, the panel and the API are closed, but traffic keeps flowing: clicks and incoming conversions are recorded. Outgoing S2S postbacks and Facebook CAPI events are not sent: they wait in a queue and go out on their own after renewal.
When access is closed
The panel and the API are open in two license states: “License active” («Лицензия активна») and “Licensing not enabled yet” («Лицензирование ещё не подключено»). In all other states access is closed. The state is shown in the Micator license («Лицензия Micator») block on the closed access screen.
| State | What happened | What to do |
|---|---|---|
| “License term has ended” («Срок лицензии закончился») | The Paid / trial until («Оплачено / пробный период до») time has passed. When the license service responds with a refusal, the state changes to “License unavailable” | Renewal and orders |
| “License unavailable” («Лицензия недоступна») | The license service responded with a refusal: the term has expired, the license was revoked or suspended, the server was unbound in your account, or the license is bound to another installation. The red line in the block reads “License expired, revoked or bound to another installation” («Лицензия истекла, отозвана или привязана к другой установке») | Service refusal |
| “License confirmation required” («Нужно подтвердить лицензию») | The Works offline until («Работа без связи с сервисом до») time has passed, and the tracker did not get a new confirmation | The “License confirmation required” state |
| “Activation required” («Требуется активация») | The key has not been activated on this server yet | Getting a key and activation |
The “License check failed” («Проверка лицензии не пройдена»), “Check the server time” («Проверьте время на сервере») and “License service not configured” («Сервис лицензий не настроен») states also close access. They are covered in the state reference.
What is closed
The panel
Instead of any panel page except the login page, the “Tracker access closed” («Доступ к трекеру закрыт») screen opens with the text: “Renew the license to return to the panel. Traffic and incoming conversions keep being recorded. Outgoing events will be sent automatically after renewal.” («Продлите лицензию, чтобы вернуться в панель. Трафик и входящие конверсии продолжают записываться. Исходящие события отправятся автоматически после продления.»)
- All users see the screen, whatever their role.
- Reports, logs, settings and the other sections are unavailable until renewal.
- A panel page that is already open changes to this screen on its own.
- You can log in with your login and password, but the same screen opens.
The screen keeps the Micator license block and the Log out («Выйти») button. The block shows the license state and the Paid / trial until and Works offline until fields. The installation owner also sees the License key («Ключ лицензии») field and the Activate («Активировать») and Check renewal («Проверить продление») buttons.
The API
Protected API methods respond with code 402 — both to panel requests and to requests with an API token:
{"code": "license_required", "message": "Доступ к трекеру закрыт до продления лицензии. Трафик и приём конверсий работают, исходящие события ожидают продления."}The message means “access to the tracker is closed until the license is renewed; traffic and conversion intake keep working, outgoing events wait for the renewal”. This applies to campaigns, reports and exports, logs, settings, backups, spend and password changes in the profile. Only reading the license state and key activation by the installation owner are available — details are in the Expired license section of the API overview.
Background tasks
Until renewal, the following do not run:
- the blocklist registry check and automatic domain replacement;
- the reverse proxy node check and automatic domain transfer;
- campaign target monitoring;
- automation rules checks: campaigns are not paused, and no entries appear in the rules log;
- the daily audit log auto-cleanup;
- processing of spend uploaded by the extension.
Collection in the spend extension ends with the message “The tracker license is inactive; we will retry after renewal” («Лицензия трекера неактивна; повторим после продления») — see extension errors.
While the license is inactive, a domain from the blocklist registry is not replaced automatically, and the domains of an unavailable reverse proxy node are not moved to a working one.
What keeps working
- Redirects: campaign links open, and streams, filters and cloaking work with the saved settings.
- Click recording.
- Receiving incoming postbacks from affiliate networks. Conversions are recorded in the statistics.
- Receiving leads from forms.
- Issuing HTTPS certificates for domains already added to the tracker.
After renewal, reports show clicks and conversions for the whole time the panel was closed.
Outgoing event queue
Source and campaign S2S postbacks and Facebook Conversions API events stay in the queue. This applies both to events that were waiting to be sent when access closed and to events from conversions received later.
- Waiting does not use up delivery attempts.
- An event is stored with the address and parameters the tracker filled in when it received the conversion.
- An event the tracker had taken for processing but did not manage to send before access closed returns to the queue.
The installation owner sees the number of events in the queue — on the closed access screen and on the Settings → License («Настройки → Лицензия») tab: “Awaiting renewal: N events. After renewal they will be sent automatically, keeping the order of statuses and limiting the rate.” («Ожидают продления: N событий. После продления они отправятся автоматически с сохранением порядка статусов и ограничением скорости.»)
What happens after renewal
How to renew the license is described on Renewal and orders. The tracker itself rechecks the saved key every 1–2 minutes and picks up the renewal without any action from you. To avoid waiting, the installation owner clicks Check renewal in the Micator license block.
When the license is active again, the closed access screen disappears and the panel opens — without logging in again. The API responds again. On the Settings → License tab, a successful check shows the message “License confirmed. Queue delivery resumed.” («Лицензия подтверждена. Отправка очереди возобновлена.») If an error is shown instead, see If something went wrong.
The accumulated events are sent automatically:
- waiting does not create duplicates: each event is in the queue only once;
- events of one click to one recipient go out in the order they appeared, for example the lead first, then the sale;
- the rate is up to 10 accumulated events per second.
Until the queue is cleared, the remaining deliveries are shown in Logs → Event delivery («Логи → Доставка событий») in the “Pending” («Ожидает») state, with license_hold or “—” in the Result («Результат») column. Details are in Deliveries while the license is inactive. Their number is shown by the same “Awaiting renewal” line on the Settings → License tab.
The stopped background tasks resume on their own.
What is not sent automatically
Receipt not confirmed
An S2S request for which the tracker got no response is not retried automatically: the recipient may have accepted it, and a retry would create a duplicate. Such a delivery gets the “Needs review” («Нужна проверка») state and the “Receipt not confirmed” («Получение не подтверждено») result. License renewal does not restart it.
Find the delivery in Logs → Event delivery and check with the recipient before retrying — the procedure is described in the “Receipt not confirmed” section.
Old Facebook CAPI events
An event from the queue goes to Facebook with the conversion time, not the sending time. Whether Facebook accepts an event with an old time does not depend on the tracker.
If you are not the installation owner
Only the installation owner — the account created in the first-run wizard, when logged in with a login and password — enters the key and checks the renewal. Other users, including those with the “Owner” («Владелец») and “Admin” («Администратор») roles, see the license state, both terms and the text “Contact the installation owner to renew.” («Для продления обратитесь к владельцу установки.»)
Tell the installation owner that access is closed. You can leave the tab open: after renewal the panel opens on its own, and you do not need to refresh the page.
When you are logged in as a user, the key field is not shown. You cannot activate a license with an API token either: the request gets a response with code 403.