Versions and Preview
  • 13 Dec 2022
  • 2 Minutes to read
  • Contributors
  • Dark

Versions and Preview

  • Dark

Article Summary

In the Publish section of your JENTIS Tag Manager you have the option to control the versions, preview, see change logs and publish the latest updates of your configuration to your website.


Tag Management is the orchestration of all data streams using tags, variables and triggers to solve your data needs.

Each JENTIS Tag Manager configuration of your settings comes packed as a version. So you can edit and change your settings in a new version and have that separated into different packages from what is published to productive or staging systems.

Here you can find more details on the JENTIS account and container structure, including environments of containers: JENTIS Accounts and Containers

A list of all your versions you will find in the Publish section. Each configuration version can be in one of three states:

  1. current edit (this one contains all the changes you did recently but yet not published)
  2. published to live, stage or both
  3. legacy (these can not be edited any more, but you can publish those to rollback a published version)

You can also inspect a log of all changes in a version.

Preview Monitor (Inspector)

With server side tracking architecture a configuration preview is key. As it makes transparent what is not visible to the website visitor. The communication stream from user to any service provider (tools) is in your hand. The preview monitor enables you to preview and debug all data streams.

To open the preview monitor you must navigate to the Publish section that displays all versions.

The inspector is a tool that displays all streams of the server-to-server communication. That is when a tags trigger is activated and data is transmitted to a configured data receiver (Tools).

In the inspector tab (web browser) you can click on the “play”-icon to open your website in preview-mode. This query parameters will instruct the JTM to display more information for debugging.

There are two layers to inspect the information:

  • frontend (in the browsers developer tools you can find information in the JS console)
  • backend (here the server to server communication is displayed)

In the inspector window you will see the incoming State events and what data was then send to a tool, following a tag configuration.

The following example displays a data stream to a Google Analytics tools pageview-tag. It consists of the payload and HTTP parameters so you can check if the configuration meets your requirements.


When your preview results look just as required then its the right time to create and publish a new version.

You can select to publish your environment to staging, production or both. When publishing to live systems that will automatically create a new “current edit”-version for the next release cycle.

In the publish-options you can also add a commit message.

Was this article helpful?

What's Next