ObservePoint Pricing Overview

Building journeys is straightforward, with plenty of tests and scripting options that help us get the most out of our crawls. We initially used it to monitor analytics KPIs, and expanded our use from there. The detailed post-mortem reports are especially useful for analyzing journey findings. They allow me to pinpoint the exact source of issues like rogue cookies, broken JavaScript, content problems, and more. I appreciate that my reports are easy to share, and that users in different roles can access the tools they need without unnecessary complexity. Customer support has also been excellent; their team has even created journeys for us when we were too busy. Review collected by and hosted on G2.com.

Easy to forget about and with infrequent use, I get lost in the configuration options. Review collected by and hosted on G2.com.

ObservePoint is full of potential and possibilities. I'm actually surprised every time I find a use-case that I would like them to cover that they are not already covering due to how many use-cases they already take into account.

They provide a way for us to watch over our implementation, to verify our new changes work correctly before and after publishes and to feel more confident that things are working on the data colection side. Review collected by and hosted on G2.com.

#1 OP needs to offer consulting services. I want to be able to augment my team with an OP professional who uses the tool every day. Someone who can aid us in implementing the tool but then also be the person who works to maintain and report on what OP finds. There’s simply too much to cover for someone who is learning OP on the fly and likely only dabbles in the tool during their day to day work. They end up feeling lost or frustrated over time in trying to keep up with the implementation or what is actually valuable to report on. Too often I have worked at companies that implement OP with excitement only to fairly quickly burn out on the tool because no one is actively maintaining it or doing good reporting and analysis to show value from the tool.

#2 ObservePoint is difficult to maintain and is often purchased without a good understanding of just how much time needs to be set aside to build and report on its results but also to fix it when it breaks. Because IT WILL BREAK regularly for most people. That's not OP's fault, but it needs to be expected. Maintenance for this tool can be quite involved. ObservePoint is a finicky tool. Or rather, web sites are finicky and seemingly ever changing and it makes maintaining an OP implementation very difficult. If you have a web/marketing team that continually changes your website then OP is going to be much more difficult to maintain for in-depth Journey's/Audits. Higher level Audits can easily and reliably help you know if things break in analytics calls and pixels that are set on all page loads since you don't have to rely on click listeners. Journeys can let you know if a flow breaks and cannot be completed for some reason, but be wary, as OP may not be able to complete the Journey even though everyopne else can because of the "finicky-ness" of CSS Selectors.

#3 OP needs a server-side solution that works from the data storage side. I need them to be able to tell me if what is actually getting to the database is trending correctly or looks accurate. There is so much wiggle room and so many unknowns on the client side due to device types, browsers, and individual extensions, plugins, manual changes, etc that people use on their own devices. However, the data that actually arrives server-side is consistent and ultimately is the reality of what you are reporting on. I want a tool like OP that lets me validate that things look good on the client-side, but I'm also aching for one that allows me to use APIs to look at the collected data for trends and outages. One tool that reports in a unified way instead of having to rely on Adobe, Google, Meta, etc to provide good alerting tools. Many don't. Review collected by and hosted on G2.com.