---
title: "Request Structure"
slug: "request-structure"
updated: 2025-10-17T13:30:44Z
published: 2025-10-17T13:30:44Z
canonical: "docs.mapp.com/request-structure"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request Structure

Each tracking request sent to Mapp Intelligence follows the same structure, regardless of whether it originates from the client-side pixel or from a server-to-server integration.

The key element of the request is the parameter **p**, which combines several pieces of information into a single, comma-separated string.

---

## Structure Overview

A tracking request consists of the tracking domain, the tracking ID, and the p parameter that bundles the core information.

```xml
http[s]://[track-domain]/[track-id]/wt?p=[version],[page-name],[javascript],
    [screen-resolution],[color-depth],[cookies],
    [client-time],[referrer],[screen-size],[java]
```

Each value inside the p parameter is separated by a comma (,).

If a value is missing, use 0 as a placeholder.

---

### Request Example

```bash
https://track.webtrekk.net/111111111111111/wt?p=600,home,1,1024x768,32,1,1730181123123,https%3A%2F%2Fwww.google.de,1000x700,1
```

This example represents a standard server-to-server pageview request sent to the Mapp Intelligence tracking server.

All values are transmitted in UTF-8 encoding.

---

## Request Elements

| **Element** | **Description** | **Example** |
| --- | --- | --- |
| Track Domain | The tracking domain provided by Mapp Intelligence. | track.webtrekk.net |
| Track ID | Your unique identifier for data collection. | 111111111111111 |
| wt?p= | The parameter that holds the compact set of core tracking values. | p=600,home,1,... |

---

### Structure of the p Parameter

```bash
p = 
600,                         # version (fixed value for S2S)
home,                        # page name (formerly content ID)
1,                           # JavaScript active (1) / inactive (0)
1024x768,                    # screen resolution
32,                          # color depth
1,                           # cookies active (1) / inactive (0)
1730181123123,               # client time (ms)
https%3A%2F%2Fwww.google.de, # referrer (URL encoded)
1000x700,                    # screen size
1                            # Java active (1) / inactive (0)
```

| **Field** | **Description** |
| --- | --- |
| **Version** | Internal protocol version used by Mapp Intelligence. For all **server-to-server (S2S)** implementations, use the fixed value 600. |
| **Page Name (formerly Content ID)** | Identifier for the current page or screen (for example home or product-detail). |
| **JavaScript** | 1 = active, 0 = inactive. |
| **Screen resolution** | Width × height of the display. |
| **Color depth** | Color depth in bits. |
| **Cookies** | 1 = active, 0 = inactive. |
| **Client time** | Local time of the visitor (in milliseconds). |
| **Referrer** | URL of the previous page (**must be URL-encoded**). |
| **Screen size** | Size of the browser window. |
| **Java** | 1 = active, 0 = inactive. |

> [!NOTE]
> Note
> 
> All parameters must be transmitted using UTF-8 encoding.
> 
> Values that include special characters (such as URLs) must be URL-encoded.

---

### Additional Parameters

Beyond the p parameter, additional information such as IP address, referrer, or user agent can be passed as header or URL parameters — for example:

```plaintext
X-WT-IP=212.5.8.2
X-WT-UA=Mozilla/5.0 (Windows NT 10.0; WOW64)
X-WT-RQ=https%3A%2F%2Fsub.domain.tld%2Fhome.html
```

See [Specific Parameters](/v1/docs/specific-parameters) for more details.

---

## Supported Characters and Data Formats

The following rules apply to all parameter values sent in a server-to-server request.

**General Rules**

- **Encoding:** UTF-8
- **Maximum request size:** 7 KB
- **Case sensitivity:** All input is case-sensitive

---

**Data Types**

| **Type** | **Description** | **Limit** |
| --- | --- | --- |
| **Text** | Stores string values. If configured for multiple values, each individual value can contain up to 255 characters. Each value is stored separately in the database. | 255 characters per value |
| **Figure** | Stores numeric values. Supported range: decimal(12,2) → up to 10 digits with 2 decimal places. | −9 999 999 999.99 to +9 999 999 999.99 |

---

**Automatically Filtered Characters**

Certain characters are automatically removed during data processing and should therefore not be included in tracking requests.

| **Character Range / Symbol** | **Description** |
| --- | --- |
| 0x00–0x1F | Non-printable ASCII characters |
| ' | Single quote |
| " | Double quote |
| < > \ | Angle brackets and backslash |
| 0xA0 | Non-breaking space |

Additional cleanup rules:

- Multiple spaces are reduced to one.
- Leading and trailing spaces are automatically trimmed.

Specify your Mapp Intelligence track domain. This information is provided by your account manager.

Track IDs are used to assign requests to an account. You find the track ID under *Mapp Q3 >**Configuration > System Configuration > Data Collection.* If the same information is to be recorded for multiple accounts, you can enter the corresponding Track IDs of the accounts comma-separated.