The sanest way to manage tags is really quite simple: use google tag manager or Opentag from Qubit. Give any third party partner the ability to write tags and r

The sanest way to manage tags is really quite simple: use google tag manager or Opentag from Qubit. Give any third party partner the ability to write tags and rules. Do NOT give them Deploy access. Then the dev team gets to use the sandbox debugger to test and profile, and then publish. Because GTM has immutable snapshots of config, rollback is painless. We were working with an agency serving a large software company in the Seattle area. They have a site dedicated to competing with other companies that make productivity software, among those a company that also has a search engine. We outlined the above workflow and successfully deployed Google Tag Manager on the site in what may be my career's biggest -#ironywin to date. Marketers have highly complex rules for when customer events turn into when tags should fire. This is best left to them as rules and platforms are always in flux. We even sometimes use GTM variables to split test tags from different inventory sources. I would love the future to allow for tag management to be done on a seperate web server that uses a single proxy tag that sends event streams to a service that routes the event data to all 3 party tracking. No document writes, one tag to load. Anybody know if that is or isn't possible?