> For the complete documentation index, see [llms.txt](https://developer.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.mediarithmics.io/user-points/user-identifiers/networks-ids/user-based-network-ids/utiq-martechpass.md).

# UTIQ martechpass

### Understand UTIQ identifiers

UTIQ proposes **two types of identifiers**:

* **UTIQ martechpass (mobile)**: refers to identifiers coming from **mobile network connections**
* **UTIQ martechpass (fixed)**: refers to identifiers coming from **internet box connections**

### Subscribe to UTIQ

To subscribe:

1. Go to **Navigator > Settings > Organisation > Compartments**.
2. In the **Shared user account compartments** section, click on **Manage subscriptions**.
3. Subscribe to:
   * **UTIQ martechpass (mobile)**
   * **UTIQ martechpass (fixed)**

{% hint style="warning" %}
If you manage **multiple datamarts**, ensure UTIQ is activated on each one.
{% endhint %}

{% hint style="warning" %}
You must **subscribe to each type individually**, depending on the identifiers you want to capture.\
The configuration steps are **the same** for both mobile and fixed identifiers.
{% endhint %}

<figure><img src="https://4196284719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMuoqM-5hJ5JY0WnAKL%2Fuploads%2FBF38CLYf6YLZCo1Vyq5k%2FCapture%20d%E2%80%99e%CC%81cran%202025-04-30%20a%CC%80%2013.37.27.png?alt=media&amp;token=fd79fb39-5218-4fe2-ac85-d700ca89edba" alt=""><figcaption></figcaption></figure>

### Activate UTIQ ingestion from your websites

UTIQ IDs can be ingested **natively** via the `user-event-tag` when users browse your websites.

To enable automatic ingestion:

1. Go to **Navigator > Settings > Datamart > Channels**.
2. Select the site where you want to activate UTIQ capture.
3. Under **JS Tag Configuration > Device Identification**, enable:
   * **UTIQ martechpass (mobile)**
   * **UTIQ martechpass (fixed)**
4. Repeat this process for each website where UTIQ ID capture is&#x20;

   required.

<figure><img src="https://4196284719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMuoqM-5hJ5JY0WnAKL%2Fuploads%2FtrSOZCuDpmosM78LeAUE%2F7293fe76b0cdde3e6889278a184affb2.png?alt=media&amp;token=e7bedf98-bcaa-4d00-bbf2-864106af220f" alt=""><figcaption></figcaption></figure>

### Storage and impact on user point merges

The storage method for UTIQ identifiers depends on their type, which directly impacts how UserPoint are merged:

* **UTIQ martechpass (mobile)**: stored as **UserAccount** identifiers in compartment 20. The identifier value is provided in the `user_account_id` property. These act as reconciliation keys, triggering a [**User Point merge**](https://userguides.mediarithmics.io/basics/key-concepts/what-is-a-user-point/user-point-merges) when the same identifier is seen across different sessions.

<pre class="language-json"><code class="lang-json">{
<strong>    "type": "USER_ACCOUNT",
</strong>    "user_account_id": "mt1-k4LwxGWEn-...........",
<strong>    "creation_ts": 1770466916312,
</strong>    "compartment_id": 20,
    "expiration_ts": 1778241090397
}
</code></pre>

* **UTIQ martechpass (fixed)**: stored as **UserProfile** in compartment 21. The identifier value is provided in the `$utiq_martechpass_fixed` property. These are anonymous profiles (no `user_account_id` and therefore not linked to any userAccount) and **do not trigger any UserPoint merge**.

```json
    {
        "$compartment_id": "21",
        "$last_modified_ts": 1774049259779,
        "$expiration_ts": 1779898252683,
        "$creation_ts": 1774049244368,
        "$utiq_martechpass_fixed": "mt2-k4LwxGWEn-..........."
    }
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.mediarithmics.io/user-points/user-identifiers/networks-ids/user-based-network-ids/utiq-martechpass.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.