Why Amplitude is the Go-To Choice for Data Tracking at Fitbots...
4 min read

Why Amplitude is the Go-To Choice for Data Tracking at Fitbots...

Why Amplitude is the Go-To Choice for Data Tracking at Fitbots...
...when Compared to the Other Platforms Available.

With the increasing emphasis on data-driven product optimization, choosing an appropriate analytics platform has never been more important. At Fitbots, we overemphasize product optimization, but our core need is a suitable platform that gives us data insights at ease, but with precise accuracy. Amplitude visibly stood out as a perfect match to our needs.

With Amplitude, we can undoubtedly say that integrating data analytics into the product for features of varying complexities has never been easier than now.

How Did We Go About Choosing the Right Tool?

(Note: Here, we'll use Google Analytics, a widely known analytics tool for comparison.)

If analytics is the only ask, then GA will do just fine to monitor some high-level numbers for your website or app, like active users, etc. If you have a simple conversion funnel, for example, e-Commerce stores, GA would be a great choice in that scenario too. 

However, in order to assess if Amplitude is ahead of the game… Here are a few boxes that were checked off:

1. Product complexity and multiple possible ways for user interaction. 

2. Frequent product changes and the associated need for specific data capturing. 

3. Product is highly data-driven and has a high level of detailing introduced in it. 

4. If we want to track the behavioral drivers contributing to revenue or any other metric instead of the metric itself, which is overly complex and keeps branching as the product grows. 

There are were other key points that motivated us to go for Amplitude: 

1. The Amplitude model of unlimited events. This comes in handy while experimenting and figuring out the behavioral patterns of users across our product before we can start getting any actionable data out of it. 

2. In-Built support for complex funnel analysis to capture various user journeys. 

3. Highly customizable user segmentation. 

4. Above and beyond support for various tech stacks and the ease of implementation, all it takes to register an event is an API call with no configuration at all and no SDK nightmares.

5. Ability to transfer our data from any other analytics tool directly into Amplitude 

Let’s get a bit more technical!

Wondering how one would go about registering events in Amplitude? There are primarily two ways to get data onto the platform.

1. Import Data From Other Platforms. 

When migrating onto a new platform, data-transfer compatibility issues often arise, 

be it for completely migrating onto the new software or using it in tandem with the existing ones to boost efficiency. Even if any organization wants to try out the new tools they find it almost impossible to do so with the existing data that they have at hand in other legacy software. So to tackle this issue, Amplitude provides a wide range of data importing capabilities from many platforms like that.

Some of the platforms that Amplitude supports are: 

  • Adjust 
  • Adobe Launch 
  • Airbridge 
  • Amazon 
  • AppsFlyer 
  • Branch 
  • Braze 
  • Convizit 
  • Google Play 
  • Google Tag Manager 

2. Use Event-driven Data Capturing From Within the Product.

According to current stats, most of the businesses that are doing some sort of data tracking in the industry, are doing it for the first time. This means they don’t have the data with them, therefore data will be collected from the users using their services.

The most common type of data tracking is Event-driven in which a data point is saved with a bunch of information on some action that the user performs on the platform.

Now there were two approaches available for us:


a) Using technology-specific SDKs 

b) HTTP API driven 

We decided to go for HTTP API, mainly because the implementation is way faster than SDKs and we wanted to have the liberty of registering events into Amplitude from anywhere in our tech stack – front-end, back-end, and in some scenarios, even from Cloud while maintaining consistency in the implementation. Maintaining an API call and keeping up with the updates can be done with minimal effort. 

We took a slightly different approach wherein, instead of calling the Amplitude API right from the front end, we decided to take it to the back end. This decision was taken primarily due to these reasons:

  1. Keeping the core API in one place and wrapping it with our own API gave us the ability to modify it at our will without affecting the implementation.

  1. By doing this, we came over the whitelisting issue: many organizations have a very strict policy when it comes to where their data can flow from internal sources, therefore they only allow some specific domains on their networks. Additionally, it is impractical to ask every user to whitelist some domains every time we use a 3rd party tool on our platform.

They have detailed Documentation on how to use the HTTP API.

Note -> 

Some hiccups arose at the beginning like data not being populated inside Amplitude in some predefined fields while implementing the API. Please refer to this Documentation to get around some of the common issues.

How does Amplitude Help With Easy Filtering and Data Visualization?

Collecting data from sources is only one part of the whole process. There is also a need to have an efficient way to analyze that data and derive some insights from it to steer the product. 

This is where Amplitude shines the most since it already has a lot of preconfigured data segmentation and configurations. Some examples are - Funnel, User Sessions, Segmentation, Life Cycle, and many more. 

Let's take the example of Life Cycle.

A Life-Cycle analysis breaks out your active users into new, current, and resurrected categories, alongside offering a count of your churned users. 

Image Source - Amplitude

These properties are based on the predefined parameters that we provide while calling the API. We can plot charts based on the custom data that we send in the Payload. They also provide a feature for configuring custom formulas, which gives us Excel-like freedom and the ability to transform and visualize our data as we wish. 

Image Source - Amplitude


We can compare the current data with historical data right there on the same chart with different kinds of charting like stacked, pie, histogram, etc. 

Our Experience with Amplitude

We faced various challenges regarding the feature usage, their usage frequency, what features were not being used at all, and most importantly the user behavior throughout the platform.

Amplitude was the solution to all these challenges. One such use case (where we modified our product based on the analytics data) was when we had to decide what the default states of the features in our product would be.

Which data-display type did users prefer - tabular or separate card view? What we speculated in the initial release was to go with one method as default. Looking at the data helped us realize that there is no one majorly preferred method, therefore, we changed our model to a preference-based setup. Where we save the data in cookies on how a user wants to view the UI of a particular page, the UI will be displayed accordingly based on the saved data the next time a user visits that page.

Finally, considering all the features and functionalities that Amplitude gives us, aside from the ease with which we can analyze our data, makes it a very promising choice over any other product out there – especially for a high-growth team with limited bandwidth.

Get OKRs right with Fitbots OKRs_OKR software free trial

About the Author

Vaibhav Chauhan is a product engineer at Fitbots. He is a Product-oriented developer and loves all things tech.


eBooks on OKRs

Book a demo