---
title: "Client Tracker Administration"
slug: "client-tracker-administration"
status: "update"
updated: 2026-10-15T18:51:20Z
published: 2026-10-15T18:51:20Z
canonical: "docs.unqork.io/client-tracker-administration"
---

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

# Client Tracker Administration

To access Client Tracker Administration, navigate to **Administration** > **Environment** > **Client Tracker Administration**.

Client Tracker Administration lets Creators integrate with third-party client tracker systems to learn how end-users interact with their applications. Typical analytics tools report trends across many end-users. Client trackers let Creators analyze individual end-user sessions, including recordings of how an end-user interacted with an application. Client trackers run only in end-user applications.

Supported trackers include New Relic, Log Rocket, and Datadog RUM. Each environment supports one configuration per tracker type. Session recording depends on the tracker type:

- **Log Rocket** records end-user sessions.
- **Datadog RUM** records end-user sessions when **Record Session Replays?** is checked.
- **New Relic** monitors application performance and doesn't record sessions.

> [!CAUTION]
> Session replay can capture what end-users enter in an application. Creators are responsible for getting end-user consent and following applicable privacy rules before turning on a tracker.

> [!WARNING]
> Managing client trackers requires administrative permissions. Administrators needing access should contact their environment administrator.

![[docs-mockup:DocsAdminListCanvas] Administration panel overview](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261015_185115_20125a0a30f144b097afb9a01a44b63b.png?sv=2026-02-06&spr=https&st=2026-11-02T07%3A26%3A21Z&se=2026-11-02T08%3A26%3A21Z&sr=c&sp=r&sig=sNoD7Jq40t5bBmbx00mP%2FWsW2zOi95bdX9ty70VcSrs%3D)

## Tracker List

The tracker list displays all configured trackers in the environment. Each row displays the tracker name, application ID, and status.

| Column | Description |
| --- | --- |
| **Tracker** | The name of the analytics or monitoring service. |
| **Application ID** | The application identifier used to connect to the service. |
| **Status** | Whether the tracker is **Enabled** or **Disabled**. |
| **Actions** | Opens a menu with the tracker's **Edit** and **Delete** actions. |

### Tracker Actions

On any row, select ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261015_185115_29b3cd603baf4fc7b88aa0755260c93d.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A26%3A21Z&se=2026-11-02T08%3A26%3A21Z&sr=c&sp=r&sig=sNoD7Jq40t5bBmbx00mP%2FWsW2zOi95bdX9ty70VcSrs%3D) (**ellipsis**) to access the following:

| Action | Description |
| --- | --- |
| **Edit** | Opens a new page to update the tracker configuration. |
| **Delete** | Opens a modal to confirm removing the tracker configuration. Deleting a tracker can't be undone. |

## Adding a Tracker

Select **Create Tracker** to open a drop-down with the following tracker types:

- **New Relic**
- **Log Rocket**
- **Datadog RUM**

Selecting a tracker type opens a new page with its settings. Tracker types that are already configured are disabled in the drop-down. When every tracker type is configured, **Create Tracker** is disabled.

### Tracker Settings

Each tracker type has its own settings.

#### New Relic

| Setting | Description |
| --- | --- |
| **Account ID** | The New Relic account identifier. Required. |
| **Agent ID** | The New Relic browser agent identifier. Required. |
| **Application ID** | The New Relic application identifier. Required. |
| **License Key** | The New Relic license key. Required. |
| **Trust Key** | The New Relic trust key for cross-account access. Required. |
| **Is Enabled?** | When checked, this setting activates the tracker in end-user applications. Default: selected. |

#### Log Rocket

| Setting | Description |
| --- | --- |
| **Application ID** | The Log Rocket application identifier. Required. |
| **Capture** | When checked, this setting captures end-user IP addresses. Default: selected. |
| **Capture User** | When checked, this setting captures end-user identity information. Default: selected. |
| **Ingest Server** | The Log Rocket ingest server URL. Required. |
| **Is Enabled?** | When checked, this setting activates the tracker in end-user applications. Default: selected. |

> [!NOTE]
> The **Capture IP** and **Capture User** settings apply only to Log Rocket.

#### Datadog RUM

| Setting | Description |
| --- | --- |
| **Application ID** | The Datadog RUM application identifier. Required. |
| **Client Token** | The Datadog client token for authentication. Required. |
| **Tracker Site** | The Datadog site that receives tracker data. Required. Default: `datadoghq.com`. |
| **List of Allowed Tracing Origins** | The origins that use distributed tracing. Optional. |
| **Track Interactions?** | When checked, this setting tracks end-user interactions like clicks and taps. Default: cleared. |
| **Record Session Replays?** | When checked, this setting records end-user session replays. Default: cleared. |
| **Is Enabled?** | When checked, this setting activates the tracker in end-user applications. Default: selected. |

> [!NOTE]
> Datadog RUM sends the end-user's user ID, name, and email with each session. Datadog RUM has no setting to turn this off.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-10-15 | Restored the overview of what client trackers do, added end-user privacy guidance, and clarified which settings apply to each tracker. Updated the article to current style guidelines, converted settings tables to the administration format, and corrected the **Create Tracker** button label. |
| 2026-10-08 | Removed tracker descriptions — confirmed by engineering (Leo Fisher) that no APM changes shipped in 9.0. Descriptions were inaccurate and did not reflect the v1 docs. |
| — | Initial publication. |

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module.

A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.