Event delivery log and resending
How to find a delivery by click, understand its state and result, and retry it without creating a duplicate at the recipient.
The delivery log shows every conversion recording and every outgoing delivery: an S2S postback to the source and to campaign recipients, and a Facebook Conversions API event. The log shows whether an event was sent, how many attempts there were and how they ended. Owners and admins can see the section.
Where the log is
- Logs → Event delivery («Логи → Доставка событий») — all deliveries of the workspace for a period. How to open the section is covered on the Logs section page.
- The Event delivery block in the click card — all stored deliveries of one click, without filters and without a period limit.
The recipient address and the request contents are not shown in the log. Above the table on the tab is a line like “Time: Europe/Warsaw. Recipient secrets are hidden.” («Время: Europe/Warsaw. Секреты получателей скрыты.») Times in the table are shown in the browser time zone.
Finding a delivery
- Open Logs → Event delivery. The list for the last 7 days opens.
- Fill in the filters.
- Click Find («Найти»).
| Filter | Values |
|---|---|
| Subid | The full click subid, exact match. Up to 64 characters: Latin letters, digits, _, - and dots (not at the start or end, and not two in a row) |
| From («С») and To («По») | The period by task creation time, no longer than 93 days. Both fields are required |
| State | All states («Все состояния»), Pending («Ожидает»), Processing («Обрабатывается»), Done («Выполнено»), Needs review («Нужна проверка») |
| Type | All types («Все типы»), Conversion («Конверсия»), S2S, CAPI |
| Recipient | All recipients («Все получатели»), Source («Источник»), Campaign («Кампания»), Source + campaign («Источник + кампания»). With a recipient selected, only S2S rows with the same recipient remain in the list |
A page holds 100 rows, newest first. Use the ← Back («← Назад») and Next → («Далее →») buttons to page through. The Refresh («Обновить») button reloads the list with the same filters. If nothing is found, the table shows the line “No deliveries for the selected period” («Доставок за выбранный период нет»). If you do not know the subid, find the click by IP or external_id — see Click and lead search.
Table columns
| Column | What it shows |
|---|---|
| Created («Создано») | The task creation time. On hover — the time of the last change |
| Type / recipient («Тип / получатель») | The task type and the recipient, see below |
| Click («Клик») | The subid. Clicking it opens the click card. The click card does not have this column |
| State («Состояние») | The current state of the task |
| Attempts («Попытки») | How many times the tracker has run the task. After a manual retry, the count starts over |
| Result («Результат») | The outcome of the last attempt |
Task types:
- Conversion record («Запись конверсии») — the tracker saves the accepted conversion to the statistics. Until this task is done, there are no S2S or CAPI rows for this conversion: they are created after the recording.
- S2S · source («S2S · источник») — a postback to the traffic source.
- S2S · campaign («S2S · кампания») — a postback to an additional campaign address.
- S2S · source + campaign («S2S · источник + кампания») — the final source address and the campaign address matched, so the request is sent once.
- CAPI — an event to Facebook.
States
| State | What it means |
|---|---|
| Pending | The task is queued: it is waiting for the first delivery, the next automatic attempt or a license renewal |
| Processing | The tracker is running the task right now |
| Done | The conversion is recorded or the recipient responded successfully |
| Needs review | There will be no more automatic attempts. Look at the Result column and decide whether to retry the delivery |
Values of the “Result” column
| Result | What it means | What to do |
|---|---|---|
| “—” | There have been no attempts yet, or the task was returned to the queue with the Retry («Повторить») button | Nothing |
ok | The task is done. For S2S, the recipient responded with a 2xx code | Nothing |
http_404, http_500 and other http_… | The S2S recipient responded with this HTTP code. On 5xx and 429 the tracker retries on its own; on other codes it sets Needs review right away | Check the postback address and its parameters in the source or campaign. The corrected address applies to new conversions; Retry sends the previous one |
| No connection · retrying («Нет соединения · повторяется») | The tracker could not connect to the recipient, and the request was not sent. The tracker will try again | Wait |
| No connection · attempts exhausted («Нет соединения · попытки исчерпаны») | The connection failed and automatic attempts have run out | Make sure the recipient is available and retry |
| Receipt not confirmed («Получение не подтверждено») | The request was sent, but no response was received. The event may have arrived | Check with the recipient, and only then retry |
| Invalid URL («Некорректный URL») | The postback address could not be parsed or does not start with http:// or https:// | Fix the address in the source or campaign. This task cannot be retried |
| Address blocked («Адрес заблокирован») | The address points to a non-public IP: a local one or one from an internal network. The tracker does not send to such addresses | Use a public address. This task cannot be retried |
| Restored from backup · needs reconciliation («Восстановлено из копии · нужна сверка») | The task was not finished at the time of the backup, and the tracker was restored from that backup | Check with the recipient, then retry |
capi_error | Facebook did not accept the event or did not respond. In the Pending state, the tracker retries the delivery on its own | In the Needs review state — see If the event was not sent |
license_hold | The delivery is on hold while the license is not active | Nothing: it will be sent automatically after renewal |
storage_error, ack_error | The tracker could not record the conversion to the statistics or save the task result. It retries on its own | If the error persists, open System status |
invalid_payload, invalid_kind | The task is corrupted | This task cannot be retried |
Automatic retries
S2S succeeds when the recipient responds with a 2xx code.
The tracker retries a delivery on its own in three cases:
- the connection to the recipient was not established;
- the S2S recipient responded with a 5xx or 429 code;
- Facebook responded with a 5xx or 429 code, or the request to it was interrupted.
The pause before the next attempt doubles: from 10 seconds to 85 minutes. After 12 attempts, S2S and CAPI move to the Needs review state. Conversion recording is retried with no limit on the number of attempts.
The tracker does not retry other responses, for example 404.
“Receipt not confirmed”
This result appears for S2S when the request was sent but no response was received: the recipient did not respond in time or the delivery was interrupted. The tracker does not know whether the event was counted and does not retry it on its own: not every recipient filters out repeat postbacks.
- Check with the recipient whether there is a conversion for this click.
- If there is, do nothing.
- If there is not, click Retry.
Manual retry
The Retry button is available only for rows in the Needs review state.
- Click Retry in the task row.
- Read the prompt: “Retry the delivery? If the recipient has already accepted the event, it may get a duplicate. Check the data with the recipient first.” («Повторить отправку? Если получатель уже принял событие, у него может появиться дубль. Сначала сверьте данные у получателя.»)
- Confirm.
The task returns to the Pending state, and the result changes to “—”. The request is sent to the recipient unchanged: changes to the postback address made after the conversion do not affect a task that has already been created.
The counter in the Attempts column is reset. S2S and CAPI get a new series: up to 12 automatic attempts, with pauses starting from 10 seconds again.
The button is not available for the Invalid URL, Address blocked, invalid_payload and invalid_kind results.
Retrying after the Receipt not confirmed or Restored from backup · needs reconciliation result without checking may create a second conversion at the recipient.
Deliveries while the license is inactive
While the license is not active, S2S and CAPI are not sent. Conversion recording continues. Tasks wait in the Pending state, and no attempts are used up. After renewal, the accumulated deliveries are sent automatically. While the queue is being processed, tasks not yet sent show license_hold or “—” in the Result column. More in License expiry.
The “Queue status” tab
Logs → Queue status («Логи → Состояние очередей») shows a summary of the queues. It refreshes every 10 seconds.
The Event delivery table counts the unfinished tasks of the workspace. Its rows are the task types: conversion, s2s and capi.
| Column | What it counts |
|---|---|
| Pending («Ожидают») | Tasks in the Pending state |
| In progress («В работе») | Tasks in the Processing state |
| Errors («Ошибки») | Tasks in the Needs review state |
| Processing timed out («Истёк срок обработки») | Tasks whose processing did not finish in time |
| Unknown result («Неизвестный результат») | Tasks with the Receipt not confirmed result |
| Queue age («Возраст очереди») | How long the oldest task in the Pending or Processing state has been waiting |
If there are no unfinished tasks, the table shows the line “No unfinished tasks” («Незавершённых задач нет»).
The Click intake («Приём кликов») table covers the whole server and shows the Clicks («Клики») and Landing page clicks («Переходы с лендинга») queues. Its columns and states are covered on the System status page.
Frequently asked questions
The conversion is in the tracker, but there is no S2S row
A task is created only if a source or campaign postback was configured at the time of the conversion and the conversion status is one of the statuses that are sent. Postbacks added later are not sent for old conversions. Other causes are in the Postback to the source was not sent section.
Choose a period of up to 93 days («Выберите период до 93 дней»)
The period between From and To is longer than 93 days, or the start is later than the end. Shorten the period. The deliveries of one click are shown without a period limit in its card.
Invalid subid («Некорректный subid»)
The Subid field has more than 64 characters, contains characters other than Latin letters, digits, _, - and dots, or has a dot at the start, at the end or two in a row. Enter the full click subid.
A task stays in the “Pending” state for a long time
Look at the Result column:
- No connection · retrying,
http_500and other 5xx codes,http_429,capi_error— the tracker is waiting out the pause before the next attempt. license_hold— the delivery was on hold until the license renewal and will be sent in queue order.- “—” — the delivery has not started yet. S2S and CAPI of one click are sent in turn: the task waits until an earlier delivery of this click with the same type and recipient finishes.