Skip to main content
All CollectionsConfigurations
Using File Substitutions to Test Tealium
Using File Substitutions to Test Tealium
Luiza Gircoveanu avatar
Written by Luiza Gircoveanu
Updated over a week ago

File Substitutions allows you to answer the question: 'How would my data quality be affected IF I published my tag management changes to my production environment?' This can be useful when making changes to your Tealium (or another tag manager) tagging implementation and are apprehensive about publishing to Production. File Substitutions allow you to do large-scale testing with ease!

How to Use File Substitutions

In any Audit or Journey, you have the option to use File Substitutions. To enable File Substitutions you'll need to edit an existing Audit or Journey or create a new one for testing purposes. You'll find the File Substitutions settings in the Advanced Setup tab.

From here you'll toggle on File Substitutions then you'll need to identify your production and QA Tealium containers. You can identify the container by pasting the URL exactly or using regex to identify it. You can replace the production Tealium container by using the URL or uploading a TXT file.

How to Check the Results

You'll need to run your Audit or Journey again to see the results. Once it has run you'll see all the reports showing AS IF you had published your QA container in production. Your actual site does not change and your customers would not see any changes. Essentially the Audit or Journey is simulating the page load with the QA file and shows you what would happen if the file was published to production as is.

Make sure to check the Tag Presence report as well as the Variable Report to make sure your tags are firing correctly. To investigate the relationships of those tags you'll want to investigate individual pages and go to the Tag Initiator report in the top right corner of any page details.

Note: This can be used in combination with the other Tealium integrations. You can use the Tealium Trigger in QA profile to automatically run this analysis on your live site.

Did this answer your question?