📄️ How it works: Running A/B test on the server
ABRouter SDKs are working pretty easily. They making the HTTP requests to the ABRouter remote server. You need to send the user identifier and branch uid to run the experiment. The response will contain what branch the user got.
📄️ User identifiers
In the world of ABRouter statistics exists multiple user identifiers. The temporary user id and user id.
📄️ Branch memorization
After the experiment runs the user will get into the branch. Each further running will return the same branch. Syncing with glued temporary user-id is currently not implemented, but you can help us do it.
📄️ API Resources
The page should be completed
📄️ Separating env's
Currently, we don't have the ability to separate the env's in a single account. You can easily separate it by the different accounts for dev/RC/prod env's.