Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
$0.01
Per Verification
Localytics
Score 6.0 out of 10
N/A
Upland Localytics helps you connect with mobile app customers on a deeper, more meaningful level.
$95
Per Application Per Month
Twilio Segment
Score 8.3 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…
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 …
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
For the price and the features available, Localytics is one of the best options. It is more robust in areas that we don't need it to be and overall there could be simpler flows for sending push notifications or performing actions that you need to do every week. Also, the data it sends back on how push notifications perform is basically useless. There needs to be more explanation on the impact notifications have on users. The data would always say that notifications drove less engagement but we would see engagement go up every time we sent a notification.
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
Analytics wise, retention is extremely important to our app, therefore we take advantage of the cohort analysis to see the impact of our middle funnel (retargeting, push, email) efforts affect the percent of users that come back into the app. Firebase allows us to easily segment these this data and look at a running average based on certain dates.
When it comes to any mobile app, a deep linking strategy is essential to any apps success. With Firebase's Dynamic Links, we are able to share dynamic links (recognize user device) that are able to redirect to in-app content. These deep links allow users to share other deep-linked content with friends, that also have link preview assets.
Firebase allows users to effectively track events, funnels, and MAUs. With this simple event tracking feature, users can put organize these events into funnels of their main user flows (e.g., checkout flows, onboarding flows, etc.), and subsequently be able to understand where the drop-off is in the funnel and then prioritize areas of the funnel to fix. Also, MAU is important to be able to tell if you are bringing in new users and what's the active volume for each platform (Android, iOS).
Multi-platform. Segment has easy integrations in many different web, backend, and app platforms/frameworks. We use the Segment SDK in Android and iOS as well as our node.js backend.
Segment is fairly affordable for early-stage companies that are trying out different analytics software. The "developer" plan is free and is suitable for most companies with products that have a small user base.
The UI is great! It is extremely intuitive and easy-to-learn, and this made it take very little time to integrate this software into our analytics and marketing workflows.
Attribution and specifically multi-touch attribution could be more robust such as Branch or Appsflyer but understand this isn't Firebases bread and butter.
More parameters. Firebase allows you to track tons of events (believe it's up to 50 or so) but the parameters of the events it only allows you to track 5 which is so messily and unbelievable. So you're able to get good high-level data but if you want to get granular with the events and actions are taken on your app to get real data insight you either have to go with a paid data analytics platform or bring on someone that's an expert in SQL to go through Big Query.
City-specific data instead of just country-specific data would have been a huge plus as well.
The biggest thing I would like to see with Localytics is the capability for more correlations. The limited amount of correlations available does restrict the type of analyses that could be done with the data.
An easier interface to move data into Microsoft Excel would be very useful, rather than creating annoying workarounds.
More/better automatically scheduled reporting, as well as an Excel plug-in to access the data rather than being restricted to the Localytics interface.
More and richer sources. For example, MailChimp is a source but the data you get from MailChimp is quite limited. I ended up writing my own scripts to take better advantage of MailChimp's API because Segment's integration was lacking.
Better examples on how to set up event tracking. Pageview tracking is easy enough, but it would be nice if they had a sample app and corresponding code for it and showed you, via Git commits, how to add various kinds of events.
I don't use the Firebase UI much, but rather connect it to GA4. GA4 has a great event model but the GA4 UI and analysis capabilities are limited. It's harder to measure product usage type of engagement but if you have the time and resources to leverage the GA4 to BiqQuery export you'll have all the raw event data you'll need for deep analysis, segmentation, and audience activation.
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
It would take several weeks to hear back from the billing team. It took 3 months to resolve an invoice last year. Their technical support is very responsive. I would typically get a response in under 24 hrs.
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.
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
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 user interface to use depending on circumstances and requirements.
Makes building real-time interfaces easy to do at scale with no backend involvement.
Very low pricing for small companies and green-fields projects.
Lack of support for more complicated queries needs to be managed by users and often forces strange architecture choices for data to enable it to be easily accessed.
Segment has enabled us to get a full view of our front end activity, join it to our back-end activity, and get full visibility into our funnels and user activity.
Segment lets us send events to ad tools with a full audit trail so all the numbers line up.
Segment also brings data from other sources into our data warehouse, saving our data engineering time from building commodity connectors.
