Apache Flink vs. Ensighten Manage

In well-suited scenarios, I would recommend using Apache Flink when you need to perform real-time analytics on streaming data, such as monitoring user activities, analyzing IoT device data, or processing financial transactions in real-time. It is also a good choice in scenarios where fault tolerance and consistency are crucial. I would not recommend it for simple batch processing pipelines or for teams that aren't experienced, as it might be overkill, and the steep learning curve may not justify the investment.

Incentivized

Ensighten manage can be setup to be used by non technical business users. However the product provides a lot of flexibility by the way of custom custom Javascript and HTML tags, and advanced features like events, which needs coding experience as well as understanding of web technologies. Ensighten mobile is also a promising tool, but so far we have not had any luck setting it up, mainly due to challenges with Android setup

Incentivized

• Low latency Stream Processing, enabling real-time analytics
• Scalability, due its great parallel capabilities
• Stateful Processing, providing several built-in fault tolerance systems
• Flexibility, supporting both batch and stream processing

Incentivized

• Supports typical software development life cycle (SDLC) process by facilitating DEV, QA and PROD deployment stages through spaces.
• Roles and security can be thoroughly defined.
• Very good selection of tagging technologies.
• Site is stable, no availability concerns.
• GUI in general is straightforward.

Incentivized

• Python/SQL API, since both are relatively new, still misses a few features in comparison with the Java/Scala option
• Steep Learning Curve, it's documentation could be improved to something more user-friendly, and it could also discuss more theoretical concepts than just coding
• Community smaller than other frameworks

Incentivized

• While the code templates that are already existent provide an easy interface to leverage existing code sets, custom codes still need to be written a lot of times since the templatized versions apply them to a global scope only and not for individual URLs or regex's for specific use cases for pixel vendors. Also, the library needs to be updated more frequently with new pixel vendors injecting their own variations of codes
• Professional services (both the shared and dedicated model) definitely needs a lot of improvement since this is something that we have been immensely challenged with as a client of Ensighten in general. General response times and availability of support hours both from an account management standpoint and professional services/support standpoint have been quite challenging in the past year or two and there has been no real progress on this front
• Ensighten Manage uses its own best practices to modify certain code sets from say JavaScript to Jquery for instance as it may be more compatible within its platform. This needs to change so that the tool is more nimble, agile and flexible in accepting and executing on different vendor codes

Incentivized

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.

The GUI looks professional and is overall very usable. Menu and buttons are laid out well and easy to view. Wizard-like tag configuration is pleasant. Color scheme is pleasant to view, lacking fatiguing colors. Page load progress indicator is reassuring. Filters on past-visited screens are remembered, very handy. Filter options are flexible.

Incentivized

The Ensighten Manage support team has been helpful and dedicated to assisting us solve problems that come up with tag deployments even when the issues are completely unrelated to the core Manage product itself. They seem to have the right mix of tag-specific subject matter experts and general support resources.

Incentivized

Ensighten is a great tool, and as good as any in the industry with strong workflow capabilities, an admin API and a friendly interface. It does have some limitations and is not entirely "marketer friendly" as they claim. Also, note we've experienced some performance/load time issues with the Ensighten data layer, which we are addressing with them.

Incentivized

Apache Spark is more user-friendly and features higher-level APIs. However, it was initially built for batch processing and only more recently gained streaming capabilities. In contrast, Apache Flink processes streaming data natively. Therefore, in terms of low latency and fault tolerance, Apache Flink takes the lead. However, Spark has a larger community and a decidedly lower learning curve.

Incentivized

We've used Ensighten Tag Management since 2013 - before this, we used Adobe's out of the box dynamic tagging solution. Since Ensighten is a purpose-built tool, it provides a great deal more flexibility than that of Adobe. Rule-drived spaces and conditions were not available in Adobe's tag container. Ensighten's visual tagger is unique in its ability to place MBOXes on the page for A/B testing. Finally, mobile tagging is simply not possible without going through the release process, which Ensighten has freed us from

Incentivized

• Allowed for real-time data recovery, adding significant value to the busines
• Enabled us to create new internal tools that we couldn't find in the market, becoming a strategic asset for the business
• Enhanced the overall technical capability of the team

Incentivized

• Increased complexity when debugging so bug are taking longer to fix when they are related to Ensighten
• Our sites are loading about 10 seconds faster and have opened our eyes as to how much javascript we are rendering onto our sites which is no longer needed.

Incentivized