Snowplow could be improved in a couple of areas. The Snowplow team is readily available and proactive, always jumping on calls to make changes, especially how we track consent and non-consent data for the EU market. One area of improvement could be its vast canvas, which might feel overwhelming and confusing to people who are less technical or are not sure how to best structure their data. Although Snowplow is powerful, getting value from this granular event data does require strong SQL skills and knowledge of the underlying data model. Therefore, making the data more accessible to less technical users could enhance intuitive self-service exploration, funnel visualization, and easier debugging of tracking issues, allowing product teams to gain insights without relying heavily on analysts. Snowplow could also automate most processes and implement smarter monitoring alerts for fallback. Better documentation and easier debugging when event tracking or schemas change would help, given that managing event definitions centrally can be a hassle when there is a breaking change. Having automated systems to inform users about changes in events or properties would make things smoother across teams.
I do not have many improvements to deliver for Snowplow. Perhaps for smaller companies that do not need to customize so many things would be helpful. In the beginning, we also did some things wrong. The data model that we used was not as clean everywhere we were tracking. We made some mistakes, but I think we learned from them, and perhaps for smaller companies that start now, it could be made a little bit easier, although I think Snowplow has already worked on that.
Web Analyst at a media company with 1,001-5,000 employees
Real User
Top 20
Apr 30, 2026
Honestly, I don’t have any real complaints. Snowplow has been great, especially the support they gave us during the initial implementation. They had a few "old school" approaches to data schemas early on, but they’ve already deprecated those and moved in the right direction. It feels like a truly state-of-the-art setup now. It’s actually pretty tough to come up with constructive feedback because I’ve been so happy with how everything works.
Snowplow is a data collection platform known for its ability to gather rich, event-level data across websites and applications in real-time, offering unique insights and advanced analytics capabilities for users.Snowplow provides a powerful framework for capturing and managing complex data streams. Its architecture supports the collection, storage, and processing of high-quality, granular data. Users benefit from the high level of detail it provides, which enables sophisticated analytics and...
Snowplow could be improved in a couple of areas. The Snowplow team is readily available and proactive, always jumping on calls to make changes, especially how we track consent and non-consent data for the EU market. One area of improvement could be its vast canvas, which might feel overwhelming and confusing to people who are less technical or are not sure how to best structure their data. Although Snowplow is powerful, getting value from this granular event data does require strong SQL skills and knowledge of the underlying data model. Therefore, making the data more accessible to less technical users could enhance intuitive self-service exploration, funnel visualization, and easier debugging of tracking issues, allowing product teams to gain insights without relying heavily on analysts. Snowplow could also automate most processes and implement smarter monitoring alerts for fallback. Better documentation and easier debugging when event tracking or schemas change would help, given that managing event definitions centrally can be a hassle when there is a breaking change. Having automated systems to inform users about changes in events or properties would make things smoother across teams.
The setup process is an area for improvement because getting the pipeline infrastructure right is hard.
Snowplow can be improved by reducing the pricing, as it is currently too high.
I do not have many improvements to deliver for Snowplow. Perhaps for smaller companies that do not need to customize so many things would be helpful. In the beginning, we also did some things wrong. The data model that we used was not as clean everywhere we were tracking. We made some mistakes, but I think we learned from them, and perhaps for smaller companies that start now, it could be made a little bit easier, although I think Snowplow has already worked on that.
Honestly, I don’t have any real complaints. Snowplow has been great, especially the support they gave us during the initial implementation. They had a few "old school" approaches to data schemas early on, but they’ve already deprecated those and moved in the right direction. It feels like a truly state-of-the-art setup now. It’s actually pretty tough to come up with constructive feedback because I’ve been so happy with how everything works.