2 Tealium profiles for one site?

[manish_dixit]

Can we use 2 Tealium profiles for one site? Current Situation: We have client site which contains â contentâ , â videosâ and â shopâ section pages and Tealium/CoreMetrics is also there on current live website. We are re-designing â shopâ section pages with new analytics design, other sections of website and analytics design will remain same. We have created a new Tealium profile to manage/track â shopâ section pages and configure new analytics design in Tealium for â shopâ section pages. Our Approach: For â contentâ , â videoâ pages: use old Tealium profile (/oldtealium/utag.js) For â Shopâ section: use new Tealium profile (/newtealium/utag.js) Note: in both Tealium profiles, using same CoreMetrics client id/profile. Need inputs if the approach is correct and if this will not make any impact on data session when a user will move from â contentâ to â shopâ section pages as we have 2 different profiles on both section but same CoreMetrics client id/profile configured in Tealium. Thanks in Advance.

[james_hartley]

Hey Manish, I would look to the Tealium folks for the final answer on this but I think this depends on the complexity of your tag implementation and web site. I would think you could accomplish this with 1 profile and 2 tags. Trigger 1 tag for your "content" and "video" sections and a separate tag for your "shop" section. You could accomplish this through load rules as well as scope extensions and map data sources accordingly. This would leave you with a single source of maintenance within within Tealium IQ as well as a cleaner implementation. I have accomplished this with the Site Catalyst Tag - not sure if this approach is in line with CoreMetrics. Hope this helps. Cheers!

[nicholas_earl]

What are you looking to gain by putting a separate Tealium profile up for a subset of the site's pages? If you just need to have separate metadata for "shop" vs the rest of the site (variable values, events, etc) and want to use the same Coremetrics profile/client ID, you should generally be able to modify the analytics implementation for the new "shop" pages independently from the "content" and "videos" sections by using conditional logic in your extensions. For example in a "Set Data Values" extension, you can add a condition like "if URL contains "/shop" or domain equals "shop.example.com". Since you want to use the same Coremetrics profile across both "shop" and the rest of the site, that approach would be easier than having two separate Tealium profiles. If you need to configure the actual Coremetrics tag differently for "shop" vs the rest of the site (ie, different client ID, tag version, collection domain, etc) you can use Jim's approach above . Hope that helps!

[jared_hislop · Accepted solution]

Hey Manish, I would have to agree with Jim. Using two profiles will require you to re-code your pages with the new utag.js file. This could be a task on your developer's side to make sure all the necessary pages have the correct utag.js file loading. Than as you begin to transition the content section of the site to the new analytics design you'll have to recode those pages to use the new utag.js file as well. Using two tags and Load Rules, you can specify with tag loads on the specific section of the site. Since both tags will be configured with the same Client ID, Cookie Domain, etc this shouldn't cause any sort of drop off in your reporting. With that said, you may still continue with your approach if you'd like to start with a new/clean profile for your new site. I'm not sure I would call this a best practice, but it can still be done this way. Since the tags will be configured the same and be using the same cookies the user data should persist from one section to another without any problems. Hope this helps.