-
Notifications
You must be signed in to change notification settings - Fork 4
Unable to export Tags with type: Universal Analytics #3
Comments
Hi, to come around this, you can take a look at: #2 (comment) Additionally, if you would like to see this feature, you can consider a donation. |
we can transfer the whole container, Google provided this feature. |
Thank you vilaskumkar, very useful, I will update the documentation to reflect this. |
Thanks maschek and vilaskumkar, the new Google feature is exactly what I've been waiting for. Also, the new beta test of GTM looks very well put together with no need for implementing listeners.seems, like a pretty well put all-round package now! |
The new Google feature is not what we're looking for -- we don't want to export/import a whole container, only rules and tags. Looking at #2 (comment), changing the rule from Universal Analytics to Custom HTML is not an option, since we have some 40 such rules for different domains. I would like to be able to copy the rules and tags I have set up for one domain to another, all within the same container tag. I figure I can export, change the appropriate fields to new names and domains in my text editor, then import. How much work is it to get this to work with Universal Analytics? I'm familiar with web development so if you point me in the right direction I might be able to add UA tag support. What do I need to keep in mind when exporting and importing? The blocks of code that handle export/import for other tags don't seem too big - where did you get info on which properties to get and set? |
Hi @mikalmadsen, The problem with the analytics tag type is that it has a lot of options. There is no info on which properties to get and set, you have to experiment and inspect the requests in your browser debugger. This makes it long to develop. Since the new UI is coming in June, probably it is not worth the effort right now to develop this. |
Please could you offer support for tags for Universal Analytics. Much needed feature please!
The text was updated successfully, but these errors were encountered: