Highlighted

What is the best pratice for pointing dev version to one SiteCatalyst report suite and prod version to another?

Silver Contributor
Silver Contributor
Our client wants to send to a specific report suite when utag is linked with the dev environment, and another report suite when utag is linked on prod. For example: [...]/dev/utag.js -> RS A [...]/prod/utag.js -> RS B what is the best path to follow to achieve this, avoiding to change values every time when publishing to different environments? Is there a UDO variables that indicates what envinronment is been called? Thanks, Alessandro
2 REPLIES 2
Highlighted

What is the best pratice for pointing dev version to one SiteCatalyst report suite and prod version to another?

Employee Emeritus

Salve Alessandro,

 

this is a good idea and we support it. If you have utag version 4.36 or above you can access the environment name by creating a data source called 'ut.env' (you can check or upgrade your utag version by following this post https://community.tealiumiq.com/t5/2-Tealium-iQ-Documentation/How-do-I-upgrade-to-the-latest-utag-js... If you are on older version then you can create a 'set data values' extension and set a new data source to 'utag.cfg.path.split('/')[6];' using javascript: http://note.io/1znrWgi Then, you could create a new data source called 'sc_report_suite_id' and map that to the report suite in SiteCatalyst (see mappings toolbox). Once you have done that, use a 'lookup' extension to set the correct value for the relevant environment: http://note.io/1BlKDa3 Hope this helps!

 

Thanks,

 

Roshan

Highlighted

What is the best pratice for pointing dev version to one SiteCatalyst report suite and prod version to another?

Silver Contributor
Silver Contributor
Perfect, we are on utag 4.28 so we'll go with the split. Thanks! Alessandro