RudderStack Reviews

My major use case for RudderStack is streaming the event data from our website and mobile apps to our analytical database, or destination database, and afterwards, we are preparing our BI or analytics over the events that we captured using RudderStack.

Apart from it, we are preparing some user journeys and funnels through RudderStack events, making it a very helpful tool.

We captured events mainly from our major funnels through RudderStack. For example, we have a sign-up funnel, KYC funnel, order funnel, and repeat order funnel. We placed some events at different points across the journey on our website. Whenever users interact with specific points on the website, we capture their presence. Afterwards, we try to map those events with the timestamps and the session ID provided by RudderStack, which is one of the most important features, allowing us to see where users are when they drop off and better our product.

RudderStack provides a platform to ensure product quality and understand user behavior, allowing us to improvise and optimize our product. The tracking plan feature provides an optimized version of the events in a semantic way, which is very helpful. The default attributes such as page attributes, page properties, operating system properties, context traits, and user traits are also major aspects we use across events.

Overall, RudderStack is a good tool. Additionally, I believe that organizations not using the high-price version of RudderStack should have access to the event audit API, which I consider one of the most fantastic features that every organization should have to track their events. A basic versioning of the event audit API or allowing stakeholders to upload event schemas via CSV to the tracking plan would be very helpful, but the tracking plan feature itself is fantastic.

The best feature RudderStack offers is the analytics over the past two days, past seven days, past 30 days, or however much event volume has occurred in those windows. Other major features include the tracking plan feature, the code-generation feature, and the event audit API feature, all of which are very helpful across RudderStack.

The best feature I rely on the most in my daily work is the volume of events in a specific time window, which I check every two hours during working hours. This feature gives me an idea of how my website is performing, the traffic flow during working hours, and alerts me if something breaks based on the event volume.

RudderStack has positively impacted our organization by opening the door to tracking user journeys across the platform, understanding user performance and behavior, and assessing how well our product is doing. It helps us measure the impact of different features on our product.

RudderStack has helped us reduce errors by revealing where users get stuck in their journeys, allowing us to improve our product and reduce manual efforts. If we understand user performance, we can optimize our product to reduce friction at key success points.

RudderStack should work on its sync time; currently, the minimum sync time for injecting data into warehouses is about 30 minutes. I think it should be reduced to about five to ten minutes so that the BI team does not have to wait so long for insights on the user journey.

Another improvement I have mentioned is including the event audit in basic or starter plans, making it accessible for smaller organizations with lower budgets.

I have been using RudderStack for almost 18 months.

RudderStack is definitely stable.

On scalability, I believe RudderStack is already more than capable without requiring version upgrades. It handles multiple tasks simultaneously without lagging or latency issues, indicating its good scalability.

Customer support has been good in our case. Whenever we face issues or have questions, our customer support agent returns to us within two business hours. We have not encountered difficulties with customer support previously, so I think it is good.

Positive

I cannot comment much on the pricing, setup cost, and licensing since I am not the right person to answer that question. However, I can say, in comparison with other market-standard tools that I am not too familiar with, people often say that RudderStack is a value-for-money tool. It has been a good experience.

I purchased RudderStack through the AWS Marketplace.

I have seen a good return on investment with RudderStack, as it gives me valuable insights into my product and user behavior. I believe I am getting a good return on the investment I have made in RudderStack. I can comment on two metrics: time saved and better insights I gained using RudderStack. In terms of time saved, I do not need to contact each user to understand their journey anymore; I can see the metrics or funnels from RudderStack directly. Regarding insights, RudderStack provides ample information on performance and areas needing attention.

While choosing RudderStack, we did not evaluate any other options. We found that RudderStack was suitable for our specific use case through public community recommendations, so we decided not to delay our decision by researching other tools.

I would recommend RudderStack to my community if someone asks me for solutions related to the issues I have solved with RudderStack. I would definitely advocate for RudderStack.

I advise anyone looking into using RudderStack to choose it if they are seeking a tool that effectively captures events, tracks user journeys, and evaluates products. RudderStack offers good value for money regarding scalability, stability, reliability, and features, so I positively recommend people use it and provide feedback based on their experiences.

I provided a review rating of 10 for RudderStack.

My main use case for RudderStack includes event collections and customer unification for 360 profiles.

RudderStack has impacted my organization by allowing us to integrate our customers and providing scalable visibility into the activities within our system.

RudderStack allows for a smooth integration of customers from several sources, approximately seven in total.

The best features of RudderStack for my setup are identity stitching and event collections from different sources, which end up getting used the most.

The biggest friction point or frustration I have encountered with RudderStack is documentation and updates to the releases.

I wish RudderStack had a better transformation framework.

