> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/destinations/destinations-catalog/kwanko.md).

# Kwanko

[Kwanko ](https://www.kwanko.com/)provides a global affiliation network connecting businesses with customers.\
Using this destination you can implement server-side lead and sale tracking.

## Key features

The Kwanko destination provides the following key features:

* **Events structure**: our [Events reference](https://community.commandersact.com/platform-x/developers/tracking/events-reference) covers Kwanko lead and sale tracking, meaning that your data is properly bridged to the expected fields in an optimized way.
* **Prebuilt mappings**: data mapping for event-based destinations happens automatically, which simplifies user inputs.
* **Smart mapping**: data mapping can be readjusted using your datalayer defined fields.
* **Custom properties**: you can freely push custom properties based on your specific needs.

## Destination setup

### Configuration

<table><thead><tr><th width="338">Settings</th><th>Description</th></tr></thead><tbody><tr><td><code>Collection Server Base Url</code></td><td><p><em><strong><code>Required</code></strong></em></p><p>Your collection server base URL (E.g. "http://server.client.fr") as provided by Kwanko. Default value: "https://action.metaffiliation.com/trk.php".</p></td></tr><tr><td><code>Tracking Id</code></td><td><p><em><strong><code>Required</code></strong></em></p><p>Your tracking identifier as provided by Kwanko. It's used to identify your campaigns.</p></td></tr><tr><td><code>Conversion Type</code></td><td><p><em><strong><code>Required</code></strong></em></p><p>The conversion type that is bound with your activity. This can be either <code>sale</code> or <code>lead</code>. If conversion type is <code>lead</code>, only <code>generate_lead</code> events are forwarded to Kwanko. If conversion type is <code>sale</code>, only <code>purchase</code> events are sent to the partner.</p></td></tr><tr><td><code>Cookie Click Id</code></td><td>This is required if a value is not provided via the "Smart Mapping" field <code>Kwanko Click Id</code> .<br>For each click on Kwanko links a new "Click Id" is automatically generated. This can be found as value for the parameter <code>kwks2s</code> in landings. Input the cookie name holding this value.</td></tr><tr><td><code>Custom Event Properties</code></td><td>Map your custom event properties by setting their field names in <code>Kwanko property name</code> and adding the field name holding the value in <code>Your event property</code> .</td></tr></tbody></table>

## Quick reference

| Commanders Act Events | Kwanko Tracking |
| --------------------- | --------------- |
| `generate_lead`       | `lead`          |
| `purchase`            | `sale`          |

## Field mappings

{% hint style="info" %}
Properties can be remapped using our [Smart Mapping](https://doc.commandersact.com/features/destinations/advanced-mapping#smart-mapping) feature.\
The Kwanko property <mark style="color:blue;">`gdpr_kwk`</mark> is always set to <mark style="color:blue;">`1`</mark> . Manage your consent settings using the filter tab of this destination.
{% endhint %}

| Commanders Act Properties                                                     | Kwanko Properties     |
| ----------------------------------------------------------------------------- | --------------------- |
| `Tracking Id`                                                                 | `mclic` **\[\*]\[1]** |
| <p><code>partners.kwanko.click\_id</code><br><code>Cookie Click Id</code></p> | `cible` **\[\*]\[2]** |
| `revenue`                                                                     | `argmon`              |
| `id`                                                                          | `argann`              |
| `coupon`                                                                      | `argmodp`             |
| `currency`                                                                    | `nacur`               |
| `coupon`                                                                      | `argbr`               |

{% hint style="info" %}
**\*** Mandatory property.\
**1.** If <mark style="color:blue;">`Collection Server Base Url`</mark> is not the default value, the <mark style="color:blue;">`Tracking Id`</mark> is appended as part of base URL and the <mark style="color:blue;">`mclic`</mark> is not set.\
**2.** Priority on the left side. You can set the "Smart Mapping" field <mark style="color:blue;">`Kwanko Click Id`</mark> to provide a value for this property.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.commandersact.com/features/destinations/destinations-catalog/kwanko.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.