Tag Composer is the solution allowing you to set up and follow the tags used on your sites and applications through its configurations.
A configuration has a name and a description, as well as its own programmatic language. But it also and mainly has a version, and the possibility to update its content and settings. It then allows a configuration deployment (CDN or download), on the sites the configuration was built for.
Tag Composer's homepage allows you to list all configurations available within your organisation.
Several status may require your attention:
- Configuration has been updated but has not been deployed in its latest version:
You will only need to open the configuration and deploy. A reminder on the confirmation page will give you an easier access to it:
- Configuration doesn't use the latest available version of its platform library:
You will be invited to open the configuration, and approve the library update:
You will then be asked to confirm the configuration, to which Tag Composer will automatically label as a major update.
Configuration follow their modifications and latest deployments through a versionning system.
When creating a configuration, it is set to version 0.0. To each configuration modification, when saving, you will be asked to specify:
- A message for the update, to help following the modifications
- A description, if details are to be specified
- An update type, minor or major, to help providing an easier followup on updates
You may have had former configurations generated by Tag Composer previous version. To help you switch from your former settings, the interface allows you to import configurations generated on Tag Composer former version, to get its settings back.
Activity views (global or per configuration) help you see different actions (configuration edition or deployment) set on each configuration of your organisation.
Creating a configuration goes through a step by step process.
The first one will ask you to specify the name and description for your configuration.
Second step is picking the environment on which the configuration will be used, to get the most adapted library.
The the following screen will give you the ability to pick plugins to add to the configuration. Some will be ticked by default (the most used and expected in a standard tagging).
The configuration main page gets all information attached to it. It also provides its edition through a dedication button, to help you pick different plugins or change some settings for example.
Sites view shows all sites listed under a configuration, to quickly see on which sites the configuration has been deployed and in which version it has been deployed.
Please note that a site can be listed in various configurations at the same time. Meaning the configuration may not be the one currently being used on the site.
A configuration deployment is fully guided.
First step is picking sites on which the configuration must be deployed. By default, selected sites for the previous deployment will be selected again and held at the top of the list.
Then, all specific configurations to each site will be asked. They may vary depending on the library being used in the current configuration.
The following screen shows you the ongoing deployment process while generating the files.
Eventually, a deployment summary, with a download button for each file, and a tagging example provided.
To initiate the tag and to give it the value within the dedicated parameters sent to our servers to be processed for each analysis, we provide a specific tagging which is detailed in the dedicated documentation: https://developers.atinternet-solutions.com