Need advice about which tool to choose?Ask the StackShare community!
Amplitude vs Flurry: What are the differences?
Data Collection and Storage: Amplitude and Flurry differ in their approach to data collection and storage. Amplitude uses a real-time, event-based data collection method, which means that it tracks every user interaction and stores it in its database. On the other hand, Flurry uses a session-based data collection approach, where it captures user interactions within a session and stores them temporarily. This difference in data collection and storage methods can impact the granularity and depth of the data analysis that can be performed.
Data Analysis and Visualization: Amplitude and Flurry also differ in their capabilities for data analysis and visualization. Amplitude provides highly customizable and flexible analysis options, allowing users to drill down into specific user segments and behaviors. It also offers advanced visualization tools, such as funnels and cohorts, to help users understand user behavior patterns. Flurry, on the other hand, offers a more simplified and basic data analysis and visualization interface, with limited options for customization and deep analysis.
Integration and Compatibility: When it comes to integration and compatibility, Amplitude and Flurry have some differences. Amplitude offers robust integrations with various third-party tools and platforms, such as segment.io, which allows users to import data from multiple sources. It also provides APIs and SDKs for easy integration with different platforms. Flurry, on the other hand, has more limited integrations and compatibility options, primarily focusing on mobile app analytics.
User Segmentation and Targeting: Amplitude and Flurry also differ in their capabilities for user segmentation and targeting. Amplitude provides advanced user segmentation options, allowing users to create highly specific and granular user segments based on various criteria, such as demographics, behaviors, and actions. These segments can then be used for targeted messaging and personalization. Flurry, on the other hand, offers more basic segmentation options, with limited criteria for segment creation and targeting capabilities.
Real-time Tracking and Reporting: Another difference between Amplitude and Flurry is their real-time tracking and reporting capabilities. Amplitude provides real-time tracking of user interactions and events, allowing users to monitor user behavior as it happens. It also offers real-time reporting options, providing instant insights into user actions. Flurry, on the other hand, has a slight delay in tracking and reporting, with data updates occurring at regular intervals rather than in real-time.
Data Privacy and Security: Amplitude and Flurry also differ in their approach to data privacy and security. Amplitude offers robust data privacy features, including user-level data access control, data anonymization, and compliance with privacy regulations such as GDPR. It also employs strict data security measures, including encryption and secure storage practices. Flurry, on the other hand, has more limited data privacy and security features, with less focus on user-level access control and compliance with privacy regulations.
In Summary, Amplitude and Flurry differ in data collection and storage, data analysis and visualization, integration and compatibility, user segmentation and targeting, real-time tracking and reporting, as well as data privacy and security.
I am trying to decide on a solution to better track our user data. We need to track which google ads are leading to signups, and which signups are performing various actions on the site. We then need to visualize this data in various ways. We also need to run A/B tests on features and content, to track which ones lead to the most paid conversions.
Functionally, Amplitude and Mixpanel are incredibly similar. They both offer almost all the same functionality around tracking and visualizing user actions for analytics. You can track A/B test results in both. We ended up going with Amplitude at BaseDash because it has a more generous free tier for our uses (10 million actions per month, versus Mixpanel's 1000 monthly tracked users).
Segment isn't meant to compete with these tools, but instead acts as an API to send actions to them, and other analytics tools. If you're just sending event data to one of these tools, you probably don't need Segment. If you're using other analytics tools like Google Analytics and FullStory, Segment makes it easy to send events to all your tools at once.
Another option you might consider is Google Analytics App+Web.
It is a new type of Google Analytics property which is event-based (like Amplitude and Mixpanel). In App+Web you can collect exactly the same data and in the same format as the other 2 tools mentioned.
The great things about it are: - it is free - there is a free integration with BigQuery (though you'll need to pay for BigQuery, but for most SmB's it is peanuts - $5-30 a month)
Not so great: - reporting side is pretty buggy (App+Web is very new).
So if you are ok building your reporting in something like Google Data Studio, App+Web will be a great option. Your data analyst will especially be happy to have all the data in SQL format (BigQuery).
If you choose App+Web, then you can use Google Optimize (also free) as an A/B testing solution.
Hello Ben,
I have been using Mixpanel and Amplitude and both of them are good solutions in order to track events on your product; events, funnel analysis, retention and so on. The most important thing is that you set up properly the taxonomy and naming convention of your events' structure. I don't have anything against Segment I tried once but I didn't work with that tool but it for sure is a good one based on other workmates' opinions. ¡Important! When tracking distribution channels, take into consideration the attribution channel and all the touches that the users do in all the channels before your conversions. Some of them are good to open a path and other ones good to close.
Besides that, for A/B testing there are several options in the market but VWO is a good one that with a lot of features to get good insights into the A/B testing. Another one could be Optimizely or Google Optimize. ¡Important! Some teams instead run A/B testing because sometimes that could be a technological issue, they run cohort tests, where basically they change features on the product and they analyse this performance with the new users and compare. That could have another issue like seasonality but it is another option.
Overview, I recommend Amplitude and VWO but just to make simple the answer, because Mixpanel, Segment and the other options that the other users wrote here are good too.
All the best, and let me know how your experience was with all these tools. :)
Cheers,