Tealium Learning Center

arjan_van_wijk · ‎12-02-2014

That was indeed what I was doing (naming them TEMPLATE is a nice addition!) But going to all that trouble to set values for mapped data sources that normally can not be included in libraries for tags sounds a bit to much for me :D But thank you very much for throwing all the options out on the table, it's best to make a decision when all the options are known to you :)u :)

arjan_van_wijk · ‎12-02-2014

Hi Seth, thanks for responding. I know by duplicating it I still have to do changes manually in every profile, but that is something I will have to do either way :) I just want to have a place where I can put and easily include extensions that I might need several times. At the moment there can be several weeks or months between new site releases (creation of new profiles), so it's quite easy to forget which extensions you manually have to create for a profile to make a certain tag work. That's why including them in the tag library, but mark them as 'template' (disabling them, maybe also adding a TEMPLATE tag or name) will let you know what extensions to configure. The 'update once, propagate everywhere' aspect of the library is less important in this use case, because most of the values you enter are custom to a profile, so it's mostly for the 'template' aspect. I hope this makes sense :) I will also link this and the other issue to my Account Manager so they know about it.

arjan_van_wijk · ‎12-01-2014

Hi Roshan, Thank you, I was indeed aware of those solutions to configure something. I've already used the same solution to configure our GA tags profile ID based on the environment. But that in itself raises the same problem, where to put that configuration code so you don't have to create that extension every time. For reuse-purposes you want to put it in a library, but then it's not editable in a profile. See that exact question I posted: https://community.tealiumiq.com/t5/Tealium-iQ/Disable-extension-in-library/m-p/8439#M2792 I hope this stuff is on the todo-list (or it will be now :)) to make this easier in the future :)

arjan_van_wijk · ‎12-01-2014

Hi Roshan, Thank you for the extensive explanation! This is indeed a valid third option, but sadly enough still a compromise with its own downsides. As new profiles and tags are created along the way there is no way to determine if a tag will be used in one or multiple profiles, so it's hard to decide where to place them; in an own library of in the generic library. To correctly make use of the Data Sources in the tags you are almost required to put all of the tags in the general library, but that will in turn bloat all the profiles with tags they are not using (with tag-related data sources and extensions). I think I will stick with option 1 at the moment, as it is the least amount of work and overhead, while still keeping all tag-libraries separated. But other might choose other options based on their use cases and personal opinion.

arjan_van_wijk · ‎11-27-2014

I guess I can partly answer my own question, as the disabled library extension now correctly shows up disabled in the profile. I think it was not published correctly before for some reason, but now it works fine. I would still like to to know if this is the best way to use extensions in libraries which have values that need to be changed in the profile where it is included.

arjan_van_wijk · ‎11-27-2014

I'm having some issues setting up our project spanning over multiple sites with multiple optional libraries. We have a website being released in multiple markets. Each site has its own Tealium Profile. Each profile can have one or multiple tags and extensions (e.g. SiteCatalyst, Google Analytics, Webtrekk, etc). We have one overall Data Layer that's connected with our website code. These variables are used in all different tags and extensions. So we created a library for all our generic Data Sources that gets included in all our site profiles, so we can keep track of them in one place. We also created a library for each individual Tracking Tag. Here we added the tag with default configuration and mappings, together with the related extensions. However, the tags' mapped data sources and extensions need access to the Data Sources defined in the other library. But it cannot access them. As far as I can see there are two options: 1. Copy all (needed) data sources in all tag-libraries that need them. I don't like this solution because now the data sources are duplicated all over different libraries, and it duplicates the amount of work needed when we introduce new data sources. 2. Don't use libraries for tags/extensions and configure them in the site profile where you can access the Data Sources from the included library. I don't like this either because it you cannot use the benefit of pre-configured tags and extensions, so you need to copy them over from a previous site, or write them down somewhere else. Also, updates normally done in a library that propagate to all profiles, now have to be done manually in every profile for the same tag, which involves a lot of work. It would be better of a library could import another library that it needs to make use of, but that doesn't seem possible right now. Am I missing something here, or is this indeed not possible in a normal way without reverting to a cumbersome workaround?

arjan_van_wijk · ‎11-27-2014

I have created a Google Analytics profile library that contain Data Layer variables, the GA tag, and some related extensions. One of the extensions has some variables in them that must be filled in from the containing site profile (e.g. a lookup table with GA accounts). Because you cannot change any value in library extensions, I can duplicate this extension and only replace the default values from the library version. Now both versions of the extension (library & duplicated) are enabled, which is not good. So I want to disable the extension in the library (indicating that it will be used for duplicating). However, when I do this, it still looks enabled in the site itself. How does this work? Or is there a better way to achieve this (without creating even more variables and extensions)?

Date Registered	‎09-22-2015 07:37 PM
Date Last Visited	‎01-30-2019 04:14 AM
Total Messages Posted	7

Tealium Learning Center

That was indeed what I was doing (naming them TEMP...

Hi Seth, thanks for responding. I know by duplicat...

Hi Roshan, Thank you, I was indeed aware of those ...

Hi Roshan, Thank you for the extensive explanation...

I guess I can partly answer my own question, as th...

How to correctly setup Library Architecture?

Disable extension in library?

Products

Company