If I could change just one thing about RudderStack that would make the biggest difference in my workflow, I would say a more predictive monitoring of the event workstream would reduce the number of alerts we receive.

I have been familiar with RudderStack for almost three years.

Our team did not need any formal training as it was intuitive, but we actually received support from RudderStack as part of the purchase.

Before I landed on RudderStack, I was partially using Snowplow.

I decided on RudderStack specifically over continuing with Snowplow because it was cheaper, simpler to use, and easier to manage.

When I first implemented RudderStack, it took a few weeks to get up and running.

The scope of that setup involved a small part of the data team, but there are many source systems.

The adoption of RudderStack has gone well since the whole company uses data from it, and we primarily have one type of user that generally builds the integrations, along with one or two administrators.

I did not consider any other tools alongside RudderStack.

The product I want to review is RudderStack, the customer data platform and event pipeline tool. My advice to someone considering RudderStack who has a similar workflow to mine is to try the open-source version if you have doubts and then see if it is a fit. I would rate RudderStack a nine on a scale of one to ten.

My main use case for RudderStack is for aggregating customer data from different sources and getting them into a single data set.

For example, I connect data from a Shopify store, a landing page, and a mobile application, collecting all of them into BigQuery and connecting user profiles.

The best features RudderStack offers include that it's open-source, it has a lot of data sources and sinks, and there are transformations I can apply to the data, along with a live explorer where I can analyze the data coming in real time.

My favorite feature out of those is the live explorer because it helped me a lot in debugging some of the data pipeline issues.

RudderStack has positively impacted my organization by helping us unify our user profiles across different channels without a lot of worry, such as connecting users visiting our landing page and our Shopify store, which really helped us drive better analytics and improve our targeting and marketing.

I noticed specific improvements in our analytics after implementing RudderStack; before, we had a lot of fragmented data points which were not unified, and after using RudderStack, we were able to unify all the events for a single user.

RudderStack could be improved by making the SDK easier to use; I had a lot of problems integrating it into our Shopify store, so that is one area which needs improvement.

I have been using RudderStack on and off for about three years.

I find RudderStack to be stable.

RudderStack's scalability is pretty good.

The customer support is pretty much nonexistent.

I previously used Segment as a different solution.

I switched from Segment to RudderStack because it was not open-source.

RudderStack is deployed in my organization as self-hosted on a private cloud.

We use AWS as our cloud provider.

I did not purchase RudderStack through the AWS Marketplace.

My experience with pricing, setup cost, and licensing was smooth.

My company does not have a business relationship with this vendor other than being a customer.

I have seen a return on investment because it saved us time.

I would estimate it saved our team about 10 hours a month.

Before choosing RudderStack, I did not evaluate other options.

On a scale of one to ten, I would rate RudderStack a seven.

I choose seven because it is a good platform, but the non-open-source alternatives are easier to use, such as Segment.

My advice to others looking into using RudderStack is to use it.

I would rate this product a seven overall.

My main use case for RudderStack is creating dashboards and analytics.

A specific example of how I use RudderStack for creating dashboards and analytics is calculating booking rates, where we store the data in our database regarding jobs booked for certain people, and we have linked it with RudderStack to see the analytics for the rate or for the percentage of calls that are being booked, the percentage of calls which are being dropped off or those that are not booked. Based on that at a customer level, we are seeing the rates at which we are generating leads, the booking rate for different customers, and so on.

In my previous company, we used to create custom customer-specific dashboards with RudderStack where we would track all the metrics for the customer, and that used to help us find any anomaly or gain certain insights which were useful for us to improve the experience of the customer and improve our product through it.

The best features RudderStack offers include table joining features, creating dashboards and analytics, and metrics.

The table joining feature in RudderStack helps us because we have certain data spread across multiple database tables, and there is no direct tool that we can use to actually combine certain things and query on top of that and visualize it or transform it into a dashboard or a table. RudderStack usually helps us to do that. Regarding metrics and analytics, it is mostly for different use cases, such as getting the booking lead percentage, understanding where the user is dropping off, counting certain things, or tracking certain customer behavior. So for those purposes, analytics, metrics, and dashboards are valuable.

RudderStack has positively impacted our organization by helping us keep our customers happy because we are able to track the data, and according to that, we are improving the product and the experience of the customer. So if our customers are happy, the organization is also happy and positive as well.

I cannot think of anything major that RudderStack can be improved on right now. I cannot really think of anything small or a feature that could make my work even smoother as of now.

I have been using RudderStack for two to three years at my previous company, whereas in this one, we have started a few months back, so it has been six to seven months.

My advice to others looking into using RudderStack is to just go for it if you are looking for dashboards and analytics that can be run on top of different databases.