Documentation sections

Campaign target diagnostics and monitoring

Checking the offers and landing pages of active streams, and regular checks of the campaign's external links.

Campaign targets are the offers and landing pages selected in its active streams. The Campaign target diagnostics and monitoring («Диагностика и мониторинг целей кампании») block checks the settings of each target and whether external links respond. The block is visible to everyone who has access to the campaign; monitoring is turned on and off by the owner and the admin.

Where the block is

  1. Open the Campaigns («Кампании») section.
  2. Open the campaign you need.
  3. Under the Traffic link («Ссылка для трафика») block, click the Campaign target diagnostics and monitoring row — the block expands.

The block has two parts. At the top is a one-time check run with the Check configuration («Проверить конфигурацию») button. Below it is HTTP monitoring («HTTP-мониторинг»), which checks the targets on its own on a schedule. Each part has its own results table.

Check configuration

A one-time check of the active streams' settings and the hosted pages' files. No requests are sent to external sites.

  1. Click Check configuration. While the check is running, the button says “Checking…” («Проверка…»).
  2. Look at the table under the button: the Stream («Поток»), Target («Цель»), Result («Результат») and Time («Время») columns.

What is checked for each offer and landing page:

  • the offer or landing page exists and is not deleted;
  • the offer has the active («активен») status;
  • a hosted page has uploaded files, and index.php or index.html is in their root;
  • an external page has an address that starts with http:// or https://;
  • the target's share in the stream is not 0;
  • a stream with the Landing → offer funnel («Воронка ленд→оффер») action has at least one offer selected.

Disabled streams (marked “paused” («пауза»)) are not included in the check. If the active streams have no targets, “No targets in active streams” («Нет целей в активных потоках») appears under the table.

The result of a one-time check is not saved and does not go to the history. The Time column shows a dash here: response time is measured only by HTTP monitoring.

Turn on HTTP monitoring

Monitoring is off by default and is turned on separately for each campaign. The button is visible to the owner and the admin.

  1. Expand the Campaign target diagnostics and monitoring block.
  2. Click Enable monitoring («Включить мониторинг»). The header changes to “HTTP monitoring · enabled” («HTTP-мониторинг · включён»).
  3. Wait for the result. Until the first check, the line “Waiting for the first check. The result will appear automatically.” («Ожидается первая проверка. Результат появится автоматически.») is shown.

To stop the checks, click Disable monitoring («Выключить мониторинг»). The collected history stays in the block.

Tip.

Checking an external link is a request to the external site with the Tracker-Health/1.0 User-Agent header. The external site may count such requests.

How the check works

  • Monitoring repeats the configuration check. External pages that passed it without issues get a request with the HEAD method.
  • The check runs about every 5 minutes while the campaign is active. A paused or archived campaign gets no new checks.
  • The response is awaited for up to 5 seconds.
  • Redirects are not followed: only the first response from the link counts.
  • Links with macros, for example with {subid}, are not requested. Macros are described on the Macros in links and pages page.
  • Links whose address contains a login or password, and links with a port other than 80 and 443, are not requested.
  • Hosted pages are checked by their files, without an HTTP request.
  • One check requests up to 50 different addresses. The same link in several streams is requested once.
  • While the license is inactive, monitoring is paused — see License expiry.

Results and messages

In the HTTP monitoring part, the table is headed by “Errors found: N” («Обнаружено ошибок: N») or “No errors found; check the warnings in the table” («Ошибок не обнаружено; проверьте предупреждения в таблице»). Warnings are not included in the error count. In both tables, errors in the Result column are highlighted red, warnings orange, and targets without issues green.

The Time column shows the response time in milliseconds — only for targets that returned an HTTP response.

Errors

