I’ve noticed that I can use variables from the meta site in the real site container although autocomplete is not working. The article doesn’t mention this explicitly, but can you confirm that I can use it this way and that there is no need to duplicate variables in a site container for use in site tags?
The tag trees for both metasite and site are merged. So, effectively, variables should work. Since it’s the first version of this feature, there are missing parts. I presume that you see valid use cases for using variables like that. I’ll fill in feature request to add autocomplete in this case.
variables that exist only on the meta site can’t be used in the triggers of the site
It may work. However, there is currently no autocomplete. It is the first version of the mechanism, and we plan to modify it. As a result, triggers in sites relying on variables from meta sites may eventually stop working.
triggers that exist only on the meta site can’t be used in the tags of the site
Can you provide a specific use case where this can be useful? Why is copying a trigger from meta site to site not good enough?
it’s not clear what happens if the same variable exist in both the site and the meta site => from what I can see is that the tag from the site level has priority (=good)
Yes, if a variable exists in both site and meta site, the one in the site takes precedence. We will update the description on Help Center to make it clear.
Do you need a more complex mechanism that would allow you to control the order of firing all tags in both site and meta site and mix them?