Adobe Dynamic Tag Management (DTM) was a tool used by marketers to manage tags, and for collecting and distributing data across digital marketing systems. Adobe DTM is a legacy, and it will not receive feature updates. Adobe invites users to upgrade to Launch on the Adobe Experience Platform.
N/A
Optimizely Web Experimentation
Score 8.7 out of 10
N/A
Whether launching a first test or scaling a sophisticated experimentation program, Optimizely Web Experimentation aims to deliver the insights needed to craft high-performing digital experiences that drive engagement, increase conversions, and accelerate growth.
If you're on the Adobe stack at all, you absolutely need DTM. It will make your life infinitely easier. It's so simple to update your Adobe Analytics code and have version control, and when we implemented Adobe Target, it took literally less than 15 minutes for me to do. I also think it's significantly simpler than Google Tag Manager. I went through all manner of difficulty when implementing tags on that and have not had similar problems on DTM. If you're frequently placing pixels, it's a great tool that will speed their deployment. The only situation in which I think a tag manager is not appropriate is if you have a dev with too much time on their hands. Otherwise, get a TMS and get DTM.
I think it can serve the whole spectrum of experiences from people who are just getting used to web experimentation. It's really easy to pick up and use. If you're more experienced then it works well because it just gets out of the way and lets you really focus on the experimentation side of things. So yeah, strongly recommend. I think it is well suited both to small businesses and large enterprises as well. I think it's got a really low barrier to entry. It's very easy to integrate on your website and get results quickly. Likewise, if you are a big business, it's incrementally adoptable, so you can start out with one component of optimizing and you can build there and start to build in things like data CMS to augment experimentation as well. So it's got a really strong a pathway to grow your MarTech platform if you're a small company or a big company.
It is a rules based tag management system that allows the application of tracking pixels much easier than hard coding.
By placing 2 pieces of code on the top and bottom of each page of a website, we can create rules that track certain events and relay the information back to Adobe Media Optimizer and Google analytics.
It has simplified the coding process so one doesn't have to generate tons of gory javascript to deploy on each individual page to get tracking.
The Platform contains drag-and-drop editor options for creating variations, which ease the A/B tests process, as it does not require any coding or development resources.
Establishing it is so simple that even a non-technical person can do it perfectly.
It provides real-time results and analytics with robust dashboard access through which you can quickly analyze how different variations perform. With this, your team can easily make data-driven decisions Fastly.
I rated this question because at this stage, Optimizely does most everything we need so I don't foresee a need to migrate to a new tool. We have the infrastructure already in place and it is a sizeable lift to pivot to another tool with no guarantee that it will work as good or even better than Optimizely
Optimizely Web Experimentation's visual editor is handy for non-technical or quick iterative testing. When it comes to content changes it's as easy as going into wordpress, clicking around, and then seeing your changes live--what you see is what you get. The preview and approval process for sharing built experiments is also handy for sharing experiments across teams for QA purposes or otherwise.
I would rate Optimizely Web Experimentation's availability as a 10 out of 10. The software is reliable and does not experience any application errors or unplanned outages. Additionally, the customer service and technical support teams are always available to help with any issues or questions.
I would rate Optimizely Web Experimentation's performance as a 9 out of 10. Pages load quickly, reports are complete in a reasonable time frame, and the software does not slow down any other software or systems that it integrates with. Additionally, the customer service and technical support teams are always available to help with any issues or questions.
Although it is a newer product to Adobe, they seem to truly care about our challenges and are very proactive in making sure that we have the most knowledgeable support available in a timely manner.
They always are quick to respond, and are so friendly and helpful. They always answer the phone right away. And [they are] always willing to not only help you with your problem, but if you need ideas they have suggestions as well.
The tool itself is not very difficult to use so training was not very useful in my opinion. It did not also account for success events more complex than a click (which my company being ecommerce is looking to examine more than a mere click).
In retrospect: - I think I should have stressed more demo's / workshopping with the Optimizely team at the start. I felt too confident during demo stages, and when came time to actually start, I was a bit lost. (The answer is likely I should have had them on-hand for our first install.. they offered but I thought I was OK.) - Really getting an understanding / asking them prior to install of how to make it really work for checkout pages / one that uses dynamic content or user interaction to determine what the UI does. Could have saved some time by addressing this at the beginning, as some things we needed to create on our site for Optimizely to "use" as a trigger for the variation test. - Having a number of planned/hoped-for tests already in-hand before working with Optimizely team. Sharing those thoughts with them would likely have started conversations on additional things we needed to do to make them work (rather than figuring that out during the actual builds). Since I had development time available, I could have added more things to the baseline installation since my developers were already "looking under the hood" of the site.
Adobe DTM provides a more secure data analytics solution. It is customized and best used on large scale deployments of websites with pages 10,000+. The Adobe Analytics tool, once learned, is very easy to use and provides more robust, customized graphics and ability to export data to "securely" via FTP from the cloud to SQL database.
The ability to do A/B testing in Optimizely along with the associated statistical modelling and audience segmentation means it is a much better solution than using something like Google Analytics were a lot more effort is required to identify and isolate the specific data you need to confidently make changes
We can use it flexibly across lines of business and have it in use across two departments. We have different use cases and slightly different outcomes, but can unify our results based on impact to the bottom line. Finally, we can generate value from anywhere in the org for any stakeholders as needed.
The key factor is that my devs are not tied up with petty things like adding JS or advertising pixels. Simple work like that can be handled by me while they work on feature development.
Release cycle is much shorter when a dev is needed, say for a direct call rule that involves JS being written. We don't have to go through the normal release cycle and can do it on an ad hoc basis without all the rigmarole of a hot fix.
We're able to share definitive annualized revenue projections with our team, showing what would happen if we put a test into Production
Showing the results of a test on a new page or feature prior to full implementation on a site saves developer time (if a test proves the new element doesn't deliver a significant improvement.
Making a change via the WYSIWYG interface allows us to see multiple changes without developer intervention.
