Amplitude Analytics vs. ConfigCat

Amplitude Analytics is well suited for scenarios where you have multiple data points to understand customer behavior and journeys and utilize simple to medium complexity graphs/charts. It may not be suitable for scenarios where you need to slice and dice data into highly customizable dashboards as that requires significant effort from technical teams.

Incentivized

If you are looking for an experimentation/feature flag style tool that is quick to adopt and provides enough functionality for light/medium use cases, then this is the tool for you. Additionally, they are growing and expanding their functionality and feature set so they can grow alongside you and your needs. The publicly accessible roadmap is also a great benefit to see where time is being spent on which feature next.

• Feature analytics - measuring frequency of usage
• Time taken by users to convert in funnels
• Actions that drive certain user behaviors in funnels via correlation
• Actions that lead to user drop off in funnels via correlation
• Comparing behavior of two custom user cohorts

Incentivized

• Fast and easy feature toggling that gets developers developing
• World class support in both speed and quality for how to best use the service
• Great ear for customer needs and fast paced development

• Some more clarity and examples of implementation with GDPR in mind
• Some segregation inside user properties can be difficult to implement
• Splicing information inside funnels could be more intuitive
• User support for the cheaper tiers is hard to access
• Pricing transparency really needs to be improved

• No automatic push for flag changes - have to write our own webhooks
• No scheduling interface for flipping flags automatically on a schedule
• Interface is a bit cluttered for people who are just flipping flags

ConfigCat has done the job, and has been great to work with.

I haven't used the Amplitude support other than their training docs so I can't speak too much to the in-person support but the docs are serviceable. Nothing too crazy but between the user tips, email notifications, and the decent number of docs I was able to get the support I needed to ramp up on the tool.

Incentivized

They have a community Slack channel that is open to anyone. They always seem to have people in there, even over the weekends and are always happy to answer any questions you have,

It's the best in class with all the bells and whistles. Other options could suit you just fine at a lower price point, but you need to be sure of what you are not getting and the switching cost associated with when you do need it.

Incentivized

At iBinder we searched for and vetted several suppliers of a feature toggle service to handle feature toggling in our production environment. In addition to our functional requirements, it was crucial for us to find a partner that could deliver an EU-compliant service. We finally decided to sign a service agreement with ConfigCat. This has been a real success story for us – in addition to being compliant, ConfigCat delivers an amazing, flexible, and reliable service. They continue to impress by also being very transparent and having a fantastic support and they are very solution oriented and accommodating when it comes to our feature requests etc. We have now used ConfigCat for approximately 2 years and we give our warmest recommendations to anyone who needs a stable, reliable and EU-compliant feature toggle service.

• It collects data of great importance which allows to make product improvements.
• It easily identifies problems a user may have with the product.
• The flow of users who have used the product has improved, thus being able to generate more income thanks to the improvements and new functions.

Incentivized

• Allowed us to migrate seamlessly from a major customer communication system to another, reducing end-user friction and production bugs by being able to turn features off if they didn't work as intended.
• We went from zero experimentation to running 10-20 experiments concurrently across systems. Engineering teams are thinking in an experimentation mindset.