Client Tracker Administration

Overview

Client Tracker Administration lets you integrate with third-party client tracker systems get more insight into how end-users 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. interact with your applications. Client trackers give more insight than typical analytic tools, letting you analyze individual end-user sessions. Instead of reading reports on end-user trends, you can view a recording describing how your end-user interacted with your website. That said, end-users must give consent before you can track their sessions.

You can use this data in the following ways:

Viewing how end-users interact with your website so you can improve the end-user experience.
Determining exactly what a end-user did when experiencing a error so you can fix it correctly.
Determining specific areas of improvement on your website.

Client Tracker Administration lets you connect a third-party client tracker to your application. Unqork supports New Relic, LogRocket, and Datadog RUM. Client tracker integrations are configured for your entire Unqork environment. That said, you can configure the integration for each module if the data must be sent to the environment-level integration.

Client Administration lets you control which application and specific modules should track end-user activity. But, you can only configure one DataDog, LogRocket, or New Relic integration in your environment.

Accessing Client Tracker Administration

To access the Client Tracker Administration page:

At the top right of the Unqork Designer Platform, click Settings ▾.

Click .

Under Environment, select Client Tracker Administration.

Adding a New Client Tracker

When accessing the Client Tracker Administration page for the first time, you'll see no configured client trackers. Client Tracker Administration lets you configure three client trackers, one for each supported third-party system.

To add a client tracker:

At the top right, click Add New Tracker.

From the Tracker drop-down, select your third-party system.

Each client tracker requires unique configuration. The following sections describe the settings you must configure to create it. When you have finished configuring your client tracker, click Done.

All fields are required to configure your client trackers.

About the Datadog RUM Settings

Setting	Description
Application ID	Your unique Datadog identifier, so you can connect your Datadog account to your application.
Client Token	Used to send events and logs from your end-user.
Tracker Site	If the Tracker Site field is left blank, when saved it defaults to datadoghq.com. This URL supports most users in a us1 region. If you belong to a different region, view the following documentation to configure the correct Tracker Site URL: https://docs.datadoghq.com/getting_started/site/#access-the-datadog-site. If you edit the Tracker Site filed, remove the URL, and save it, datadoghq.com no longer becomes default. Doing so will break the configuration.
List of Allowed Tracing Origins	Enter your Datadog tracing libraries to link requests from your Unqork applications to their corresponding back-end traces. In Datadog, you can view your full front-end and back-end data through one lens. To learn more about connecting RUM and traces, view the following documentation: https://docs.datadoghq.com/real_user_monitoring/platform/connect_rum_and_traces/?tab=browserrum. Further configuration might be needed by adding your Datadog URLs to the available Express Content Security Policy (CSP) fields in Environment Administration.
(OFF) Track Interactions?	Records your end-users' clicks when interacting with your application. You can view the details of each interaction in your Datadog account. By default, this toggle is set to (OFF).
(OFF) Record Session Replays?	Records your end-users' sessions when they interact with your application. You can view each session replay in your Datadog account. By default, this toggle is set to (OFF).
(ON) Is Enabled?	When set to (ON), the tracker tracks end-users. Turn this setting (OFF) if you do not want to track users. Your tracker still stores in Client Tracker Administration. By default, this toggle is set to (ON).

The Datadog settings are accurate as of the date this article was published. Always refer to Datadog RUM's internal documentation for the most recent information.

About the New Relic Settings

Setting	Description
Account ID	Your unique New Relic identifier, so you can connect your New Relic account to your application.
Agent ID	Your New Relic browser version number. Enables browser monitoring for your end-users.
Application ID	Your New Relic Browser Application ID. Use this along with the Agent ID to enable browser monitoring for your end-users.
License Key	Your New Relic License Key that's generated when you create a new app in New Relic.
Trust Key	Enter your Account ID again. In New Relic, the Trusted Account ID and Account ID are the same.
(ON) Is Enabled?	When set to (ON), the tracker tracks end-users. Turn this setting (OFF) if you do not want to track users. Your tracker still stores in Client Tracker Administration. By default, this toggle is set to (ON).

The New Relic settings are accurate as of the date this article was published. Always refer to New Relic's documentation for the most recent information.

About the LogRocket Settings

Setting	Description
Application ID	Your unique LogRocket identifier, so you can connect your LogRocket account to your application.
(ON) Capture IP	Records the IP address of your end-user in LogRocket. It helps you locate end-user sessions in your LogRocket account. By default, this toggle is set to (ON).
(ON) Capture User	Records your end-users' name, email, and ID in LogRocket. It helps you locate end-user sessions in your LogRocket account. By default, this toggle is set to (ON).
(ON) Is Enabled?	When set to (ON), the tracker tracks end-users. Turn this setting (OFF) if you do not want to track users. Your tracker still stores in Client Tracker Administration. By default, this toggle is set to (ON).
Ingest Server	Bypasses Unqork's standard content security policies to ensure sessions record. You can copy and paste LogRocket's server path into this field : Content Security Policy: child-src 'self' blob:; worker-src 'self' blob:; script-src 'self' https://cdn.logrocket.io https://cdn.lr-ingest.io https://cdn.lr-in.com; connect-src https://.logrocket.io https://.lr-ingest.io https://.logrocket.com https://.lr-in.com

The LogRocket settings are accurate as of the date this article was published. Always refer to LogRocket's documentation for the most recent information.

Editing a Client Tracker

Client Tracker Administration also lets you edit your client track configurations.

To edit a client tracker:

For the client tracker you want to edit, click Edit.

Make any changes to the fields or toggles as needed.

Click Done.

Removing a Client Tracker

When a client tracker is no longer needed, you can remove it from Client Tracker Administration.

You can also set Is Enabled? to (OFF) to disable the client tracker instead of removing it.

To remove a client tracker:

For the client tracker you want to edit, click Remove.

In the confirmation modal A modal is a window that appears on top of the content you are currently viewing., click Remove.