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
Heroku Platform
Score 7.8 out of 10
N/A
The Heroku Platform, now from Salesforce, is a platform-as-a-service based on
a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric
approach for software delivery, integrated with developer tools and
workflows. It’s three main tool are: Heroku Developer Experience (DX), Heroku
Operational Experience (OpEx), and Heroku Runtime.
Heroku Developer Experience (DX)
Developers deploy directly from tools like…
$85
per month
Pricing
Google Analytics
Heroku Platform
Editions & Modules
Google Analytics 360
150,000
per year
Google Analytics
Free
Production
$25.00
per month
Advanced
$250.00
per month
Offerings
Pricing Offerings
Google Analytics
Heroku Platform
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Google Analytics
Heroku Platform
Considered Both Products
Google Analytics
No answer on this topic
Heroku Platform
Verified User
Engineer
Chose Heroku Platform
I believe Azure App Service is pretty similar to Heroku as you can in both deploy your backend applications. However, the dyno concept and it's drastically simple web dashboard makes Heroku a much better and sane alternative to Azure App Service. In Heroku, you get abstracted of …
Heroku is a really great platform to get up and running QUICKLY and efficiently. What Heroku is really great at that other services are lacking is ease of use, documentation. It is really great for beginning developers and awesome to get up and running to take care of lots 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.
Heroku is very well suited for startups looking to get a server stack up and running quickly. There is little to no overhead when managing your instances. However, you'll need a background in basic DevOps or system management to make sure everything is set up correctly. In addition, it's easy to accidentally go crazy on pricing. Make sure you're only creating the server instances you need to run the base application and set up an auto-scaler plugin to handle peaks.
Heroku has a very simple deployment model, making it easy to get your application up-and-running with minimal effort. We can focus on our efforts the unique aspects of our application.
The robust add-on marketplace makes it easy to try out new approaches with minimal effort and investment -- and when we settle on a solution, we can easily scale it.
Heroku's support is quite good -- their staff is quite technical and willing to get into the weeds to diagnose even complicated problems.
Large price jumps between certain resource tiers (2x Dyno for $50 per month versus Performance Dyno for $250). Free Postgres next jumps to $50 per month.
Marketing/Branding to non-technical stakeholders. As the years pass, I've had to fight more to convince stakeholders on the value of Heroku over AWS.
Improve Buildpack documentation. This is one area where Heroku's documentation is fairly confusing.
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.
Heroku is easy to use, services a ton of functions for you out of the box, and provides a means to get a software product off the ground and managed quickly and easily. The tools provide allows a small to medium size org to move very quickly. The CLI tools provided make managing an entire technical infrastructure simple.
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
Easy to use web based console and easy to use command line tools; deployment is done directly from a GIT repository. What more could you ask for? The one thing that keeps me from giving it a 10 is that custom build packs are almost incomprehensible. We used one for a while because we needed cairo graphics processing. Fortunately, I was able to figure out a different way to do what we needed so that we could get off the custom build pack.
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.
Heroku availability correlates pretty strongly to AWS US EAST availability. We had a couple of times where there was a Heroku-specific issue but not for the last 7-8 months.
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.
I've used it for many years without facing any major problem. It's not hard at all to get used to it, it's documentation is outstanding and simple. We are close to 2020 and I don't think most of the existing companies or startups should still face old problems such as wasting time deploying code and calculate computing resources.
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.
Be ready to pay a bit more than expected in the beginning if you're migrating from a big server. The application is probably not ready for the change and you have to keep improving it with time.
It's also important to consider that you can't save anything to the disc as it will be lost when your application restarts, so you have to think about using something like S3.
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.
Heroku is the more expensive option for hosting compared to some of the cloud platforms we investigated, but it's worth it for us because of the plug-and-play nature of Heroku deployment. We can be up and running in a few minutes and know with precision how much it will cost us each month to run the application, unlike Amazon Web Services where you have to go to great pains to configure it correctly or else you might end up with a shocking monthly bill. Overall, spending the time to configure Amazon Web Services or one of its competitors is likely the more affordable and powerful choice, because you have control over so many specifics of the configuration. But it also requires the burden of continuing to maintain and update your AWS instance, whereas with Heroku they take care of security fixes and platform upgrades. It's a great service and we are happy to pay the extra cost for the value-adds Heroku provides.
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