Amplitude Analytics is an analytics platform for mobile and web. It is designed to help organizations segment users and analyze funnels,
retention and revenue. Amplitude Analytics helps you achieve actionable insights from customer digital journeys and uses behavioral graphs to build customer-focused products. Amplitude also optimizes digital products for increased quality engagements, increased conversion rates, and long-term customer loyalty.
$59
per month
Google Tag Manager
Score 8.7 out of 10
N/A
From Google, the Google Tag Manager is a tag management application that facilitates creating, embedding, and updating tags across websites and mobile apps, thus gaining the benefits of data standardization and speed of deployment. Google touts an agency friendly system with multiple user access, and tools to improve tags performance like debugging, and rules, macros or automated tag firing. The Google Tag Manager also integrates with Google product DoubleClick. Moreover, Google Tag Manager is…
N/A
Pricing
Amplitude Analytics
Google Tag Manager
Editions & Modules
Plus
$49
per month (paid annually)
Growth
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
Amplitude Analytics
Google Tag Manager
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
Amplitude Analytics
Google Tag Manager
Considered Both Products
Amplitude Analytics
Verified User
Manager
Chose Amplitude Analytics
Amplitude Analytics provides much more granular data than Google Analytics and gives you much more flexibility in how you can segment and splice the data. It also provides the ability to create closed funnels, which I have yet to find out how to do in Google Analytics. …
Amplitude Analytics is an excellent solution for anyone with a mobile app and you want to track what users are doing, are they completing conversion steps, and are they coming back more often. This all helps you visual your customer bases engagement and help project future engagement and create goals. This also helps with prioritizing products to address drop-off points in the product to increase conversions.
I use Google Tag Manager (GTM) daily and create tags/triggers for all of our client's websites. It is easy to set up but for some of my tasks, the process does get repetitive so it'd be nice to have a default setting I can use when I have to create accounts, and then tweak/add things to them as needed. It is a great way to collect data and have code on the site without having to log into the site builder all the time. It makes it convenient to make edits or add code after our client's sites go live with us.
Selecting elements on a site [object, class, cookie, etc] (to later fire an event, send some data, etc) is very easy with triggers. Want to add an event when someone clicks on a button? Super easy. It was many many DOM selectors and you can even add custom functions if you need to do something more specific
In general, firing events in different circumstances is very easy mixing triggers and tags. You can track almost any element of the DOM and do whatever you want with it.
Testing is a great functionality. Only you can see what's on the site and you can debug it easily by seeing which events or tags were triggered and all the DOM elements involved (and why they matched the trigger).
Working in environments (staging, production) and versioning is easy to do, deploying changes in 2 clicks.
Some offerings seem duplicative, like dashboards and notebooks, which only seem to differ in that one can subscribe to dashboards
The messaging on valid vs invalid property types could be better explained to clarify which types (string, Boolean, integer, etc) are expected in particular scenarios. Though the type is usually set during event creation, we've often seen examples where the data received in production is different, leading to 'invalid type' errors
There are several good integrations, but there can always be more. Native tracking for call tracking solutions, analytics providers, non-Google advertisers would be top of my list.
Documentation is just dreadful. Luckily there are some awesome folks out there doing crowdsourced tutorials (shout out to Simo Ahava) but by and large the Google Tag Manager instructions are worth what you pay for them.
Great product Good value for the cost/initiate Support docs and FAQs are great - they limit the necessity of reaching out to in-person support. So when you do call them ... it is for a legit question/issue, no just a "where is it" or a "how to I do xyz123?"
Google Tag Manager makes tracking traffic to our websites effortless, which enables our developers to focus on other tasks. Setting up a new instance takes only minutes and additional scripts can be added/modified without touching the source code of a site in production. This enables our marketing directors to coordinate tests and experiments with minimal effort.
It's a fairly straightforward platform that's beginner friendly. The biggest usability hurdle is most often created by your own team, as it's imperative to know what event sources are being sent to Amplitude and what those event names are. Within being properly onboarded by a team member it can be hard to get started using Amplitude. It takes time to understand what data your company may be sending to the product, the naming conventions of events (especially if there are old or deprecated events names
No difficult obstacle to overcome but Google Tag Manager can still be difficult for many users to deploy. Sure the basic HTML script can be deployed quite easily, but when you start to require triggers, variables, etc, it can be a little daunting.
Alway up and running, or if there is a problem we can get back in the game right away. The reliability was a big selling point for me, and it was true when this company got it. Rollouts can be tough, but this was pretty seamless. Good support throughout the process, good documentation to handle questions/tips
No issues, problems, or negative remarks from us!! We had a plan, vendor support was rock solid, our data folks have experience, OCM supported as needed, and we got the rollout done on time, on budget, and with only minor hiccups. SInce the rollout, most of us have already forgotten the hiccups and generally speak highly of the product
I haven't used the Amplitude support other than their training docs so I can't speak too much to the in-person support but the docs are serviceable. Nothing too crazy but between the user tips, email notifications, and the decent number of docs I was able to get the support I needed to ramp up on the tool.
GTM does not provide support. This is one of GTM's biggest issues but it's due to the level of customization for each website. If your team thinks they would heavily rely on the need for a support staff it is probably better to invest in a paid service with a team that can support your needs.
Virtual Not bad considering the timeframe and turnaround. The biggest benefit was for my end-users to hear a voice (other than mine/ours! LOL) telling them about the new features and capabilities. The in-person training was really good for having an expert that knows the answers and could refer to past experiences, problems, solutions. THey were a great resource to ease the transition ... basically a "you are gonna be okay with this change ... you got this etc.!" kinda vibe
Good enough to get strong baseline. I always make sure our our users go to and/or focus on the vebndor-provided support docs rather than any formal training. Our instructors come and go, but written policy and how-to docs live much longer in a corporate setting. That said, the online training is sufficient. I like that the training curric is stacked and progressive.
My team members all have background as data analysts, so Amp was pretty easy to for them. There was sufficient online training available. We also used the available support documents. The actual rollout went well. We did significant testing beforehand. We did a phased rollout, with partial silent rollout (part of OCM's plan) for the smallest line of business. THe silent one was "silent" b/c it was done without fanfare or public notices ... it was just a "we're doing some things, it wont impact your work or workday
Planning and communication will help greatly with an in-house implementation. If there are large teams, try to limit the number of people involved to 1-2 developers (back-end dev may be necessary depending on your platform), one analytics marketer and one project manager.
Amplitude Analytics provides much more granular data than Google Analytics and gives you much more flexibility in how you can segment and splice the data. It also provides the ability to create closed funnels, which I have yet to find out how to do in Google Analytics. Amplitude has a very similar interface to Mixpanel, with a few handy additions, like the ability to name and categorize your events.
We moved to GTM from a standard Google Analytics implementation. GTM is much more flexible and easier to make changes, especially as the changes relate to multiple sites and environments. While there is a learning curve when figuring out how to use GTM, I believe the change has been worth it because it helps us understand at a more fundamental level how our tracking works and gives us a lot more control over what we track and how.
Like all the other grades, it was mostly an easy implementation ... we have experience people, the rollout in general is well planned, and the vendor was very supportive
GTM is very useful to determine if a particular element on the site is useful (i.e. is it being watched, is it being clicked, does it help customers navigate through more pages). As an SEO person, I can use this information to decide what to optimize for but also to track progress and see improvements in engagement.
With the use of Google Tag Manager, I was able to easily inject an A/B testing tool which lead to several improvements in lead generation.
