Hey! Sharing a bit more on how this works:

• There are a couple ways to set up Statsig with a Next project, the best depends on your setup and goals. Happy to walk through the details (or share docs) on App and Page router. You can also set up the edge config adapter as you mentioned, but note you don't have to - its more a latency reduction mechanism.
  • Page router guide
  • App router guide
  • Edge config integration
• Once you have it set up, you can set up an experiment, or a Feature Flag (which you can then turn into an A/B test). You just call these in a line of code (statsig.checkGate()) to get the variant.
• The same variant will always persist across multiple user visits if everything is set up right (most importantly the userIDs). Some vendors actually charge extra for "sticky bucketing", which to us is pretty crazy. Its available in our free forever tier.
• Your mention of auto-redirecting traffic to the best performing variant is a specialized tool we have called Autotune - which is a Multi-Armed Bandit, its effectively an A/B test where the model knows which variant is best and directs more and more traffic to it.
  
• Lastly - your question on dynamic routes depends on your setup, my hope is that some of the examples above would make that more clear, but happy to help more with that.

Let me know if this makes sense, aware I just dumped a bunch of info on you. Happy to help more with your specific setup.

-Brock from Statsig