It has been a wild few weeks. We publicly released our beta about 2 weeks ago and have gotten some fantastic feedback – some simple and some more challenging. I’ve personally thanked everyone who has given feedback so far, but want to extend a thanks to those who are still actively using the tool. We’ve taken many steps to resolve any issues you may have encountered when using the tool. I’m happy to say we’re at a pretty stable point. For those hold-outs who disabled Tagtician because it was behaving funky – give it another shot and let us know if something still looks off. This is an actual beta, not one of those “here’s a full release but we’re going to call it a beta” type of things. If you aren’t already using Tagtician as your tag management companion, then
you’re crazy let us know what we’re missing. I respond to every suggestion, criticism, and love letter.
Let’s talk about exporting. I’ve been waiting for this feature for SO long… so I built it. As of today (v0.84), you can export your entire DTM library to CSV. We even have a video explaining exactly how it works. I want to start with the first question we ask ourselves before we release a feature. Why would someone want to export their DTM library?
As a consultant, I want to…
- Get a quick snapshot of my new client’s implementation
- Quickly determine the scale of an implementation
- Make notes
- Send tangible documentation to colleagues
- Store the current state of an implementation
As an analyst, I want to…
- Own a local copy of my entire implementation (like an SDR)
- Have the flexibility to switch tag management systems
- Reference rules on-the-fly
- Make notes and do the stuff the consultant wants to do…
Think of this as an insurance plan for your implementation. Alright, so what does it look like? Clicking on the button below will trigger the CSV download of all of the rules (or Data Elements) you see on the screen:
When you open the file, this is what it looks like:
We still have some formatting work to do… and it could probably use information like site name. However, we think this is a sufficient starting point. We hope you love it! If you don’t already have it installed, grab Tagtician off of the Chrome store.
Love this tool already, it’s just what we’ve been looking for =). Is there any chance of an option for Tagtician to look for custom implementation of the DTM header and footer script? For example, our header tag is standard, but our footer has been adapted (by our Devs) to only show when a particular quote and buy journey is present. Because our devs have tweaked the code Tagtician thinks DTM isn’t present – but it is! If there was an option for me to paste in the code we used as the header or footer then that would be awesome!
Thanks for the feedback, Rik! I’d love to do that. Did you change the physical object name to something other than _satellite? I think I may have an idea of how to approach it.
Pingback: DTM-to-Launch Migration Series #1: Options and Considerations - 33 Sticks
Pingback: DTM-to-Launch Migration Series #3: The Migration Process - 33 Sticks
Pingback: DTM-to-Launch Migration Series #1: Options and Considerations | Digital Data Tactics
Pingback: DTM-to-Launch Migration Series #3: The Migration Process | Digital Data Tactics