The Split Boxes demo is a tool to help users understand the interaction between rules and the impact of various features. It's a simple visualization that allows you to see the impact of whitelisting, custom attribution, traffic allocation, and dynamic configuration.
Using the Boxes Demo
Each box represents a user ID.
You can whitelist using the cell location, such as b8 or j5. You can also create a segment that includes any of the available values.
You can create targeting rules using the attributes row, col, or account; row and col will use letters and numbers respectively, usually with 'is in list' as the matcher. Valid account names include Nike, Apple, LinkedIn, Best Buy, Google, Microsoft, Pintrest, Dell, Slack, Zoom, Samsung and Disney.
You can modify the configuration of the treatments by updating any of the values. The font_size expects standard HTML sizes, such as medium, large, x-large, etc.
Setting up the Boxes Demo
There are three files attached. The HTML contains the SDK and can be run locally or on a server. You need to provide the browser API key for whichever Split Environment in which you will be updating the rollout plan. You also need to provide the name of the split. These are entered as vars in the HTML.
The Boxes_split.txt file contains an example baseline definition of the split.
The Split can be created automatically using CreateBoxSplit.sh script which uses Split Admin Rest API, and jq tool. Run the script with the following command line to create the split and add the definitions:
CreateBoxSplit [Workspace Name] [Environment Name] [
Traffic Type] [Split Name] [Admin API_KEY]
CreateBoxSplit Default Production user front_end_choose_boxes 9enxxxxxxxxxxxxxxxxxxxxxx
In Chrome, to see split changes immediately you should Disable cache for the Network in the browser's Developer Tools.