Streamline implementations and empower non-technical employees with Ensighten 2.0
Updated December 09, 2014

Streamline implementations and empower non-technical employees with Ensighten 2.0

Adam Waddington | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Software Version

Manage 2.0

Modules Used

  • SiteCatalyst

Overall Satisfaction with Ensighten

Our company transitioned to Ensighten Manage 2.0 fairly recently in an effort to streamline the process of implementing new tracking pixels. The key users in our situation are the marketing specialists and analytsts, who will be using the tool to manage tracking deployments for a variety of partners. Although we are still in the early stages, the obvious benefits of using tag management technology in the long term will include ease of implementations for non-technical employees, streamlined removal and maintenance of existing code deployments, and the ability to work with the consultants from Ensighten to mitigate risk of impact on user experience. Furthermore, it will allow both large and small-scale modifications with targeted scope without the need to slow the backlog of development efforts on the client-side, meaning our internal resources can focus on improving the website while marketing and non-technical folks handle the portfolio of partners.
  • Reduces reliance on IT and developers to add, remove, or manage code
  • Enables non-technical users to actively manage their own tracking deployments
  • Ensighten support is particularly helpful in implementation projects
  • Fast, safe removal of code if issues to arise
  • Could benefit from more details change logging
  • Would like to see better filtering/search approaches for deployments (ie - search in code, etc.)
  • Deployments don't publish immediately, so any reduction in time here would be an improvement
  • Allows for a single point-of-reference of all tracking deployments as opposed to having multiple teams editing the site at once
  • Simplified the code by placing a bootstrap rather than multiple lines for each pixel
  • In some cases negatively impacted page load time
  • Does require training to understand how to use the UI/Technology
  • Non-developers feel more involves/connected the site itself
  • Encourages relationships across the organization because the deployments effect multiple team, as opposed to being silo'd as 'devs' or 'analysts' or 'managers'
I have no means for comparison except to say that Manage 2.0 has many improvements from Manage 1.0. The UI improvements alone make it a good switch, and the ability to use the apps to templatize deployments is a great feature.
For the volume of tracking pixels that we plan to implement it only makes sense for us to continue. At this point, development is benefiting significantly from not being bogged down with writing tracking pixel code and the marketing team(s) enjoy being able to stay connected to their tool deployments. As the portfolio of tracking methods increases, the usage of Ensighten will increase with it.
Ensighten, as with any tag management solution, is not always the right solution. If you own/operate/maintain a site that already has sufficient development resources to manage it, you already have a significant number of 'deployments' on your site, or if you are not in a financial situation that can support the cost, Ensighten may not be for you. Case-in-point, if you are working for a small start-up and your site has limited functionality - especially non-e-commerce - moving code into tag management is probably not worth the cost because you likely don't drive enough traffic to necessitate that kind of oversight. In these cases, you may only have a single tracking method (such as Google Analytics), and using Ensighten would be overkill.

However, if you are starting fresh with a high-traffic site, you have limited dev resources, and you have specific types of tracking you know you want to put in place, Ensighten might be the way to go. With Ensighten, you will be able to have non-technical folks place code deployments into the tool without clogging the backlog of dev work, and speedup the time to delivery.