Click API

Choose the correct API

Click API works with the tracking visit and routing flow. The authenticated management API creates or reads panel resources. They serve different purposes; do not substitute a management API key into a public tracking link.

Get the generated configuration

Open Settings → Click API and the related examples available in your installation. Keep the exact endpoint, method, parameter names and return fields shown there. Use the campaign key for the intended campaign and pass source values in their configured fields.

Integrate step by step

1. Make a request for a dedicated test campaign.
2. Inspect the returned tracking context and destination fields.
3. Keep the returned click ID available for the lander-to-offer and conversion flow.
4. Apply the response in your application without adding an extra duplicate tracking request.
5. Verify the click and subsequent conversion in the panel.

Forward request context carefully

A server-side request originates from your application server. Follow the supported contract for visitor properties; do not assume the application's own IP or user agent describes the visitor. Keep the original values and avoid arbitrary header spoofing.

Failure handling

Record response status and non-sensitive diagnostics. Do not silently replace a failed tracking request with a fresh unrelated click. For the management API, see API access.