Google Optimize is well suited for testing small changes on the browser pages. You have the option of changing designs, texts, and some small features on the page. The audience can be divided using a long list of factors, so it makes it quite easy to set up the test. It is not well suited for complicated feature tests where you need to monitor the user over a long period or where the user is likely to use multiple sessions across multiple devices or browsers
Statsig is well suited for running straightforward a/b tests on frontend deployments. We've actually used it to log events on our backend and used the HTTP API to integrate with tools like Hubspot to evaluate email campaigns
For the most part it is pretty easy to use. - There are some quirks with the javascript SDK (getExperiment().getValue?). - The Events vs. Metrics design pattern is complex, and creating new Metrics from Events can be frustrating if you are trying to use event metadata - It's really frustrating not to be able to link Static IDs (before a user signs up) to User IDs, in order to follow users all the way through onboarding, or to log events that occur for signed in users when you are exposing the experiment to users before they've signed up
We switched from Google Optimize to AB Tasty which is a paid platform. AB Tasty provides much better capabilities and support, although this is with a cost implication which Google Optimize didn’t have. Google Optimize was useful as an introductory platform prior to getting a full programme running but this has now sunset so is no longer available.
Useful with clients on a budget who need to see ROI without another paid platform to install.
Setting up Google Optimize helps as an additional value add when bidding on projects.
Nothing negative unless a larger client needs a more robust package; then, there is always Google Optimize 360 as well as platforms from other vendors.
