Streamline implementations and empower non-technical employees with Ensighten 2.0
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.
Pros
- 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
Cons
- 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.
Comments
Please log in to join the conversation