System log, postbacks and traffic log
What is recorded on the “System log”, “Postbacks”, “S2S postbacks” and “Traffic” tabs, how to turn on the traffic log, and how to search and clear records.
In the Logs («Логи») section, opened via Admin panel → Logs («Админ-панель → Логи»), the System log («Системный лог»), Postbacks, S2S postbacks and Traffic («Трафик») tabs show a feed of the tracker's latest events. The section is visible to the owner and the admin. The other tabs are covered in The Logs section: overview and access.
General rules
- Each log keeps the 2000 latest records. A new record pushes out the oldest one. There is no time-based retention period.
- New records are at the top. The list shows up to 500 records.
- The logs are shared by the whole installation. The Clear («Очистить») button and the Log («Логировать») toggle also act on the whole installation.
- The record time is shown in the
YYYY-MM-DD HH:MM:SSformat in the browser's time zone. - Logs cannot be exported to a file.
The controls are the same on all four tabs:
| Control | What it does |
|---|---|
| The Search («Поиск») field | Keeps the records whose text contains the entered string. Case does not matter. The list changes as you type. The search covers all 2000 records and shows the 500 newest matches |
| live / pause («пауза») | Auto-refresh of the list every 3 seconds. It is on by default, and the button says live. Click it to stop the feed: the label changes to pause |
| Refresh («Обновить») | Re-reads the list once |
| Clear | Deletes all records of the log — see Clearing a log |
| Log | Only on the Traffic tab: turns traffic log recording on and off |
System log
This log gets warnings and errors of the tracker services, as well as events of domains and reverse proxy nodes. Columns: Date and time («Дата и время»), Level («Уровень»), Context («Контекст»), Text («Текст»). Search works only on the Text column.
- Level:
WARN— a warning,ERROR— an error, “—” — an event without a level. - Context:
admin— a record of the panel and API (settings, conversion intake, background tasks),click— a record of traffic processing (clicks and redirects).
Events without a level and context:
- a domain got into the blocklist registry, was replaced in a stream, the replacement was canceled or the domain reserve ran out — see Blocklist registry (PL) and automatic domain replacement;
- a reverse proxy node was set up or its setup failed, a node is unavailable, domains were moved to another node or pointed at a reverse proxy node — see Reverse proxy nodes;
- a hosted offer's lead log is full, and new leads are not written to the file — see Receiving leads from forms.
The ⚠ sign marks blocklist registry events in which the automatic domain substitution was not performed or has not been applied yet. The record text says what will happen next or what to do manually.
Postbacks
The log of incoming postbacks and form data. Columns: Date and time, Text.
For each postback whose click is found, three records are written: Received postback, Using … as subid, Processing subid. New records are at the top, so on screen they appear in reverse order. If the postback is then rejected or skipped, a record with the reason appears above them. Conversion import from CSV leaves the same records.
| Record | What it means |
|---|---|
Received postback /api/v1/postback | The postback is received and the click is found. Only the request path is shown, without parameters |
Using "<subid>" as subid. Postback added to queue. | The subid by which the click was found |
Processing subid <subid>, Campaign ID: <ID>, Status: <status> | The click's campaign and the status from the postback before mapping to conversion types: lead, sale, hold or rejected. Any other value, including an empty one, is shown as custom |
Click for subid <subid> not found | There is no click with this subid. The conversion is not recorded |
Rejected <subid>: неверный/отсутствует secret источника | The source secret was not passed or did not match. The conversion is not recorded |
Duplicate transaction for <subid> (status <status>) — skipped | An exact repeat of an already accepted transaction. No new conversion is created |
Late transaction status for <subid> — skipped | After a sale, a lead or hold came for the same transaction. The status is not changed |
Late status without txid for <subid> — skipped | A sale without txid is already recorded for the click, and then a lead, a hold or a postback without status came, also without txid. The sale is not changed |
Параметр cost пуст или не подставлен для <subid> — расход из постбека не взят | The cost parameter has an empty value or an unsubstituted network macro. The postback is not rejected because of this, but the cost is not taken from it |
Выплата в postback не распознана или недопустима — записан 0 | The payout parameter is not a number, or the amount is negative or too large |
Данные лида закреплены за <subid> (email/телефон/имя) | The contact data from the form is saved for the click |
Данные лида за <subid> уже сохранены — без секрета источника не перезаписываются | The form was submitted again; the saved data is not changed |
Лид оффера <offer ID> записан в leads.php | The lead is added to the hosted offer's lead log |
The address format and the secret are described on the Incoming postback page, repeats and status changes on the Transaction ID, duplicates and conversion corrections page. If a postback was sent but there are no records, open Postback not arriving: what to check.
To see the records of one conversion, enter the click's subid in the Search field. The Received postback records and the records about an unrecognized payout and about an offer lead do not contain the subid and will not show up in such a search.
S2S postbacks
Columns: Date and time, Text. One record is written for each attempt to send an S2S postback:
Campaign #<ID>: postback (source); Sub_id: <subid>; Attempt: 1; HTTP 200
Campaign #<ID>: postback (campaign); Sub_id: <subid>; Attempt: 2; Failed: connection_failed| Part of the record | What it means |
|---|---|
Campaign #<ID> | The click's campaign |
(source), (campaign), (source_and_campaign) | The recipient: the source, an additional campaign address, or the same address for both — see Campaign and source S2S postbacks |
Sub_id | The click's subid. The Search field finds records by it |
Attempt | The attempt number for this delivery |
HTTP <code> | The recipient responded with this HTTP code |
Failed: connection_failed | The tracker could not connect to the recipient; the request was not sent |
Failed: unknown_delivery | The request was sent, but no response was received. The event may have been delivered |
Failed: invalid_url | The postback address could not be parsed or does not start with http:// or https:// |
Failed: blocked_address | The address leads to a non-public IP; the tracker does not send to such addresses |
The postback address is not included in the record. CAPI deliveries are not recorded here.
The tab also gets a record about a Facebook event that the tracker could not prepare:
CAPI: pixel/token не найдены (ни в источнике, ни в клике, ни в параметрах кампании) — click <subid>It means the source has sending to Facebook enabled, but the pixel or token was not found, and the event was not sent. Where they are set is described on the Facebook Conversions API page.
Among the S2S records, this one is easiest to find with search: enter CAPI: in the Search field.
See the state and result of each S2S and CAPI delivery on the Event delivery («Доставка событий») tab — see Event delivery log and resending.
Traffic
The click processing log. Recording is off by default, and the tab shows: “Traffic logging is off — turn on the ‘Log’ toggle to record the click pipeline.” («Логирование трафика выключено — включите тумблер «Логировать», чтобы записывать пайплайн кликов.»)
Turning it on
- Open the Traffic tab.
- Click the Log toggle. There is no confirmation; the setting is saved immediately.
- Wait up to 15 seconds — that is how long it takes to apply the setting.
- Send a test click or wait for traffic.
To turn recording off, click the toggle again. Turning it off is applied with the same delay. Records made before you turned it off stay in the log.
What a record contains
One record is a block of text of several lines. A record of a visit to a campaign link starts like this:
[ClickContext]
Starting pipeline
Possible IP headers: x-forwarded-for: 203.0.113.10, 198.51.100.24; cf-connecting-ip: 203.0.113.10; x-real-ip: Empty
Requested: https://track.example.com/summer?sub_id_1=testPossible IP headers lists three request headers that may carry the visitor's IP; an empty header is shown as the word Empty. cf-connecting-ip holds the visitor's IP; if the request did not come through Cloudflare or a reverse proxy node, it holds the connection address. x-forwarded-for may contain several comma-separated addresses. Requested is the full requested address, with parameters.
The rest of the block depends on how processing ended:
| Continuation of the block | What it means |
|---|---|
Searching campaign, Processing campaign <alias>, Stream "<name>" chosen (type …, action …), Saving clicks: 1, User info: {…} | The click is recorded. You can see the campaign alias, the chosen stream, its type and action |
Searching campaign, Campaign not found. Shows 404 NotFound | There is no campaign at this address, or it is not active. The visitor got 404 |
[Cloak server] Завёрнут на whitepage до челленджа. Причина: … | Cloaking filtered out the visit at the server checks; the reason is at the end of the line. This record has no subid. A record of the first kind is also written for the same click — with the stream the visitor got |
The [Cloak challenge] SubID … record comes without this beginning. It holds the JS check decision for the click: the score and threshold, the reasons, the browser signals and the outcome. The reasons are explained on the Diagnostics: why a click went to “white” page.
Fields of the User info line:
| Field | Value |
|---|---|
SubID | The click's subid |
IP, UserAgent | The visitor's IP and User-Agent |
Country, Region, City | Country, region and city according to the GEO databases |
Isp, Connection Type | Provider and connection type |
OS, Browser, Device type | OS, browser and device type |
Is bot | yes or no — whether the click was classified as a bot |
Is unique in campaign | yes or no — whether the click is unique in the campaign |
The traffic log keeps visitors' IPs, User-Agents and request addresses with all link parameters. The log is shared by the installation and visible to all owners and admins. Recording goes on while the Log toggle is on.
With heavy traffic, 2000 records fill up quickly, and the click you need gets pushed out. Look for it right after the visit: enter the subid or IP in Search and click live to stop the feed. The click's data for the whole retention period is on the Clicks and leads («Клики и лиды») tab, see Click and lead search.
Clearing a log
- Open the tab of the log you want to clear.
- Click Clear.
- Confirm the prompt “Clear the log?” («Очистить лог?»).
All records of this log are deleted for the whole installation. The other three logs are not affected.
Deleted records cannot be restored.
Clearing a log and switching the Log toggle are recorded on the Audit log tab. In the Resource («Ресурс») column, they have the value logs:
- clearing — the
deleteaction, and the ID column shows the log:system,postback,s2sortraffic; - the Log toggle — the
updateaction, and the ID column has the valuetraffic-enabled.
How to search the action log is described on the Audit log: user action log page.
Frequently asked questions
The “Log” toggle is on, but there are no records
The setting takes up to 15 seconds to apply. Records appear only on visits to campaign links. Check that the Search field is empty and click Refresh.
A record was there and disappeared
The log keeps the 2000 latest records: old ones are pushed out by new ones. Or another admin cleared the log — clearing is visible on the Audit log tab.