Actions72
- Кампания Actions
- Лендинг Actions
- Оффер Actions
- Клик Actions
- Настройки Actions
- Пользователь Actions
- Блэклист Actions
- Бот Actions
- Постбэк Actions
- Источник Actions
- Конверсия Actions
- Статистика Actions
- Группа Actions
- Поток Actions
- Фильтр Actions
- Лог Actions
- Домен Actions
Overview
The node integrates with the Keitaro API to perform various operations on different resources. Specifically, for the resource "Клик" (Click) and operation "Получить Все" (Get All), it fetches a list of clicks from the Keitaro system. It supports filtering clicks by date range, interval presets, main filters (campaign ID, stream ID, landing ID, offer ID), additional filters (country code, IP address, bot status, unique clicks, conversions, and Sub IDs), and pagination and sorting options. This node is useful for retrieving detailed click data for analysis, reporting, or further processing in marketing and traffic management workflows.
Use Case Examples
- Retrieve all clicks from a specific campaign within a date range to analyze traffic sources.
- Fetch unique clicks with conversions for a particular offer to evaluate campaign performance.
- Get paginated click data sorted by creation time for integration with external analytics tools.
Properties
| Name | Meaning |
|---|---|
| Параметры Фильтрации Кликов | Parameters for filtering clicks when retrieving the list |
Output
JSON
data- Array of click objects matching the filter criteriacount- Number of clicks returned in the responserequesturl- The URL of the API request mademethod- HTTP method used for the API request
resource- Resource type, here it will be 'click'operation- Operation performed, here it will be 'getAll'
Dependencies
- Requires an API key credential for Keitaro API access and the domain URL of the Keitaro instance.
Troubleshooting
- Ensure the API key and domain are correctly configured in the credentials; missing or incorrect values will cause authentication errors.
- When using date range filters, both start and end dates must be provided; otherwise, a limit must be set to avoid errors.
- If the API returns an error status, check the error message for details such as invalid parameters or permission issues.
- For large data sets, use pagination parameters (limit and offset) to manage response size and avoid timeouts.
Links
- Keitaro API Documentation - Official documentation for the Keitaro API endpoints and parameters.