By default, extensions with preloader scope don't get executed when the profile (which they are defined in) is subloaded. Is it possible to have these extensions execute?
Also, in the publish settings there is a flag called "This profile can be subloaded". What does this flag do exactly?
I believe this is a known "bug" or limitation in the subloading logic. Subprofile will not process extensions with a preloader scope, nor will it process rules scoped to "All" (ie- there has to be a Load Rule declared). There are a couple of other limitations (nothing that can't be overcome with a little elbow grease):
* Caching -- it seems the subprofiles are cached a bit more heavily than loading it directly. To combat this, we have tried adding a cache bust parameter to the subloader template.
* Cannot access data/variables/load rules of the "parent" profile or other subloaded profiles. Each subprofile needs its own data set and rules.
The checkbox on the profile for "This profile can be subloaded" marks the subprofile as available to the Subloader Extension. I believe only the files with this designation can be subloaded (it will ignore other requests despite the load rules matching). In our company, we use a "main" profile for global (worldwide) scripts/tags, and have a subprofile for each geography to manage their own (so North America can load their own pixels without risk of ANZ getting their pixels by accident). Each subprofile has their own set of "managers" that can only access their profile.
Thanks for the informative reply Reid!
I've been informed that Tealium is currenty improving the subloading logic. Hopefully this overcomes these limitations, as subloading is very powerful!