# Mapp

[Mapp](https://mapp.com/), formerly Webtrekk, generates actionable insights for brands to engage with their customers and deliver cross-channel marketing campaigns. Using this destination you can implement Mapp [server-side tracking](https://documentation.mapp.com/1.0/en/server-to-server-7240721.html).

## Key features

The Mapp destination provides the following key features:

* **Events structure**: our [Events reference](https://community.commandersact.com/platform-x/developers/tracking/events-reference) covers [Mapp request types](https://documentation.mapp.com/1.0/en/which-request-types-are-supported-by-mapp-intelligence-36143348.html), 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.
* **Custom events and properties**: you can freely push custom events and properties based on your specific needs.
* **Support for multi-item data**: information included in the [item](https://community.commandersact.com/platform-x/developers/tracking/events-reference#item) array is dispatched to Mapp.

## Destination setup

{% hint style="info" %}
This destination supports Mapp [independent parameters](https://documentation.mapp.com/1.0/en/implementation-3-setup-options-for-the-tracking-of-elements-7209582.html#id-.Implementation3SetupOptionsfortheTrackingofElementsv1.0-12.2Independentparameters) by detecting them in<mark style="color:blue;">`Custom Event Properties`</mark>. See [Configuration](#configuration) for more details.\
Use [**Destination filters**](https://doc.commandersact.com/features/destinations/destination-filters) to refine events and/or other properties matching your specific needs.
{% endhint %}

### Configuration

<table><thead><tr><th width="150">Settings</th><th>Description</th></tr></thead><tbody><tr><td><code>Track Domain</code></td><td><p><em><strong><code>Required</code></strong></em></p><p>Your track domain as provided by Mapp.</p></td></tr><tr><td><code>Track Id</code></td><td><p><em><strong><code>Required</code></strong></em></p><p>Your track identifier as provided by Mapp.</p></td></tr><tr><td><code>Custom Event Properties</code></td><td><p>Map your custom event properties by setting their field names in <code>Event property name</code> and adding the field name holding the value in <code>Commanders Act event property</code>. E.g. if you input<code>size</code>in the <code>Event property name</code> and <code>items.0.product.size</code> in <code>Commanders Act event property</code>, you'll have a custom event property in Mapp called<code>size</code>with a value based on the content of the field <code>items.0.product.size</code> <strong>[1]</strong>.</p><p><br>In the column <code>Commanders Act event property position</code> you should keep the default value <code>Default (root)</code> as it better fits most scenarios. In case you select either <code>In "items" {items.X}</code> or <code>In "product" {items.X.product}</code> this destination will look for the input event property starting from the <a href="https://community.commandersact.com/platform-x/developers/tracking/events-reference#item">items </a>or <a href="https://community.commandersact.com/platform-x/developers/tracking/events-reference#product">product </a>level respectively and concatenate values separated by a semicolon (";").</p></td></tr><tr><td><code>Exclude Mapp "ct" Parameter</code></td><td>Under the "Advanced Settings", you have the option to exclude the Mapp <code>ct</code> parameter by flagging this checkbox. More information on this parameter are available in the <a href="#field-mappings">Field Mapping</a> section.</td></tr></tbody></table>

{% hint style="info" %}
**\[1]** Using "dots" (".") you can navigate deeper to the specific field you want to get the value of. See [Events reference](https://community.commandersact.com/platform-x/developers/tracking/events-reference) for more details on the standard field names by event. You can also freely set custom fields: there are no boundaries.
{% endhint %}

## Quick reference

| Commanders Act Events | Mapp Request Type                               |
| --------------------- | ----------------------------------------------- |
| `[Any Event]`         | `page` or `event` or `media` or `form` **\[1]** |

{% hint style="info" %}
**\[1]** Custom events are also supported. More details on Mapp request types are available following this [LINK](https://documentation.mapp.com/1.0/en/which-request-types-are-supported-by-mapp-intelligence-36143348.html).
{% endhint %}

## Field mappings

{% hint style="info" %}
Session handling is done by Mapp using the ever id. If this information is not available, the session is recognized by the user agent and the IP address. More details are available following this [LINK](https://documentation.mapp.com/1.0/en/session-and-visitor-handling-7240758.html).\
Depending on Mapp request types you're sending, some properties may not be tracked by Mapp. More details are available following this [LINK](https://documentation.mapp.com/1.0/en/which-request-types-are-supported-by-mapp-intelligence-36143348.html).
{% endhint %}

<table><thead><tr><th width="418">Commanders Act Properties</th><th>Mapp Properties</th></tr></thead><tbody><tr><td><code>partners.mapp.version</code>,<code>page.title</code>,0,<code>device.screen.width</code>x<code>device.screen.height</code>,<code>device.density</code>,0,<code>event_timestamp</code>,<code>page.referrer</code>,<code>device.screen.width</code>x<code>device.screen.height</code>,0</td><td><code>p</code> <strong>[1]</strong></td></tr><tr><td><p><code>partners.mapp.ceid</code></p><p><code>device.sdk_id</code></p><p><code>user.tcId</code></p></td><td><code>ceid</code> <strong>[2]</strong></td></tr><tr><td><p><code>partners.mapp.eid</code></p><p><code>cookie</code> <a href="https://documentation.mapp.com/1.0/en/session-and-visitor-handling-7240758.html"><strong>wt3_eid</strong></a></p></td><td><code>eid</code> <strong>[2]</strong></td></tr><tr><td><code>device.ip</code></td><td><code>X-WT-IP</code></td></tr><tr><td><code>device.user_agent</code></td><td><code>X-WT-UA</code> <strong>[3]</strong></td></tr><tr><td><code>page.url</code><br><code>page.location</code></td><td><code>X-WT-RQ</code> <strong>[2][3]</strong></td></tr><tr><td><code>page.lang</code></td><td><code>la</code></td></tr><tr><td><p><code>partners.mapp.event_name</code> or</p><p><code>event_name</code></p></td><td><code>ct</code> <strong>[2][4]</strong></td></tr><tr><td><code>currency</code></td><td><code>cr</code></td></tr><tr><td><code>id</code></td><td><code>oi</code></td></tr><tr><td><code>value</code></td><td><code>ov</code></td></tr><tr><td><code>(event_name)</code></td><td><code>st</code> <strong>[5]</strong></td></tr><tr><td><code>items.X.product.name</code></td><td><code>ba</code> <strong>[6]</strong></td></tr><tr><td><code>items.X.product.price</code>*<code>items.X.quantity</code></td><td><code>co</code> <strong>[6]</strong></td></tr><tr><td><code>items.X.quantity</code></td><td><code>qn</code> <strong>[6]</strong></td></tr><tr><td><code>items.X.list_position</code></td><td><code>plp</code> <strong>[6]</strong></td></tr><tr><td><code>Custom Event Properties</code></td><td><code>[Custom Property Name]</code> <strong>[7]</strong></td></tr></tbody></table>

{% hint style="info" %}

> **\[1]** Default value: <mark style="color:blue;">`300,0,0,0,0,0,event_timestamp,0,0,0`</mark>.  \
> \&#xNAN;**\[2]** Priority order is listed in the left column.  \
> \&#xNAN;**\[3]** Encoded property.  \
> \&#xNAN;**\[4]** Property excluded with [**page\_view**](https://doc.commandersact.com/developers/tracking/events-reference#page_view) event.  \
> \&#xNAN;**\[5]** If the [**items**](https://community.commandersact.com/platform-x/developers/tracking/events-reference#item) array is filled and depending on incoming events, this is set with:\
> •<mark style="color:blue;">**`add`**</mark>, for [**add\_to\_cart**](https://doc.commandersact.com/developers/tracking/events-reference#add_to_cart) event.\
> •<mark style="color:blue;">**`conf`**</mark>, for [**purchase**](https://doc.commandersact.com/developers/tracking/events-reference#purchase) event.\
> •<mark style="color:blue;">**`view`**</mark>, as default value.  \
> \&#xNAN;**\[6]** Product information separated by semicolon and computed amounts are rounded with two decimals.  \
> \&#xNAN;**\[7]** See<mark style="color:blue;">`Custom Event Properties`</mark>in [Configuration ](#configuration)for more details on how you can bridge custom properties to Mapp.
> {% endhint %}