Firebase vs. Matomo Analytics

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.

Incentivized

If you want to balance data-driven marketing and a privacy-minded approach to analytics, Matomo Analytics is for you. It's easy to be compliant with GDPR and other regulations while still having detailed (anonymized) analytics that help inform what content is resonating vs what content is not resonating. And of course you also get all of the rich referral, campaign, and goal conversion data to help you optimize your marketing.

Incentivized

• 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).

Incentivized

• One of Piwik's strengths is the provision of customizable widgets for different bits of analytics data. The ability to add and remove them, change dates and more makes this a flexible way to visualize data.
• The visitor log section is also rich, providing date, keywords, actions and more in a single table, which makes it easy to identify your most effective content.
• And the visitor actions table includes both bounce rate and time on site, so you can quickly tell which pages have the most engagement.
• Data display is a strength for Piwik, as you have access to overview charts while simultaneously being able to drill deeper.

• 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.

Incentivized

• From a user security standpoint it would be useful to provide users the ability to have two-factor authentication. While stats data is not necessarily sensitive in aggregate, some users may feel that certain portions need to be more secure.
• It would be nice if there was a tighter integration with the Google search/referrer API so that "keyword not defined" would be replaced more often with the actual keyword that is being used to send a visitor to a site.
• An easier branding method, maybe in the form of an API function set, that pulled branding URLs from a set of database fields would be great as well.

At this point, there is not a single conceivable reason as to why we would not renew and continue to use Piwik Analytics. Especially since it is a free program and open source. The product will only get better over time as more people look into it and donate to cause so that development can continue.

Firebase functions are more difficult to use, there are no concepts of triggers or cascading deletes without the use of Firebase functions. Firebase functions can run forever if not written correctly and cause billing nightmares. While this hasn't happened to us specifically it is a thing that happens more than one realizes.

Incentivized

Piwik succeeds in presenting me (and my associates and my clients...) large amounts of data in a user friendly way. The interface and functionality can easily be customized. While some enhancements do need technical background (API calls by programming language from the webserver or javascript), others are easy to use (goal / event tracking)

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.

Incentivized

The best thing about the Matomo support is that they have a forum which basically you can find the answer to almost all of your questions and most of the time you don't need to contact them regarding your questions and problems but if you need help they will answer in a reasonable time slots.

Incentivized

Only one hiccup when we were using a beta installation. Other than that, smooth sailing.

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.

Incentivized

We have used Google Analytics before for one of our online tools and we switched to Matomo for the other web applications we have. We did that because Matomo is free but mostly since we wanted us to own the data on these sensitive apps and not share it with third parties. Since we have the data locally, we can now apply machine learning techniques to improve the systems even more.

Incentivized

• 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.

Incentivized

• By using Piwik, we can better identify keywords used to search for the website and by targeting those keywords on search engine advertising (Google, Bing, Yahoo), it helps with conversion and also saves us money by cutting down guess work.
• By using Piwik graphs, it helps to save our employees time in creating pie charts and bar charts to present to upper management.
• Since Piwik is free to use, there is no reason not to implement it. Most likely, with your website, you will already have access to SQL and hosting package. There is minimal cost to implementing Piwik.