Logs

This is the "something broke" screen. Three raw logs live behind one tabbed screen: Clicks, API log and Postbacks. All three are read-only. You don't edit anything, you don't delete anything — you just see what actually happened.

Every tab is built the same way: a paged table with a pager, filters above it, and a row detail view on click. What differs is the columns and which kind of event you're looking at.

One shared trait, learn it up front: there's no sorting here. None. That's not a bug or a missing feature — it's deliberate. Logs always run newest-first (by internal id, descending), and clicking a column header sorts nothing. Want to find something? Filter, don't sort.

Clicks tab

The raw visit log. Each row is one click on your link: who arrived, from where, which campaign they hit and where the stream sent them.

Columns:

• Time — when the click happened (in your timezone).
• Campaign — the campaign (flow) the visit landed in.
• Stream — the stream (way) that fired.
• Landing — the landing (site) that was shown.
• Country — the geo, always UPPERCASED (RU, KZ, FR).
• IP — the visit's IP address.
• utm_source — the source.
• SubID — the sub-id.
• Payout — click price with currency.

Shows 50 rows per page, newest first. The Device, OS, Browser, utm_campaign and utm_medium columns are hidden by default — see the Columns section below to switch them on.

Filters (the Filters button above the table): date (from/to), campaign, stream, landing, click id, geo, IP, hour, filter (cloaker), browser, OS, mobile, all utm_*, domain, SubID.

API log tab

The raw log of incoming API calls: what hit the tracker from the outside — pixels, connectors, third-party integrations. Come here when "the pixel didn't land" or "the integration went quiet."

Columns:

• Time — when the call arrived.
• App — which app was called (flows, fbpix, p2b, etc.).
• Function — which function was called.
• Status — a green OK pill or a red Error pill.
• Error — the error text, if there was one.
• IP — where the call came from.
• Country — the call's geo.
• Click — the linked click, if any.
• Lead — the linked lead, if any.
• Campaign — the linked campaign, if any.

Shows 30 rows per page, newest first.

Filters: date (from/to), tags tag1…tag7, and Error — a dropdown with three modes: all records, clean only (no errors), or errors only. "Errors only" is code -2 under the hood; pick it and only the red rows remain. Exactly what you want when you're hunting for what broke.

Postbacks tab

The raw log of outgoing postbacks: what the tracker sent to the network or to your own integration, and what came back. This is the very screen where a web finally sees why the postback didn't fire — instead of blaming the tracker in the chat.

Columns:

• Time — when the postback was sent.
• Event — which event fired it (new / hold / approve / cancel / trash).
• Campaign — from which campaign.
• Click — for which click.
• Lead — for which lead.
• Landing — which landing was involved.
• Result — a pill: green approve (delivered) or red cancel (not delivered).
• HTTP — the server's response code (200, 404, 500…).
• Timer — how long the send took (e.g. 0.016s).

Shows 30 rows per page, newest first.

Filters: date (from/to), campaign, click, lead, landing, event.

Row detail view

Clicking a row (or the expand glyph on the right) opens the details. This is where the actual detective work begins.

• In Clicks — the full visit meta: id, short code, user, campaign, stream, landing, next step, uniqueness, filter, IP, country, full User-Agent, mobile flag, payout, currency, all utm_*, domain, SubID.
• In the API log and Postbacks — the decoded request and response bodies. JSON is pretty-printed (indented), so you read it with your eyes instead of untangling one long string. If a body isn't JSON — a plain string, or the tracker sent a string as-is — it's shown as-is; if decoding fails, the raw text is shown.

These two blocks — the request body and the response body — are what answer "why didn't the postback fire." The response code and error text inside them are the proof.

Columns

The Columns button above the table opens the field list — tick fields on and off. In Clicks this is how you pull in the hidden Device, OS, Browser, utm_campaign and utm_medium.

The setting is saved on the server and survives a page reload — it's not browser memory, it's your account preference. Switch Device on once and it stays on tomorrow, and on a different computer.

CSV export

The export button downloads the current tab as CSV. The file ships with a BOM and CRLF line breaks — so Excel opens it with correct Cyrillic right away and doesn't nag about encoding.

In the export the campaign appears as a human name (not its internal hash code), geo is UPPERCASED, money is formatted with currency. So the CSV reads the same as the table on screen.

How to do it: workflows

Workflow 1. Figure out why a postback didn't fire

1. Open Logs → the Postbacks tab. (Or the API log tab, if the problem is in an incoming call — a pixel or a connector.)
2. Click Filters, set the date range (from/to). Optionally narrow by campaign, click or lead.
3. Filter for errors. In the API log, set the Error filter to errors only (code -2) — only the red rows remain. In Postbacks, look for rows with a red Result pill and a non-200 in the HTTP column.
4. Click the problem row — the detail view opens.
5. Read the request body and the response body. The HTTP code, the error text, and what actually went to the network's server are all here.

Workflow 2. Trace a specific click

1. Open Logs → the Clicks tab.
2. Click Filters and set what you know: click id, geo, IP, campaign, stream, source, SubID, date.
3. Once you've found the row, click it — the detail view opens with the full visit meta (full User-Agent, domain, all utm_*, payout, etc.).

Workflow 3. Export a log

1. Open the tab you want and set filters so only what you need remains in the table.
2. Optionally set up Columns — the export mirrors the current tab.
3. Click export — you get a CSV with BOM and CRLF, human campaign names and UPPERCASED geo. Open it in Excel.

Coming from an old tracker?

Familiar layout, just gathered into one tabbed screen:

• Клики (Clicks) — the familiar click log (Click log).
• Постбеки (Postbacks) — the familiar postback log (outgoing postbacks).
• Лог API (API log) — the familiar API-call log (API log).