A Tracker is an abstract object that holds a configuration. Including the properties of an individual network or application required for its basic setup. This way you have a single entry point to adjust a configuration for multiple tags in your JTM setup.

Tracker Configuration

A Tracker defines properties of a single service that you need to interact with. Services in this regard are partner networks and data bases such as Facebook, Google Ads or Google Analytics. Further a Tracker can also be a configuration to a custom endpoint that your JTM server needs to interact with.

Tracker Creation Process

In your JTM account you need to navigate to the Server Tag Manager area. Here the Tracker objects are managed. You can add further Trackers. Any network or partner (Facebook, Google Ads, Google Analytics, etc.) configuration can be used multiple times. In cases that you need to implement multiple different data sources (Pixel IDs) with Facebook, or any other network.

Tracker objects have properties that you can access in all the tags that are associated with them. This properties are used for global configuration values, such as a property or account ID. In context of Google Analytics this is the Measurement ID (GA4) or the Property ID (UA-ID for Universal Analytics). Further you can define more custom parameters that are required as a global constant for your configuration.

The values of a Tracker property are assigned per account and can hold different values for each environment (live, stage). This way you can create lookup values for each individual configuration.

Tracker Tag Creation

When a Tracker is saved for the first time Jentis will ask you if you want to create automatically relevant tags for them. These tag sets are designed to work out of the box with default frontend tracking configuration, that follow the general Jentis data model on pageview, event and product tracking.