Google Analytics is perhaps the best-known web analytics product and, as a free product, it has massive adoption. Although it lacks some enterprise-level features compared to its competitors in the space, the launch of the paid Google Analytics Premium edition seems likely to close the gap.
$0
per month
New Relic
Score 8.2 out of 10
N/A
New Relic is a SaaS-based web and mobile application performance management provider for the cloud and the datacenter. They provide code-level diagnostics for dedicated infrastructures, the cloud, or hybrid environments and real time monitoring.
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Redis Software
Score 9.1 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.
N/A
Pricing
Google Analytics
New Relic
Redis Software
Editions & Modules
Google Analytics 360
150,000
per year
Google Analytics
Free
Free (Forever)
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Telemetry Data Platform
$0.25
per month per extra GB data ingest (after first free 100GB per month)
Incident Intelligence
$0.50
per month per event (after first 1000 free events per month)
Standard
$99
per month per full user (after first free full user - unlimited free basic users)
Pro
Contact sales team
Enterprise
Contact sales team
No answers on this topic
Offerings
Pricing Offerings
Google Analytics
New Relic
Redis Software
Free Trial
No
No
Yes
Free/Freemium Version
Yes
Yes
Yes
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
—
—
—
More Pricing Information
Community Pulse
Google Analytics
New Relic
Redis Software
Considered Multiple Products
Google Analytics
Verified User
Engineer
Chose Google Analytics
Google Analytics is useful for tracking data at the Client end, whereas New Relic is useful to track on the Backend API stats.
Google Analytics goes head to head when it comes to basic browser and activity tracking, but falls behind when it comes to full tracking of a request and the performance impact it has on a web site or application. A lot of this is due to the fact that Google Analytics can only …
Google Analytics is useful for end-user traffic distribution and when combined with New Relic provides a more complete picture on user interaction with our site.
All of these apps have pros and cons. AppDynamics is very powerful and provides excellent reporting and deep dives on performance. Tableau Desktop's setup can be a bit tedious, but once it is done, it is a great tool to provide visual performance reports. However, the lack of …
Google Analytics is particularly well suited for tracking and analyzing customer behavior on a grocery e-commerce platform. It provides a wealth of information about customer behavior, including what products are most popular, what pages are visited the most, and where customers are coming from. This information can help the platform optimize its website for better customer engagement and conversion rates. However, Google Analytics may not be the best tool for more advanced, granular analysis of customer behavior, such as tracking individual customer journeys or understanding customer motivations. In these cases, it may be more appropriate to use additional tools or solutions that provide deeper insights into customer behavior.
New Relic its an excellent tool for monitoring services used on the SAAS universe, like web servers, relational and nosql dbms, reverse proxies, text databases, etc. Its also a powerful tool to monitor resource usage on said servers. However, its not well fitted to monitor custom services - if you need to generate alerts based on logs or database information, for example
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
Reliable. With a proper multi-node configuration, it can handle failover instantly.
Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
Fast. We process tens of thousands of RPS and it doesn't skip a beat.
And while powerful, building tailored dashboards with organ-specific metrics (such as energy load variance across regions) can be difficult to navigate. The UI isn't as drag-and-drop easy, and query-based widgets typically involve some trial and error for non-devs.
Alerts may be hypersensitive or over general. I We often get a spam of non-critical alerts while doing load testing, all overhauling to me alone and making it difficult to identify actual issues especially in energy systems where spikes are very common.
With our expanding fleet of Iot devices, the per-host pricing model is becoming expensive, quickly. More detailed billing based on microservices, or that works at sensor level, would make it more adaptable for energy platforms.
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
We will continue to use Google Analytics for several reasons. It is free, which is a huge selling point. It houses all of our ecommerce stores' data, and though it can't account for refunds or fraud orders, gives us and our clients directional, real time information on individual and group store performance.
The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
Google Analytics provides a wealth of data, down to minute levels. That is it's greatest detriment: find the right information when you need it can be a cumbersome task. You are able to create shortcuts, however, so it can mitigate some of this problem. Google is continually refining Analytics, so I do not doubt there will be improvements
I have given this much rating as I am used New Relic in different sectors and for different use cases like its K8s monitoring, infra monitoring, full stack monitoring as compare to other tools New Relic gives data in a formatted and connected way, and also it is giving us value for money. It also launches new features day by day which helps users to track the issue very quickly. It also supports OTel integrations which is the latest trend of observability tools. thats why I had given this much rating to New Relic.
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
We all know Google is at top when it comes to availability. We have never faced any such instances where I can suggest otherwise. All you need is a Google account, a device and internet connection to use this super powerful tool for reporting and visualising your site data, traffic, events, etc. that too in real time.
This has been a catalyst for improving our site's traffic handling capabilities. We were able to identify exit% from our sites through it and we used recommendations to handle and implement the same in our sites. We have been increasing the usage of Google Analytics in our sites and never had any performance related issues if we used Analytics
The Google reps respond very quickly. However, sometimes they can overly call you to set up an apportionment. I'm very proficient and sometimes when I talk to reps, they give beginner tutorials and insights that are a waste of time. I wish Google would understand my level of expertise and assign me to a rep (long-term) that doesn't have to walk me through the basics.
The support team has been really helpful and resolved most of the issues on time. However, for a couple of issues, several follow-ups were needed to elicit a reasonable response. The issue was deeply technical and could have been investigated only by their Architects, and bringing them into the ticket took longer than needed
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
love the product and training they provide for businesses of all sizes. The following list of links will help you get started with Google Analytics from setup to understanding what data is being presented by Google Analytics.
I think my biggest take away from the Google Analytics implementation was that there needs to be a clear understanding of what you want to achieve and how you want to achieve it before you start. Originally the analytics were added to track visitors, but as we became more savvy with the product, we began adding more and more functionality, and defining guidelines as we went along. While not detrimental to our success, this lack of an overarching goal resulted in some minor setbacks in implementation and the collection of some messy data that is unusable.
It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.
I have not used Adobe Analytics as much, but I know they offer something called customer journey analytics, which we are evaluating now. I have used Semrush, and I find them much better than Google Analytics. I feel a fairly nontechnical person could learn Semrush in about a month. They also offer features like competitive analysis (on content, keywords, traffic, etc.), which is very useful. If you have to choose one among Semrush and Google Analytics, I would say go for Semrush.
Data Dog has solutions that look more attractive, but not at their price point. We have also tried to build a solution straight from the Cloud, where our business is built, but some things are too hard to replicate. This shows that New Relic is useful and helps our efficiency.
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
Google Analytics is currently handling the reporting and tracking of near about 80 sites in our project. And I am not talking about the sites from different projects. They may have way more accounts than that. Never ever felt a performance issue from Google's end while generating or customising reports or tracking custom events or creating custom dimensions
Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
