---
title: "Download and Implementation"
slug: "download-and-implementation-media-tracking"
updated: 2025-10-02T08:50:00Z
published: 2025-10-02T08:50:00Z
canonical: "docs.mapp.com/download-and-implementation-media-tracking"
---

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

# Download and Implementation

You can implement Media Tracking with or without the standard Mapp Intelligence pixel. The following steps describe how to set up and initialize the media pixel.

> [!NOTE]
> Note
> 
> If you are using SmartPixel, you do not need to follow the steps on this page.
> 
> Media Tracking is already available as a dedicated extension with its own API (MediaSession, play, pause, seek, etc.).
> 
> For details, see the SmartPixel [Media Tracking documentation](/v1/docs/integrated-media-tracking).

---

## Implementation Steps

### Step 1: Download

[Download](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/Mapp_Plugin_MediaTracking.zip) the media pixel.

### Step 2: Integration

You can integrate the media pixel in different ways:

- **Browser**

Integrate the media tracking on your website. The player actions are passed to the functions of the file `pixel-mediatracking.min.js`.
- **Server-to-server**

The media tracking is integrated directly in the multimedia player. This option works on any website, even if JavaScript is disabled.

In this case, the account information must be transmitted with each tracking call.

### Step 3: Initialization

#### Basic Initialization

Use the function `wt_init_media` to configure the media pixel.

At minimum, you must provide your Track Domain and Track ID.

```javascript
wt_init_media("track.wt-eu02.net", "111111111111111");
```

**Initialization order:**

- If no Mapp Intelligence standard pixel is integrated, the position of the media pixel file on the page does not matter.
- If a standard pixel is integrated, you must initialize the media pixel **after** the standard pixel.

#### Additional Options

**Tracking Multiple Accounts**

You can send media data to more than one account at the same time. For this, pass several Track IDs as a comma-separated list:

```javascript
wt_init_media("track.wt-eu02.net", "111111111111111,222222222222222");
```

**Sampling**

The optional third parameter defines the **sampling rate** for media requests.

```javascript
wt_init_media("track.wt-eu02.net", "111111111111111", 10);
```

- Example: 10 means that only every 10th request (10 %) is recorded.
- **Use case:** Sampling is only recommended for very high-traffic environments to reduce processing or license costs.
- For most implementations, sampling should **not** be used, as it reduces data accuracy and may distort metrics.

---

## How Media Tracking Works

Once initialized, the media pixel processes requests as follows:

1. **Check for existing pixel instance**

If a matching instance with the same Track ID exists, its configuration and user ID are reused.
2. **Create a new instance if necessary**

If no instance is found, the media pixel creates its own instance.

In this case, a third-party cookie is used to assign a user ID.
3. **No configuration = no tracking**

Without a valid configuration or pixel instance, no media requests are sent.

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.