Saving and Publishing

[#1]

Now that you have edited the configuration, it is important to understand how the save and publish process works and how to navigate your version history. This section explains the difference between Save and Save As, when to use publish environments, and how to view your version history.

In this article:

• Saving
• Publishing
• Versions and Revisions
• Save and Publish

Saving

When you add, edit, or delete an item in your configuration the interface displays orange visual cues to alert you of unsaved changes. If you logout or close your browser without saving, those changes are discarded.

The following visual cues indicate unsaved changes:

Sidebar
Individual Items
Save/Publish Button

Save/Publish Button

After you make changes the Save/Publish button becomes orange to indicate that you have unsaved changes. The drop-down displays a summary of the unsaved changes. Click an item to navigate to it.

To save your changes, click the Save/Publish button to display the save dialog.

Choose one of the following save methods:

• Save
  Changes are saved in the current version. You cannot revert to previous revisions of this version.
• Save As
  Creates a new version with a new title and preserves a copy of the previous version, allowing you to revert as needed.

We recommend using Save As in most cases for the following reasons:

• You have the ability to roll back your changes to a previous version.
• The title gives each version a unique and descriptive name.

It's a good idea to save often. If you're just making small, incremental changes, then choosing the Save option can help avoid clutter in your version history.

Publishing

When you save changes, you have the option to publish the changes to the Universal Tag (utag.js) by selecting a publish environment. Publish environments provide separate instances of the JavaScript file so that you can install one on your non-production environment and one on your live production site. This allows you to test changes before releasing them directly to your production site.

When the publish is completed, the files in the respective publish environments are regenerated to include your new configuration.

Publish Environments

There are three publish environments to support a proper release cycle: Dev, QA, and Prod. Each environment uses a separate utag.js file for your different website environments.

For example, use the file corresponding to the Prod environment on your production site:

https://tags.tiqcdn.com/utag/your_account/main/prod/utag.js

Use the file corresponding to the QA environment on your non-production sites:

https://tags.tiqcdn.com/utag/your_account/main/qa/utag.js

It typically takes a few minutes for the files to update on the CDN.

There three default publish environments are:

• Dev
  An environment for developing new tags and features.
• QA
  An environment for testing and validation.
• Prod
  The environment of your live production site. Changes published to Prod are public-facing.

Versions and Revisions

View save and publish history by clicking Client-Side Versions from the sidebar. Your account history is organized into versions and revisions.

Versions
version is created when you use the Save As option. A version has a name and contains one or more revisions. This allows you to revert back to a previous version.

Revisions
A revision is created within the current version when you use the Save option. This is is typically used for minor changes. You cannot revert back to a previous revision within a version.

Save and Publish

To continue, return to the save dialog or relaunch it by clicking the orange Save/Publish button, then follow these steps:

1. Select Save As.
2. Enter a new title for the version you are creating, for example "Getting Started".
3. Enter notes to describe your changes.
4. Click the QA publish target.
5. Click Save.

Congrats! You just completed the first save and publish of your Tealium iQ account. This is tag management in action!

The next step is to install the Tealium tag into your page code and verify that it's working.