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 7.8 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
Sentry
Score 8.7 out of 10
N/A
Sentry provides engineering teams with tools to detect and solve user-impacting bugs and other issues.
$26
per month
Pricing
Google Analytics
New Relic
Sentry
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
Team
$26
per month
Business
$80
per month
Developer
Free
Enterprise
Contact sales team
Offerings
Pricing Offerings
Google Analytics
New Relic
Sentry
Free Trial
No
No
Yes
Free/Freemium Version
Yes
Yes
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Google Analytics
New Relic
Sentry
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 …
For front-end applications we compared New Relic with Sentry, the most pro of [New Relic] is the capability the merge data from back-end applications, having a clear view of all the context. Another way, the Sentry is focused only on front-end applications and is not able to …
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.
Less expensive than Datadog and Sentry with almost everything we need. Less effort to set up and maintain than elastic search and kibana so saved a ton on engineering bandwidth which would have otherwise been lost.
New Relic is the most full-featured offering that we've found, and is incredibly easy to start using with a PHP app. The New Relic agent is installed as a PHP extension so it is able to monitor and track the performance of any PHP app being run by the web server. Other tools …
The differentiating feature, in my opinion, is the support given by New Relic, in our org, there is a slack channel dedicated for New Relic which allows us to have a quicker response and more convenience.
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 …
New Relic is more affordable for infrastructure monitoring and had a more mature app monitoring suite (but data dog is catching up). Data dog has better predictive analytics and DB monitoring.
Stackify's pricing was quite a bit better than New Relic, however on the whole New Relic had more features overall that benefitted our team. Overall though however, Stackify is worth checking out, they are improving their application over time and adding more features. It's …
Sentry is better suited for tracking and aggregating exceptions over New Relic. New Relic does report on exceptions that occur, but Sentry is better at rolling up similar exceptions and filtering out the noise. Sentry also does a great job at identifying when an exception first …
Sentry was cheaper and lighter weight/easier to deal with. New Relic always felt like it was slowing the site down some. I don’t think either has had any major negative impact, but Sentry always seemed better/faster. Also, Sentry doesn’t have contracts like New Relic does …
We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide …
It is cheaper and offers better support for front-end applications for enterprise large environments with more then 30 scrum teams and hundreds of micro frontend applications. The configuration options, both with the agent and from the user interface, are superior to other …
There are quite a few players in this space, but Rollbar and Sentry seem to be the top two. I can't remember why I chose Sentry over Rollbar, but they seem pretty close in terms of features.
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
Great for standard web application performance monitoring, analytics and error reporting. Shows line level code errors, gives insight into performance issues (plugins, API issues, etc.). Automation and scheduled scanning in production gives client visibility into 'after deployment' value. Also lets a relatively small number of developers keep tabs on a handful of different site/applications without needing a bunch of tools. The UI is pretty complicated and can be overwhelming for new users. Documentation could be better for the learning curve,
Great web interface. Lots of data available in a really clean format, with filtering options and more.
Per-user exception tracking. User is complaining about something being broken? Look up their account ID in Sentry and you can see if they've run into any exceptions (with device information included, of course).
Source map uploading. Took a little while to figure this out but now we have our deploy script upload sourcemaps to Sentry on each deployment, meaning we get to see stack traces that aren't obfuscated!
Very generous free tier – 10,000 events per month. We're nowhere near that yet.
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 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.
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.
Its incredibly versatile, but that leads to complexity for the uninitiated, which can be intimidating. Nevertheless its a well polished product, in our case leading to only using it for a focus on frontend is still more cost effective than buying a one-to-rule-them-all tool...
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
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.
It is cheaper and offers better support for front-end applications for enterprise large environments with more then 30 scrum teams and hundreds of micro frontend applications. The configuration options, both with the agent and from the user interface, are superior to other tools, and the documentation is also very easy to use.
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