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 product marketers to 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.
$61
per month
Optimizely Web Experimentation
Score 8.6 out of 10
N/A
Whether launching a first test or scaling a sophisticated experimentation program, Optimizely Web Experimentation aims to deliver the insights needed to craft high-performing digital experiences that drive engagement, increase conversions, and accelerate growth.
I have used tools in various spaces that have all the flashy bells and whistles, and is, but lacks some basic features - Optimizely isn't this. While other tools, such as Adobe Target, Evergage, Dynamic Yield, Google Optimize, or even Taplytics may make more sense for your …
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 think it can serve the whole spectrum of experiences from people who are just getting used to web experimentation. It's really easy to pick up and use. If you're more experienced then it works well because it just gets out of the way and lets you really focus on the experimentation side of things. So yeah, strongly recommend. I think it is well suited both to small businesses and large enterprises as well. I think it's got a really low barrier to entry. It's very easy to integrate on your website and get results quickly. Likewise, if you are a big business, it's incrementally adoptable, so you can start out with one component of optimizing and you can build there and start to build in things like data CMS to augment experimentation as well. So it's got a really strong a pathway to grow your MarTech platform if you're a small company or a big company.
The Platform contains drag-and-drop editor options for creating variations, which ease the A/B tests process, as it does not require any coding or development resources.
Establishing it is so simple that even a non-technical person can do it perfectly.
It provides real-time results and analytics with robust dashboard access through which you can quickly analyze how different variations perform. With this, your team can easily make data-driven decisions Fastly.
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
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?"
I rated this question because at this stage, Optimizely does most everything we need so I don't foresee a need to migrate to a new tool. We have the infrastructure already in place and it is a sizeable lift to pivot to another tool with no guarantee that it will work as good or even better than Optimizely
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
Optimizely Web Experimentation's visual editor is handy for non-technical or quick iterative testing. When it comes to content changes it's as easy as going into wordpress, clicking around, and then seeing your changes live--what you see is what you get. The preview and approval process for sharing built experiments is also handy for sharing experiments across teams for QA purposes or otherwise.
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
I would rate Optimizely Web Experimentation's availability as a 10 out of 10. The software is reliable and does not experience any application errors or unplanned outages. Additionally, the customer service and technical support teams are always available to help with any issues or questions.
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 would rate Optimizely Web Experimentation's performance as a 9 out of 10. Pages load quickly, reports are complete in a reasonable time frame, and the software does not slow down any other software or systems that it integrates with. Additionally, the customer service and technical support teams are always available to help with any issues or questions.
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.
They always are quick to respond, and are so friendly and helpful. They always answer the phone right away. And [they are] always willing to not only help you with your problem, but if you need ideas they have suggestions as well.
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.
The tool itself is not very difficult to use so training was not very useful in my opinion. It did not also account for success events more complex than a click (which my company being ecommerce is looking to examine more than a mere click).
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
In retrospect: - I think I should have stressed more demo's / workshopping with the Optimizely team at the start. I felt too confident during demo stages, and when came time to actually start, I was a bit lost. (The answer is likely I should have had them on-hand for our first install.. they offered but I thought I was OK.) - Really getting an understanding / asking them prior to install of how to make it really work for checkout pages / one that uses dynamic content or user interaction to determine what the UI does. Could have saved some time by addressing this at the beginning, as some things we needed to create on our site for Optimizely to "use" as a trigger for the variation test. - Having a number of planned/hoped-for tests already in-hand before working with Optimizely team. Sharing those thoughts with them would likely have started conversations on additional things we needed to do to make them work (rather than figuring that out during the actual builds). Since I had development time available, I could have added more things to the baseline installation since my developers were already "looking under the hood" of the site.
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.
The ability to do A/B testing in Optimizely along with the associated statistical modelling and audience segmentation means it is a much better solution than using something like Google Analytics were a lot more effort is required to identify and isolate the specific data you need to confidently make changes
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
We can use it flexibly across lines of business and have it in use across two departments. We have different use cases and slightly different outcomes, but can unify our results based on impact to the bottom line. Finally, we can generate value from anywhere in the org for any stakeholders as needed.
We're able to share definitive annualized revenue projections with our team, showing what would happen if we put a test into Production
Showing the results of a test on a new page or feature prior to full implementation on a site saves developer time (if a test proves the new element doesn't deliver a significant improvement.
Making a change via the WYSIWYG interface allows us to see multiple changes without developer intervention.
