Migrating to a new CMS (Content Management System) can be a huge undertaking, compounded by ensuring that your data collection doesn't miss a beat. The purpose of this article is to provide a starting point of the questions to ask in preparation for migrating your Tealium instance into a new CMS. It's important to note that every situation will be different and you may want to consider a reimplementation.

1. Is there a Tealium Integration/Plugin for the CMS being migrated into?

  • If yes, does the integration support the latest version of that CMS? If it does not, is that ok?
  • If choosing not to use the integration or there is none, is the JavaScript implementation of Tealium possible with the placement of the code snippet within the HTML of the website?
    See https://docs.tealium.com/platforms/javascript/

2. Is utag.js running the latest version? If not, is there a plan to upgrade?

  • Migrating can be a great opportunity to take advantage of upgrading utag.js, but depending on which version is currently installed, some functionality may have changed. Make sure to review the release notes and update your tracking accordingly. See https://docs.tealium.com/platforms/javascript/release-notes/

3. Ensure the data layer is consistent across the entire website, especially important pages, like the checkout funnel.

  • Changing variable names or data types will have an adverse effect on tracking, especially with server side products. Make sure the utag_data object is consistent during the migration process.
  • If changing the utag_data object is necessary, make sure to follow any changes downstream, such as variable names in iQ and attribute names in EventStream and AudienceStream.

4. Review all events.

  • Determine if any jQuery extensions or JavaScript extensions would be better implemented via the source code. If so, remove/update the corresponding extensions in TiQ.
  • Conversely, make sure that all events within the source code are accounted for during migration. There have been many instances of clients forgetting to include an event and while a jQuery/JavaScript extension can be implemented, in some cases, the original data being populated will not be accessible.
  • Think of an Add to Cart event. Tracking Add to Cart events are better within the source code, because the product variables can be populated. A jQuery onHandler Extension, will not be able to populate product variables, unless they can be scraped from the website, and sometimes, they are not available, leading to lost data.

5. Check all tags.

6. Check all extensions

  • jQuery onHandler extensions: Since these rely on HTML elements, any missing IDs, class names, attributes, etc., will cause errors in a website and a loss of tracking.
  • JavaScript extensions: Like the jQuery extension, the code within these extensions may be relying on elements that exist on the page. Ensure that the code within these extensions will not be affected by the migration.
  • Check remaining extensions: Set Data Values extensions, for example, have an option to inject JavaScript into a variable. Check each extension for any JavaScript that is being used to populate a variable.

7. Check Consent Manager.

  • If utilizing the Consent Manager feature, ensure that it's appearance and functionality will transfer over to the new CMS. Check any JavaScript and HTML/CSS elements that are being used.

8. Consider a Reimplementation.

  • This can be an opportunity to migrate all tracking into Tealium to leverage the full potential of the CDH.
  • Other benefits can include:
    • Upgrading to the latest version of utag.js.
    • Upgrading vendor tags.
  • You may also choose to migrate using a new Tealium profile, copying the existing, active, profile to a new one. This would allow the current profile to be maintained while the new configuration and site are being developed. 
    • One drawback to this is the effort required to apply any updates made to the original profile within the new profile. 


Version history
Last update:
‎01-20-2021 10:34 AM
Updated by: