Glassbox Reviews

Our main purpose for using Glassbox is to capture user sessions and user activity on the live site. Based on that captured data, we create funnels and reports to check the customer impact for specific services or categories that are failing and identify which countries are impacted.

For example, if a person is trying to purchase a product and add a laptop into the cart but encounters intermittent errors during this process, and then receives errors when clicking the checkout button stating they are unable to checkout, Glassbox captures this real customer experience. When this happens, specific error messages are displayed on the screen, and Glassbox highlights it as an alert with a 5XX response status code.

From a day-to-day perspective, we have created specific dashboards and reports that provide alerts if any unknown activity occurs on the live site. When a customer faces a real issue, we receive alerts and notifications that help us understand what is happening.

Glassbox now has GIA as an AI integration that provides analysis very quickly without needing to watch the entire session. Based on previous results, the analysis is accurate 90 to 95 percent of the time regarding possible reasons why a user faced an issue. Based on that analysis, we can make a report and get things done to prevent errors.

The best features that Glassbox offers are reporting and the funnel. These two use cases help us most as we can determine the expected count for user behavior and compare it to earlier weeks and days from the same period. In the report section, we can identify specific alerts that are being triggered on a regular basis so we can capture and analyze them and fix them in the longer term.

The funnel feature helps us check user impact and identify which countries or specific areas the website is failing in. With this feature, if a customer is facing a cart page error, we can check how many users were impacted at that specific time and which regions those users are experiencing errors. We can also check what products those customers are trying to add. Based on that information, we can create a report and check comparisons. When we share it with the business team, they can determine if the issue is widespread and work on it with higher priority, or if it has lower impact with fewer users affected, indicating an intermittent error that can be worked on with lower priority.

Glassbox has had a positive impact on my organization through all the features it provides. As AI is advancing and its adaptability within the app itself integrates many use cases, the reports, funnels, dashboards, GIA features, and integrations that Glassbox provides help us address issue behavior and work on resolutions. Additionally, it creates reports that we can share with other teams so they can determine if the impact is wider. To prevent errors quickly, Glassbox captures reproducible customer errors. If an error is not reproducible, Glassbox does not capture it and can mark it as a false alert. This is how we prevent false alerts and capture only genuine alerts.

There are some areas where Glassbox does not capture genuine issues. For example, during login procedures involving multifactor authentication in someone's personal use case, if a user is failing at login, Glassbox sometimes does not capture the actual error because the error is intermittent or not continuous. Glassbox occasionally skips that and misses it.

Glassbox is a heavy tool and not a normal one. There are sometimes issues with Glassbox itself where some alerts do not get captured or the GIA integration does not show correct results, but it is being learned and improving.

I have been using Glassbox for around two years.

Glassbox is stable most of the time.

Glassbox's scalability is stable according to our organization's requirements. When an issue arises, there is a slight delay of three to four seconds to load data at heavy data loads, but once it starts, it does not lag or hang significantly.

Most of the time, when any activity needs to happen, we receive prior information regarding any expected delays or errors. Sometimes we do not have that information, but when we reach out to them, we receive a quick response and the issue is fixed.

Before Glassbox, we had different dashboards that captured errors, but we were not able to check what the actual user was experiencing regarding the issue. If an issue existed, we could only check which user faced the issue or what behavior we were getting, and that was the final result. With Glassbox, we can check real customers and identify which regions they are failing in.

Glassbox has helped us save considerable money and time. For example, if an issue needs to be solved by manually checking many users to determine whether the issue persists, Glassbox provides real customer data and real customer user sessions. Based on that analysis, what previously required eight people to manually check the data can now be done by three to four people using Glassbox while working in parallel.

We receive alerts that we have specified and set based on scenarios we have encountered earlier. We set a time frame or alert specific to those scenarios so we receive notifications and can capture issues earlier. Before a real customer is impacted, Glassbox itself tests using bot users that run accordingly. When those bot users fail, we know that this is the issue behavior we can expect. We attempt to replicate these issues ourselves to confirm they are problems we can foresee. Glassbox helps us know about those things earlier, providing us time before real users are also impacted and face the same issues. By escalating to the desired teams, we help prevent those errors.

I do not have additional items to address regarding needed improvements at this time.

I am not completely aware of the pricing, setup cost, and licensing, as the admin team or the business team has handled that. We are not involved in knowing the license costs or the setup that has been done. We simply use Glassbox and its features on a daily basis.

If an error is not reproducible, Glassbox does not capture it and can mark it as a false alert. This is how we prevent false alerts and capture only genuine alerts, which is how Glassbox has helped us overall.

The questions were precise, and overall, it was a good experience. I would rate Glassbox nine out of ten.

I have been familiar with Glassbox for around one to two years through enterprise digital experience and analytics-related discussions in the project, and my exposure has mainly been from a product and customer service perspective, especially around how organizations use session replay and user behavior insights to improve the digital journey.

My main use case for Glassbox has been around understanding user behavior and improving the digital experience. In enterprise applications, it is often difficult to know where users are facing issues just from the analytics dashboards alone. One example is using the session replay and customer journey insights to identify where users were dropping off or struggling during specific flows. Instead of relying only on assumptions or support tickets, teams could actually see how users interacted with the application, which helped improve usability and troubleshoot issues faster.

The feature I used the most is session replay. It was truly useful for understanding actual user behavior and reproducing issues quickly without depending only on logs or screenshots. It made troubleshooting easier because instead of guessing where users were struggling, teams could actually see the flow, how users navigated, where they clicked, where errors happened, or where they dropped off. That visibility was probably the biggest value for me.

One of the biggest benefits of using Glassbox is faster issue identification and better visibility into customer experience problems. Before using Glassbox, teams often spent considerable time trying to reproduce issues using logs, screenshots, or support tickets. With session replay and journey insights, troubleshooting became much quicker and more accurate, helping product and support teams make decisions based on actual user behavior instead of assumptions. Overall, it improved collaboration across teams, reduced investigation time, and helped prioritize user experience improvements more effectively.

The biggest improvement from using Glassbox came from time saving during issue investigation and troubleshooting. Problems that previously took a long time to reproduce using logs and support tickets could be identified much faster through session replay. It also improved efficiency across support, QA, and product teams because everyone had clearer visibility into user behavior. While I do not have exact numbers, the reduction in manual investigation effort and faster resolution time were definitely noticeable.

One frustration I have experienced with Glassbox is that with large amounts of session data, it could sometimes take time to filter and narrow down the exact user journey I want to analyze. Additionally, some advanced configurations and analytics features had a learning curve, so newer users did not always use the platform to its fullest potential initially.

One feature I wish Glassbox had is more intelligent AI-driven summarization of user sessions and issue patterns. When there is a large volume of session data, it would help if the platform could automatically highlight the most critical friction points or unusual behavior trends more proactively. Making advanced analytics and filtering simpler for casual users would also improve the overall experience.

If I could change just one thing about Glassbox, I would make issue detection and session analysis more proactive and easier to navigate. Sometimes, teams still spend time manually filtering through sessions to find the root cause of a problem. If the platform could automatically surface the most important user struggles or summarize key patterns more intelligently, it would speed up troubleshooting and help teams focus on fixing issues faster instead of searching through data.

Before my team started using Glassbox, teams were relying more on traditional analytics dashboards, logs, and customer support tickets. The problem was that those methods showed what happened, but not always why it happened from the user's perspective. Glassbox really helped solve the visibility issue into actual user behavior. The session replay and journey analytics made it much easier to identify friction points, reproduce issues faster, and understand where users were struggling without spending much time guessing or manually investigating.

From what I remember, when my team first implemented Glassbox, the initial setup and integration process took a few weeks to get properly configured and usable across the team. The basic implementation was fairly straightforward, but tuning the dashboards, validating data, session data, and aligning it with existing workflows took additional time. Most of the effort was around integration and making sure the right user journeys and events were being tracked correctly.

When my team was evaluating options, we looked at a few other digital analytics and customer experience tools that offered similar capabilities around user behavior tracking and session replay, such as Dynatrace, FullStory, and Adobe Analytics. What stood out with Glassbox was the combination of session replay, customer journey visibility, and the ability to troubleshoot user experience issues more directly from actual user interaction.

One of the biggest benefits of using Glassbox is faster issue identification and better visibility into customer experience problems. Before using Glassbox, teams often spent considerable time trying to reproduce issues using logs, screenshots, or support tickets. With session replay and journey insights, troubleshooting became much quicker and more accurate, helping product and support teams make decisions based on actual user behavior instead of assumptions. Overall, it improved collaboration across teams, reduced investigation time, and helped prioritize user experience improvements more effectively.

Glassbox improved collaboration quite a bit between product, QA, and support teams. Earlier, different teams were often looking at separate logs, screenshots, or reports while trying to understand the same issue. With Glassbox, everyone could look at the same user session and customer journey, which made discussions much clearer and reduced back-and-forth communication. It also changed the way issues were prioritized because teams could directly see user impact instead of relying only on assumptions or ticket descriptions.

There was definitely some learning involved in the beginning for teams that had not worked much with session replay or digital experience analytics tools before. The basic features were easy to understand, but teams needed some time to learn how to interpret user behavior data efficiently and effectively for troubleshooting or product improvement. Once people became familiar with the workflows, it became much easier to use across the team.

The adoption of Glassbox was a mix of both power users and casual users. Teams like Product, Analytics, QA, and Support used it more deeply on a regular basis, while some business or stakeholder teams mainly used the dashboards and high-level insights when needed. Not everyone used it the same way because different teams had different goals. For example, the QA team focused more on reproducing issues through session replay, while Product teams looked more at customer journey patterns and usability insights. Over time, adoption improved as teams started seeing the real value from the data.

Glassbox functions more as a team workflow, as Product, Analytics, QA, and Support teams all use the insights in different ways. For example, Product teams look at user behavior trends, QA teams use session replays to reproduce issues faster, and Support teams can better understand customer complaints. From my perspective, I mostly look at it from a product and user experience perspective to understand the friction points in the application.

My advice for someone thinking about using Glassbox with a similar workflow is to first identify the customer experience or troubleshooting gap you are trying to solve before implementation. Glassbox provides the most value when teams actively use session replay and journey insights as part of their regular workflow rather than treating it as just another analytics dashboard. I would also recommend involving product, QA, and support teams early because the platform works best when multiple teams collaborate around the same user behavior data, and spend time setting up meaningful tracking and filtering upfront as it makes insights much more useful and easier to manage later. I would rate this solution an 8 out of 10.

My main use case for Glassbox is to utilize it for the product layouts and the checkout funnels. In our main use case, we have to use two homepages, such as get your money and we have some apply now. So we have two interaction maps that while variant A gets more over time, variant B drives 1.3 more actual clicks. The team will choose variant B with confidence.

There are multiple features of Glassbox. One major feature of Glassbox is the Struggle Score that will be applied to every session by identifying the behavior of rage clicks, excessive scrolling, or dead clicks. It correlates the struggle with the revenue impact. Instead of seeing a list of a thousand errors, I will see five errors actually costing us the most money, helping me prioritize what to fix first.

In addition to that, in the tagless capture, there are some benefits such as no manual coding will be required and immediate answers to any questions. That is the best feature of Glassbox as well.

Glassbox positively impacts my organization by increasing our productivity using its features.

Glassbox can be improved in various ways. I think performance and lag are areas needing improvements. Basically, it is a platform speed issue. Users have reported performance lag, especially when running some complex funnels or loading session replays, with some actions taking two minutes to process.

I have been using Glassbox for 12 months.

Glassbox is stable.

Glassbox's scalability is great; it can manage a lot of data. It records 100% of digital interactions across web and mobile, capturing everything, which ensures removing the developer intervention as new features or pages are needed.

Customer support was very good. If I have any doubt or query, I can raise tickets with customer support, and they provide help immediately.

I did not use a different solution previously.

I have seen a return on investment, having saved a lot of money and time. Previously, the company was spending more, but now, currently, our productivity has increased so we do not require too many people to handle any scenario.

My experience with pricing, setup cost, and licensing is great, and it is cost-effective. The pricing is good, and licensing is also easy.

Before choosing Glassbox, I did not evaluate other options. I found the best in the market, which is Glassbox only.

I rate Glassbox an eight out of ten because I think it is easy to use. I would rate the customer support a seven on a scale of one to ten. I advise others looking into using Glassbox to use it because it is easy to use, easy to handle, and has very good customer support. Having it is easy, and licensing is also easy. I have assigned an overall review rating of eight to Glassbox.

My main use case for Glassbox was to track the customer journey and session replays, capturing the analytics setup of the customer portals.

We had applications where a customer would come and fill in many large forms. There were interactive elements to choose from as an onboarding journey and we implemented Glassbox there to track drop-off points, where users were spending more time. If there was a drop-off, we wanted to understand the exact reason and how customers were behaving with the onboarding process.

We also saw many errors, JavaScript errors, and front-end errors on the portal. Glassbox could identify broken flows, which helped us significantly.

The best features Glassbox offers are the tagless sub-capture, which I believe is very fast to implement compared to other tools, and it has strong session replay with enterprise-grade capabilities that work very well for larger applications.

Tagless implementation made the implementation faster because there is no need for constant tagging updates. Other vendor tools often require that on a regular basis, so considerable effort was saved there. In terms of strong session replay, Glassbox's offerings were more comprehensive than competitor tools, allowing us to see real-time visibility into issues.

Glassbox positively impacted our organization because we got a one-stop solution to track all different journeys, different dashboards, and different applications. We could do all the analytics around how users were behaving and what interactions were occurring. Glassbox is used extensively by research, UX, and marketing teams, and it has made a positive impact.

Glassbox can be improved because it is somewhat complex and there is a steep learning curve that requires training. Making it simpler would help. Secondly, it is somewhat overkill for basic analytics. Working in a startup, it is very expensive and the pricing is not very transparent. If I want to use a dashboard like Google Analytics or Mixpanel, it is quite expensive and complex, so having a lighter feature set for small-scale SMBs could be beneficial.

