Share your experience using Leadfeeder

The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.

Use our online form to submit your review. It's quick and you can post anonymously.

Your review helps others learn about this solution
The PeerSpot community is built upon trust and sharing with peers.
It's good for your career
In today's digital world, your review shows you have valuable expertise.
You can influence the market
Vendors read their reviews and make improvements based on your feedback.
Examples of the 83,000+ reviews on PeerSpot:

LeslieTaylor - PeerSpot reviewer
Consultant at Pyramid Consulting
Real User
Offers depth of analytics and powerful visualization capabilities
Pros and Cons
  • "I loved using Amplitude because it allowed me to dive deep into product usage and analyze different customer segments."
  • "Setting up reports in Amplitude was challenging for me as a newer user."

What is our primary use case?

I used Amplitude mostly for data analytics and analysis.

What is most valuable?

I loved using Amplitude because it allowed me to dive deep into product usage and analyze different customer segments. My favorite part was pinpointing exactly where customers were dropping off in their journey and understanding the events tied to conversions. This helped me focus on areas needing improvement, conduct customer interviews, and validate insights with existing reviews, leading to more informed decisions.

What needs improvement?

In terms of improvement, setting up reports in Amplitude was challenging for me as a newer user. I relied on others who had specific knowledge, which sometimes caused delays due to resource constraints. It would have been helpful if the process of creating reports was more intuitive and user-friendly, allowing me to gain insights independently without relying heavily on the product team.

For how long have I used the solution?

I have used Amplitude for a year and a half.

What do I think about the stability of the solution?

Amplitude was very stable during my use. I never encountered any errors, which was refreshing compared to the occasional issues I have experienced with AWS products.

What do I think about the scalability of the solution?

I would rate Amplitude a solid ten for scalability. I didn't see any reasons why it couldn't handle scaling effectively.

Which solution did I use previously and why did I switch?

Amplitude is easier to use than Splunk because its user interface is more intuitive and user-friendly. Splunk's interface felt technical and outdated, like an old mainframe system, while Amplitude's was much easier to navigate. Although Splunk might excel in detecting anomalies, Amplitude provided a smoother experience, especially for tasks like tracking performance over time.

How was the initial setup?

Setting up Amplitude initially can vary in complexity. If you have all the necessary information, like event IDs and customer lists, and your requirements are straightforward, it's relatively straightforward. However, the complexity increases with more variables and larger datasets, making it a bit more challenging to work with.

What other advice do I have?

Amplitude played a crucial role in improving product decisions for our onboarding project. By analyzing user behavior, we identified key points where customers were dropping off in the activation process. This allowed us to tailor the onboarding experience, making it more personalized and engaging, resulting in higher activation rates and improved customer retention.

Integrating Amplitude with other tools in our stack improved our analytics capabilities. I didn't encounter any issues with its compatibility or functionality alongside other tools.

I would recommend Amplitude to others because of its depth of analytics and powerful visualization capabilities. Overall, I would rate it as an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Avijit Bhattacharya - PeerSpot reviewer
Senior Data Engineer at Warner Media Discovery
Real User
Robust data warehousing capabilities with seamless scalability and support for both structured and semi-structured data, although its user interface and customer support may require improvement
Pros and Cons
  • "The Snowflake features I find most beneficial for data analysis are primarily related to analytics, particularly their features like materialized views and queues, which are especially useful for dashboarding purposes."
  • "The scheduling of jobs requires improvement, particularly in terms of the user interface which currently lacks certain features found in comparable platforms."

What is our primary use case?

We use it in the process of collecting access revenue data from various vendors. Our next step involves integrating this data into Snowflake tables, after which we present it through dashboards for visualization and analysis.

How has it helped my organization?

Snowflake Analytics serves as the primary data repository, fulfilling the data warehousing requirements of our customers. Therefore, all incoming data from our vendors is stored within Snowflake as part of our data warehouse.

Snowflake Analytics efficiently handles large-scale data analytics, which has been crucial for managing our current database volume. We're satisfied with the refresh rate and the loading process of new data into the tables, as it aligns with industry standards, leaving us with no complaints in this regard.

We have designated specific roles for administrative tasks, which are concealed from regular developers and production support personnel. Access control mechanisms are employed to grant access only to individuals who require it for administrative purposes, and they are the biggest benefits.

The transition to Snowflake has impacted our customers' overall data strategy and cost management significantly. Initially, we were using Redshift with AWS integration, but encountered challenges with scaling and compute costs. High data volumes led to increased costs for the entire solution. Therefore, we migrated to Snowflake, resulting in a reduction of costs by approximately thirty percent.

What is most valuable?

The most valuable features primarily revolve around data ingestion, such as copy commands. Additionally, we find Streams to be particularly useful in our operations, as they provide convenient functionalities.

The Snowflake features I find most beneficial for data analysis are primarily related to analytics, particularly their features like materialized views and queues, which are especially useful for dashboarding purposes. Another noteworthy addition is their new solution, hybrid tables.

What needs improvement?

The scheduling of jobs requires improvement, particularly in terms of the user interface which currently lacks certain features found in comparable platforms.

For how long have I used the solution?

I have been working with it for three years.

What do I think about the stability of the solution?

In terms of stability, over the past three years, we haven't experienced any glitches in the production environment such as database unavailability. We have had a consistent and reliable performance without any issues, so there are no complaints in this regard. I would rate it eight out of ten.

What do I think about the scalability of the solution?

It provides excellent scalability. I would rate it eight out of ten. The majority of our current clientele utilizes Snowflake, comprising approximately fifty to sixty percent of our client base. The rest of them still operate on legacy systems, with a gradual migration process underway. Our customers are enterprise businesses. 

How are customer service and support?

If I were to rate the support on a scale of one to ten, it would fall around six. Occasionally, there are delays in receiving responses, while at other times, we receive prompt assistance.

How would you rate customer service and support?

Neutral

How was the initial setup?

The initial setup is complex and can be challenging to configure. I would rate it three out of ten.

What about the implementation team?

For a medium-complexity dashboard, the deployment process typically takes around an hour to implement all the features. This estimate applies to mid-range features, excluding high-end functionalities. Our deployment process utilizes Git actions, seamlessly integrated within Git. Each deployment involves creating a pull request, through which Git actions are triggered to deploy changes to the master branch.

What's my experience with pricing, setup cost, and licensing?

The pricing is on the higher side. I would rate it seven out of ten.

What other advice do I have?

Since Snowflake primarily functions as a data warehouse, it is well-suited for OLAP solutions. Despite incorporating some OLTP features, Snowflake remains best suited for OLAP purposes. My advice to anyone considering Snowflake is to carefully evaluate the cost in comparison to their current solution. They should assess whether they would derive significant benefits from switching to Snowflake, especially if they are currently using platforms like Databricks or BigQuery. Comparing costs beforehand is crucial before making the transition to Snowflake. Overall, I would rate it seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: integrator, consultant
Flag as inappropriate