Event tracking has transformed how we understand user journeys and improve product decisions
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using RudderStack for almost 18 months.
What do I think about the stability of the solution?
RudderStack is definitely stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
How was the initial setup?
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.
What about the implementation team?
I purchased RudderStack through the AWS Marketplace.
What was our ROI?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Data insights have transformed how we track booking rates and improve customer experiences
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What other advice do I have?
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.
Easy way to collect and send customer data
What do you like best about the product?
Setup was quick and the UI is simple. I connected sources and destinations without much help. It sends the same clean data to our warehouse and to our tools at the same time. The tracking plan keeps events consistent.
What do you dislike about the product?
You need to plan event names and properties well, or things get messy later. Debugging failed events can take a bit of time. Pricing can grow with high volume, so you have to watch usage.
What problems is the product solving and how is that benefiting you?
Collecting and sending customer data
Reliable, developer-friendly CDP that integrates seamlessly into the modern data stack
What do you like best about the product?
RudderStack makes it easy to collect, transform, and route event data to downstream tools like Snowflake, Klaviyo etc. Its warehouse-first approach aligns well with modern data workflows, and the open-source flexibility is great for teams that want more control. We’ve used it to unify customer behavior data across web and mobile into our analytics layer with minimal latency and strong governance.
What do you dislike about the product?
Setup can also be tricky without solid engineering resources on hand
What problems is the product solving and how is that benefiting you?
We’re using RudderStack primarily for website event tracking. It helps us centralize and route user interaction data to downstream tools like our data warehouse and analytics platforms. This setup gives us reliable, real-time visibility into on-site behavior without having to manage multiple custom tracking scripts, which improves data consistency and saves engineering time.
Smooth migration from Segment
What do you like best about the product?
Rudderstack does everything we need from a CDP while also utilising the investments we have made in our data platform. It's effectively the best of both worlds, end-to-end data collection, governance, and activation while being lightweight, flexible, and not over engineered. The migration was smooth and the UI is intuitive. We have also had a great experience working with the team and they deliver on their roadmap.
What do you dislike about the product?
Some of the initial Profiles and rETL setup was a bit fiddly but progress on the roadmap has resolved a lot of these pain points since we onboarded. We would still like even greater observability of data flowing through the pipes but that is also supposed to be coming soon.
What problems is the product solving and how is that benefiting you?
Rudderstack allows us to collect, govern, unify, and activate our user and customer data for a use cases covering omnichannel marketing and personalisation. Due to it's architecture we are able to do this more cheaply and efficiently than we previously experience when using a packaged CDP. The tool's ease of use allows us to bring data to business problems, often without the need for data engineering involvement.
Rudderstack as breakthrough for Data Tracking
What do you like best about the product?
What I like the most about Rudderstack is the simplicity with which different platforms can be connected, and the fact that an individual payload can be transformed on the fly and send to a wide range of destinations, including webhooks
What do you dislike about the product?
The User Interface is a bit confusing, especially when having a lot of source systems and/or destinations.
What problems is the product solving and how is that benefiting you?
Different destinations require different Payload schemas. With Rudderstack you can take the same source payload and modify it as you need
Great tool for event tracking
What do you like best about the product?
I really like RudderStack for several reasons. It’s cost-effective and incredibly easy to set up both sources and destinations once you get used to it. The built-in transformations are helpful, but the real power lies in the custom transformations—you can write your own logic in JavaScript or Python, giving you a high degree of flexibility to handle complex use cases. It also supports connectors for most of the tools we use, which makes integration seamless. Above all, the support team is outstanding—they’ve been consistently responsive and helpful whenever we’ve encountered issues.
What do you dislike about the product?
While RudderStack offers solid documentation, it can still take some time to figure out how to set up new sources, destinations, or transformations. Short instructional videos or quick-start walkthroughs would make the onboarding process much smoother, especially for new users. Additionally, while the platform is very developer-friendly—which is great—it can feel a bit overwhelming for users with less technical experience. A more guided UI or simplified setup paths could help make it more accessible to a broader audience.
What problems is the product solving and how is that benefiting you?
Helps us with processing events from various tools.
Solid, developer-friendly platform
What do you like best about the product?
RudderStack simply works. Its standard API made the switch from our previous provider painless, and the wide range of integrations covers all our current use cases. Advanced features—models, reverse ETL, and real-time transformations—give us ample flexibility, and technical support has been consistently responsive and effective.
What do you dislike about the product?
Non-technical (accounting / billing) support has been noticeably slower and less efficient.
What problems is the product solving and how is that benefiting you?
Centralizing all our analytics events flow into a single place.
Rudderstack is helping my company to implement great data solutions
What do you like best about the product?
Rudderstack tools make the life of the data engineers easier within its implementation and integration use cases. The customer support is also great. We use it on a daily basis
What do you dislike about the product?
Some tools don't have the option to customize 100% the functions yet
What problems is the product solving and how is that benefiting you?
Data Extraction from websites to a data warehouse and Customer Data Platform services within Profile Builder
Amazing Data Governance and rETL capabilities
What do you like best about the product?
They excel at making CDIs powerful and developer friendly and enable easy event tracking, unification, and activation. We also need the GDPR, and compliant solutions they offer.
What do you dislike about the product?
I do not have any cons - RudderStack gives us exactly what we need to do business. They require an initial setup but that’s what makes the tool powerful. It’s built for teams that value owning their data and pipelines end to end
What problems is the product solving and how is that benefiting you?
Our data is unified, and they allow easy event streaming across all of our tools. We had a previous solution in place and saved a large cost by migrating, and now we’re actually able to use all of the data we unify.