I have used Glassbox for about three years.

Glassbox is stable.

Glassbox's scalability is excellent as it is a complete enterprise tool, so we have no issues in that regard.

Customer support is good. We had an enterprise plan, so we had a relationship manager, which made everything easy. We did not encounter many technical issues, so not much support was needed. Learning was easy as well, with many available courses and content to set up. Once you work with a couple of applications, it becomes easier.

Previously, I had a mix of solutions, which included Google Analytics, Adobe Analytics, ContentSquare, and Quantum Metric. We switched to Glassbox to streamline into one solution.

The setup was seamless, and the support and implementation team were really helpful.

We saw a return on investment with Glassbox as we recovered the cost of implementation. The two main metrics were a better customer experience with fewer support issues and improved technical efficiency.

My experience with pricing, setup costs, and licensing was that the pricing was enterprise negotiated pricing based on sessions and features captured, along with a feature module, making it quite complex.

Before choosing Glassbox, we did not evaluate many other options. We got a very good recommendation about Glassbox and moved forward, although we had checked out Quantum Metric and ContentSquare.

My advice for others looking into using Glassbox is that if you are a startup or a small company, do not use Glassbox. There are easier to implement and cheaper tools for simple requirements. However, if you are an enterprise company needing one tool for everything, a complete end-to-end implementation with sufficient resources in terms of money and time, then use Glassbox as it is scalable and enterprise-grade.

Glassbox is a powerful digital experience platform with complete visibility into user behavior through multiple features. If you have the time and money to invest, Glassbox is a very good tool. I would rate this review a nine out of ten.

Glassbox is used primarily for digital experience analytics and customer journey monitoring. I use it to understand how customers interact with our website and applications, identify friction points, and improve the overall user experience.

One specific example of how I have used Glassbox to identify friction and improve the user experience is when we noticed a higher than expected drop-off rate during an online customer application process. Using Glassbox session replay and journey analytics, I reviewed user sessions and identified that many users were encountering validation errors on a specific form field without clear guidance on how to correct them.

In my opinion, the best features of Glassbox are session replay, customer journey analytics, error detection, and behavioral insights.

Session replay is the feature I find most valuable in my day-to-day work because it provides a clear view of exactly how users interact with our website or application, which makes troubleshooting much faster and more effective. For example, when a customer reports an issue, instead of trying to reproduce the problem based only on a description, I can review actual sessions and see where the user encountered difficulties.

Glassbox has impacted our organization positively, mainly because session replay is particularly valuable. It allows us to see exactly how users interact with our website or applications, making it easier to identify issues and understand customer behavior. Customer journey analytics helps us track how users move through different processes and identify drop-off points.

Glassbox has helped us reduce the time required to investigate customer issues, improve digital experience, and make data-driven decisions. It provides visibility into real user behavior that would otherwise be difficult to capture.

One thing I particularly appreciate about the features of Glassbox is how it brings together multiple types of insights in a single platform. Instead of looking at separate analytic reports, error logs, and user feedback, I can get a more complete picture of customer experience in one place.

Glassbox is powerful, but I think the user interface could be more intuitive for new users. Additional customization options in reporting and dashboards would also be beneficial.

I have been using Glassbox for around one year. During that time, I have used it to analyze customer journeys, review session replays, identify user experience issues, and gain insights into customer behavior across our digital platforms.

In my experience, Glassbox has been stable and reliable. We use it regularly for session replay, customer journey analysis, and issue investigation, and it generally performs consistently without disruptions.

In my experience, Glassbox has been scalable and able to handle increasing usage as our digital traffic and customer interactions have grown. Glassbox manages large volumes of session data and user interactions without noticeable performance issues.

I have reached out to Glassbox customer support a few times for configuration queries and minor issue clarification, and overall, the experience has been positive.

I was not directly involved in the tool evaluation and selection process, so I am not fully aware of the exact solution used before Glassbox. However, I understand that we previously relied more on traditional analytics and log-based troubleshooting methods, which did not provide full visibility into actual user sessions.

We have seen a positive return on investment with Glassbox; the biggest impact has been faster issue resolution and improved customer experience insights.

I was not directly involved in the vendor evaluation process, so I do not have full visibility into all the tools that were formally assessed. However, I understand that the organization evaluated a few digital experience analytics solutions before selecting Glassbox.

My advice to others looking into using Glassbox is to start with clear use cases, especially around key customer journeys where you want better visibility, such as onboarding, checkout, or application flows. Glassbox provides a lot of data, so having focused objectives helps you get value quickly. I would rate this review as an eight out of ten.