Crashlytics is a mobile analytics tool which helps users find the exact line of code that their app crashed on, providing granular insight into mobile app performance and user experience. Crashlytics was acquired by Google in 2017 and is now offered as part of the Firebase product.
N/A
Twilio Segment
Score 8.4 out of 10
N/A
Segment is a customer data platform that helps engineering teams at companies like Tradesy, TIME, Inc., Gap, Lending Tree, PayPal, and Fender, etc., achieve time and cost savings on their data infrastructure, which was acquired by Twilio November 2020. The vendor says they also enable Product, BI, and Marketing teams to access 200+ tools (Mixpanel, Salesforce, Marketo, Redshift, etc.) to better understand and optimize customer preferences for growth— all integrations are pre-built and…
Truly speaking, it is also a quite good tool for crash reports, but Firebase Crashlytics was better to use when you are using the Firebase Realtime database as your DB, so the integrations become much easier.
As mentioned previously, the only realistic competitor to Crashlytics is Instabug (backed by Y Combinator in the W16 class). While Crashlytics is focused on actual crashes, Instabug's main innovation is in collecting feedback from users for non-crash bugs. While non-crash bugs …
Based on what our developers have told me, Crashlytics is better than anything else out there. I personally have worked with Flurry for event and crash monitoring, and my experience was terrible. I know some project teams have tried some alternatives in the space that I don't …
Compared it with Crittercism on a Xamarin project a while back and on that platform, Crittercism was the best. But on Android, Crashlytics is just a lot better in providing good stack traces and having a useful analytics console. It's pretty much the defacto standard on …
Mixpanel and Amplitude offer strong data analytics and Google Analytics is powerful for web data, but their integration capabilities are less extensive compared to Twilio Segment. It's easy-to-use api and data collection and cleaning capabilities Twilio Segment operates as a …
We chose Twilio Segment for the good API integration and node resources, I would use Ontraport again, particularly if I didn't have the requirements for API and development/platform integration. Certainly the set up and management is easy and seamless with both the API and the …
Tealium was slow to set up and unreliable. It has better pricing but took significantly more Dev time to implement. We also could not debug issues and their support was slow to assist.
Segment is considerably cheaper but doesn't have the GUI for non-SQL users. GA Premium doesn't have all the data connectors, and can be more difficult to configure on SPAs.
I'm not sure these are "official competitors" (or alternatives) to Segment, but we use them in parallel for different goals. We use Datadog for logging and monitoring and we use Mixpanel to perform data analysis based on the data we gather using Segment (and other sources). I …
We tried to set up our entire data analytics process through these tools but there were some parts of the data capture, set-up, analytics that was missing with these tools. None of them could provide the ease of setting up with a complete picture of the data and analytics like …
It's much more personalized and user-focused data available in real-time, and immediately exported to an external database. It's provided more control over how the information is used and displayed for actionable insights.
Segment is not really suitable for most websites that have more than 10k MTU - If you run a semi-popular website, there are many tools out there that will do basic web analytics, like Google Analytics. Google Analytics provides simple resources for tracking user growth, …
The competitors above either charge a lot if you want to warehouse your data, don't allow data warehousing, or make it very difficult to warehouse your data (requiring you to write custom scripts and run them on schedulers). Segment makes it easy to warehouse your application's …
See my previous response. Google Tag Manager is great if you are firmly in the Google ecosphere. But they don't have as many integrations as Segment.io
Looked at Google Tag Manager, but too complicated. Segment.io mostly competes with each individual martech tool of implementing all the event tracking yourself for each tool.
Firebase Crashlytics is a no-brainer if you are already using any of the other Firebase suite of products, as its integration is very easy if you are already using these in your app. If you have cross-platform Android, iOS, and macOS apps, you should also consider Firebase Crashlytics to provide a unified across your platforms. If your app is only on Android or only on Apple, then you may be better off remaining with the default Apple Developer or Google Play Developer Console crash collection experiences.
Best suited: - Merging emails coming from: Facebook leads forms, Unbounce or landing pages forms, Google forms, any other kind of lead generation tool and bundling all that information together for a single user "profile". - Passing events generated in multiple applications by the same user (product selected in web, product discarded in cart, etc) and delivering those events into other applications (like a CRM) Less appropriate: - Reading/updating data directly from segment from a frontend application
Potentially, it could "warn" the developers/product about areas in our code that are not covered by events (and let us decide if it's "be design" or we missed it).
It's difficult to get accumulated history data exported out in order to analyze it.
There's no easy way to compare data from 2 sources (our main target is to compare the same events between our test environment and prod environment).
It is very easy for non-developer staff to use the Firebase Console and gather information for the development team. Developers will find it straightforward to integrate Firebase Crashlytics into new or existing codebases using Google's in-depth developer documentation. I cannot think of an easier cross-platform solution to use, and because of that I wish it supported more platforms!
Over the period it took us to set up, we kept going back to their enablement team to help us with the setup, and they were always ready and were very helpful in the entire process. Even with their documentation, they took the time out to help us work through the process. We've never had a message/email unanswered for more than an hour on working days.
Compared it with Crittercism on a Xamarin project a while back and on that platform, Crittercism was the best. But on Android, Crashlytics is just a lot better in providing good stack traces and having a useful analytics console. It's pretty much the defacto standard on Android...everyone uses Crashlytics. It's even more common to use Crashlytics and the Firebase crash tracking; Firebase does track ANR's a lot better though.
Segment is not really suitable for most websites that have more than 10k MTU - If you run a semi-popular website, there are many tools out there that will do basic web analytics, like Google Analytics. Google Analytics provides simple resources for tracking user growth, demographics, and conversion rates of websites, which is more suitable for companies that are looking for simpler analytics data.
Event tracking lets you take ownership of your own data, which in part makes it easy to craft metrics and do deep dives to see how your product is working. This has a huge ROI, because without metrics you're basically flying blind.
You can also use Segment's event tracking to fuel your experimentation and AB testing strategies. AB testing is the best way to ship features in a tech product with confidence that you're making a positive impact.