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?
... View more