Using Remote File Mapping to Test Tealium

Remote File Mapping 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 other tag manager) tagging implementation and are apprehensive about publishing to Production. Remote File Mapping allows you to do large scale testing with ease!

How to Use Remote File Mapping

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

From here you'll toggle on Remote File Mapping 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 Web Audit or Web 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 Web Audit or Web Journey is simulating the page load with the QA file and showing 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? Thanks for the feedback There was a problem submitting your feedback. Please try again later.