MessageWhat it meansWhat to do
“Offer is missing or deleted” («Оффер отсутствует или удалён»), “Landing page is missing or deleted” («Лендинг отсутствует или удалён»)The target is selected in the stream but has been deleted. The Target column shows its ID instead of the nameRestore the page from the trash or remove it from the stream
“Local archive not uploaded” («Локальный архив не загружен»)The hosted page has no uploaded filesUpload an archive — see Hosted pages
“No index.php or index.html” («Нет index.php или index.html»)There is neither index.php nor index.html in the root of the hosted page's filesAdd the file in the editor
“No valid HTTP(S) URL set” («Не задан корректный HTTP(S) URL»)The external page has an empty address, or the address starts with neither http:// nor https://Fix the address in the offer or landing page
“HTTP 404”, “HTTP 500” and other codes without an explanationThe external link responded with an errorCheck the address in the offer or landing page
“No HTTP response: network, DNS, TLS or forbidden address” («Нет HTTP-ответа: сеть, DNS, TLS или запрещённый адрес»)No response was received: the site did not respond within 5 seconds, the domain was not found, there was a certificate error, or the domain leads to a non-public addressOpen the link in a browser, check the domain and the page's certificate
“Could not read target configuration” («Не удалось прочитать конфигурацию целей»)The campaign's streams could not be read during the check. There is one such row for the whole checkMonitoring will repeat the check on schedule

Warnings

MessageWhat it meansWhat to do
“HTTP 301: redirect, final page not checked” («HTTP 301: редирект, конечная страница не проверена»)The link responded with a redirect; the code can be any 3xx. Monitoring does not look at where it leadsOpen the link in a browser and check the final page
“HTTP 403: HEAD rejected or limited” («HTTP 403: HEAD отклонён или ограничен»)The site responded to the HEAD request with 403, 405, 429 or 501Check the link in a browser
“HTTP not checked: dynamic or unsupported URL” («HTTP не проверен: динамический или неподдерживаемый URL»)The link has macros, a login or password, or a port other than 80 and 443Check the link manually
“HTTP not checked: invalid URL” («HTTP не проверен: некорректный URL»)A request could not be built from the addressFix the target's address
“HTTP not checked: limit of 50 addresses per check” («HTTP не проверен: лимит 50 адресов за проверку»)The active streams have more than 50 different external addresses, and this one was not requestedCheck the link manually
“Offer is not active” («Оффер не активен»)The offer has the paused («пауза») or archived («архив») status. An offer restored from the trash also gets the paused statusIn the Edit offer («Изменить оффер») window, choose active in the Status («Статус») field — see Offers. Or replace the offer in the stream
“Weight 0: target excluded from distribution” («Вес 0: цель исключена из распределения»)The target's share in the stream is 0: the item is excluded from rotationIf the target should get traffic, set a share above 0 on the Rotation («Ротация») tab of the stream settings — see Rotation
“No offers selected in the stream” («В потоке не выбраны офферы»)A stream with the Landing → offer funnel action has no offersAdd an offer with the + Item («+ Элемент») button on the Rotation tab of the stream settings

No issues

  • “Configuration available” («Конфигурация доступна») — the target's settings are fine. For the one-time check and for hosted pages this is the final result.
  • “HTTP 200” and other 2xx codes — the external link responds.

Check history

Above the monitoring table there is a list with the dates and times of checks. The latest one is selected by default. Choose another row, and the table shows the result of that check.

  • The list shows the last 20 checks.
  • Up to 100 checks are kept per campaign; older ones are deleted.
  • While the block is expanded, the data refreshes itself every 30 seconds.
  • The “Result older than 10 minutes” («Результат старше 10 минут») note appears when monitoring is on and the check selected in the list is more than 10 minutes old. If the note is on the latest check, new checks are not happening — for example, the campaign is paused.

What monitoring does not do

  • It does not change traffic routes: a stream with an unavailable target keeps working until you change it yourself.
  • It does not send notifications. View the results in the block or get them via the Admin API.
  • It does not open the page as a visitor would: content, forms and the redirect destination are not checked.
  • It does not check the address of a stream with the Direct URL («Прямой URL») action — only offers and landing pages. Stream actions are described on the Stream actions page.

To find out which stream a visitor will get into, use the stream selection check.

Troubleshooting

There is no “Enable monitoring” button

Only the owner and the admin see this button. The other roles can check the configuration and view the results.

“Waiting for the first check. The result will appear automatically.”

Monitoring is on, but there has been no check yet. Checks run only for an active campaign. If the campaign header shows the “paused” status, click Start («Запустить»). If the campaign is active but there is no result, open the Status («Состояние») section and find the Target monitoring («Мониторинг целей») row in the Background tasks («Фоновые задачи») block — see System status.

An offer with macros in its link has no HTTP check

This is expected: the row shows “HTTP not checked: dynamic or unsupported URL”. Without a real click there is nothing to substitute into the macros, so monitoring does not request such links. Check the link manually.

Updated Need help? ↗