Tag Management Systems provide vastly simplified means to update site tags and speed the deployment thereof. But what about getting the TMS deployed in the first place so that you can leverage these values?
Adobe TagManager is the quickest, easiest Tag Management System to deploy. We’ve made it so by leveraging our existing SiteCatalyst tags present on many, many pages throughout the web. Those tags are valuable in a number of ways:
- SiteCatalyst tags are capturing a superset of data as compared to any other tags on sites; the amount of granular conversion data shared is immense.
- They have prebuilt extension points (plugins and modules) for data integration with other systems and custom configuration to suit your business needs.
- They are already in place.
I’ve explained this in previous blog posts, but I think it’s worth highlighting again. The means by which we make it possible to turn your SiteCatalyst tag into a container is through what is historically referred to the s_code.js file. This is the measurement library where you configured your SiteCatalyst implementation. It contains plugins, modules, mappings, and other areas of customization. None of that is lost, you simply move it to the TagManager container. Then you replace your s_code.js file with a loader to point to the container we host. Finis! You can manage your measurement configuration and any other tags you want through Adobe TagManager’s UI and deploy it through our 3-stage deployment process without waiting on a full IT build and release cycle!
So, if you’ve already got the data you want exposed to your tag, that tag can become a tag container that orchestrates the firing of all tags on your site… and it can be enabled in a few minutes without deploying a new tag to each page on your site, why not do it?