---
title: "Passing Client Information (X-WT Parameters)"
slug: "passing-client-information-s2s"
updated: 2025-10-10T13:31:00Z
published: 2025-10-10T13:31:00Z
canonical: "docs.mapp.com/passing-client-information-s2s"
---

> ## 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.

# Passing Client Information (X-WT Parameters)

In server-to-server tracking, some client-side information — such as IP address, user agent, or page URL — might not be automatically available.

When this data is missing, you can transmit it manually using **X-WT-… parameters**, either in the **request URL** or as **HTTP request headers**.

All X-WT-… values must be **UTF-8 encoded** when transmitted as URL parameters.

> [!NOTE]
> Note
> 
> Whenever possible, prefer sending these values as HTTP headers rather than exposing them in the URL.

---

## Overview of X-WT Parameters

| **Parameter** | **Description** | **Typical Source** | **Encoding Required** |
| --- | --- | --- | --- |
| **X-WT-IP** | Client IP address | Server log / request context | No (numeric) |
| **X-WT-UA** | User agent string | Browser header / API client | Yes (UTF-8) |
| **X-WT-RQ** | Current page URL | Referrer or server variable | Yes (UTF-8) |

These parameters provide context about the visitor when this information cannot be collected automatically.

They help Mapp Intelligence correctly associate requests with browser and session data.

---

### X-WT-IP — IP Address

The IP address of the visitor is normally available through the TCP/IP connection.

However, if requests are not sent directly from the client (for example, when your backend or proxy system forwards them), you can pass the IP address explicitly.

You can include it either:

- as a URL parameter → X-WT-IP=212.5.8.2, or
- as an HTTP header → X-WT-IP: 212.5.8.2

**Example**

```bash
https://track.webtrekk.net/111111111111111/wt?p=600,home&X-WT-IP=212.5.8.2
```

---

### X-WT-UA — User Agent

The browser identification (user agent) is usually transmitted automatically in the HTTP header. If this information is missing — for example, in backend or batch tracking scenarios — you can send it manually using the X-WT-UA parameter.

You can include it either:

- as a URL parameter →

X-WT-UA=Mozilla%2F5.0%20(Windows%20NT%2010.0%3B%20WOW64%3B%20rv%3A46.0)%20Gecko%2F20100101%20Firefox%2F46.0, or
- as an HTTP header →

X-WT-UA: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0

**Example**

```bash
https://track.webtrekk.net/111111111111111/wt?p=600,home&X-WT-UA=Mozilla%2F5.0%20(Windows%20NT%2010.0%3B%20WOW64%3B%20rv%3A46.0)%20Gecko%2F20100101%20Firefox%2F46.0
```

---

### X-WT-RQ — Page URL

The current page URL is usually transmitted automatically via the referrer header. If this information is unavailable in a server-to-server environment, you can send it manually using the X-WT-RQ parameter.

You can include it either:

- as a URL parameter →

X-WT-RQ=https%3A%2F%2Fsub.domain.tld%2Fhome.html, or
- as an HTTP header →

X-WT-RQ: https://sub.domain.tld/home.html

**Example**

```bash
https://track.webtrekk.net/111111111111111/wt?p=600,home&X-WT-RQ=https%3A%2F%2Fsub.domain.tld%2Fhome.html
```

> [!WARNING]
> Warning
> 
> The referrer of the page and the current page URL must not be identical; otherwise, the referrer will not be evaluated.

---

## Best Practices

- Use **HTTP headers** whenever possible to avoid exposing data in URLs.
- Always **UTF-8 encode** parameter values that contain special characters.
- Do **not** send identical values for the referrer and the current URL.
- Include X-WT-IP only when the original client IP cannot be resolved automatically.
- Keep parameter names and formats consistent across all server-to-server requests.