Here, we can see the various use cases for Full Stack. Though you can certainly run A/B tests and personalization campaigns in Full Stack, these use cases are how we see developers using full stack primarily.
Above, we can see how Full Stack is deployed on the server side, while below, how Full Stack can be used as a client-side solution. Our tool is called Full Stack, and not "server-side tool", for a reason: you are able to track events in the client while making decisions in the server. All decisions are also stored locally in the datafile (more on that later), while other server-side tools require external API calls to go back to their own system and see what was configured.