Click lead data API

/api/v1/lead saves the email, phone and name in click data. It works without an API token on the tracking domain and campaign domains. This separate analytics and CAPI function does not submit an application to an affiliate network or create a form-data file log.

Binding data to a click

The /api/v1/lead address accepts GET and POST. The data is passed in the address parameters or in the request body: as a regular form or as FormData.

At least one data field is required. The tracker answers a POST with the text ok, and a GET with a transparent 1×1 image.

Ready-made form in the editor

1. Open Offers («Офферы») or Landing pages («Лендинги»).
2. In the row of the hosted page, click Editor («Редактор»).
3. Click + File («+ Файл»).
4. In the Template («Заготовка») block, choose HTML + lead form («HTML + форма лида»).
5. Check the File path («Путь файла»). The editor fills in index.html, or page.html if such a file already exists.
6. Click Create («Создать»).

The file gets a page with a form with the first_name and phone fields and a submit script:

<form id="lead-form">
  <input name="first_name" placeholder="Name" required>
  <input name="phone" placeholder="Phone" required>
  <button type="submit">Submit</button>
</form>

<script>
  document.getElementById('lead-form').addEventListener('submit', function (e) {
    var fd = new FormData(e.target);
    fd.append('click_id', '{click_id}');
    navigator.sendBeacon('/api/v1/lead', fd);
  });
</script>

The {click_id} macro is replaced with the click ID on a page opened through the campaign link. A preview has no real click. Check intake through a test campaign link rather than the preview. Working with files is described on File editor, versions and export.

Secrets and repeated submissions

/api/v1/lead validates the incoming postback secret: first the served offer's network, falling back to legacy source protection if the new setting is absent. A wrong or missing required secret returns 401. The form template does not add a secret itself.

Without a required secret, the request only fills empty fields. A correctly supplied applicable secret allows submitted fields to replace saved values; omitted fields are retained. Do not expose the secret in visitor-accessible form code.

Where the lead data is shown

The block is visible to the owner and the admin.

1. Open the campaign statistics.
2. Go to the Click log («Лог кликов») tab.
3. Click the click row.

The click window has the Lead data block with the Email, Phone («Телефон»), First name («Имя») and Last name («Фамилия») rows. Empty rows are not shown. If no form was submitted for the click, the block says “no data (the lead did not submit the form)” («нет данных (лид не отправлял форму)»). The click card in the Logs («Логи») section does not show contacts — it shows only the time the form data was updated.

The tracker also inserts this data into the Facebook Conversions API event when the email, phone or name did not arrive in the postback.

In release 20261101.1, HTTP 200 means the request has been saved in the lead queue; the click card may receive its contact data later. An accepted queued request does not necessarily produce an entry in Logs → Postbacks. Check the click card and, as the owner or admin, GET /api/v1/maintenance/lead-queue for queue counters without contact data.

Limits

• 600 requests per minute from one IP.
• 1 MiB per request body.
• GET parameters, a regular POST form and multipart/form-data are accepted; JSON is not a format of this endpoint.

Errors and checks

Use a test click and recipient: the request response, click data and the affiliate network receiving an application are separate checks. Calling navigator.sendBeacon does not itself confirm server receipt. Do not resubmit a real application only because a thank-you page did not appear.

The form-data file log has been removed. A custom leads.php handler remains an ordinary page PHP file; the PHP rules and page protection apply separately.