The segments tab allows you to create lists of users that can be shared by one or more split in an environment. Segment your customer base to directly target these segments in your release process and re-use these segments across your splits.
A segment is a pre-defined group of customers that a feature can be targeted to. These segments can be created from a CSV upload, via the API, or simply by adding IDs to the segment.
Segments are best for targeting relatively fixed or specific groups of users you can easily identify, like a whitelist of accounts. For more dynamic targeting, see our article on Custom Attributes.
As you think about feature releases it’s good to take a step back and acknowledge all of the things that segmentation helps you do better. Your segments should be used to:
- Ensure quality testing. (Example: you may want to release to your internal or outsourced QA team - create segment
- Target employees for internal testing. (Example: you may want to release to your entire company to test the feature or gather feedback - create segment
- Plan your release strategy. (Example: you may want to release to a group of customers who have expressed interest in a particular feature - create segment
These are just a few examples that engineering and product development teams should think about. There are a lot more ways that you can apply segmentation to drive better results and ensure a successful and safe release.
Split makes segment creation easy. First, navigate to your segments and click "Create Segment". This will prompt you to create a new segment.
While creating your segment, you can easily specify information for your new segment, including name, description, owners, and tags. This information can help you and your team manage your segment and customize to your team's workflow.
A. Name your segment
Give your segment a name your team will recognize.
B. Specify the traffic type
Select the traffic type you would like to use this segment for.
C. Add owners
Add one or more owners to your segment. Use owners to isolate segments in the browse panes to those "owned by me" and simplify permissions by providing owners edit rights for a single segment across all environments by toggling permissions ‘on’. When toggled ‘on’, permissions will inherit owners as editors.
D. Add tags
Add one or more tags to help you categorize the segment. Tags can be used to isolate to a particular team or feature release — just create tags like "reporting team", "front end", or "geo search release".
E. Describe your segment
Provide a description of the segment. This will help your team members understand the segment's purpose.
After clicking Create you will land in your new segment.
Segment Name Requirements
Segment names must start with a letter and can contain - _ a-z A-Z 0-9. Also note that segment names cannot be "datetime", "string", or "integer".
To begin using the segment in a given environment, you must configure by clicking "Add To Environment". Once you click add to environment you will be able to create and define customers within this segment.
Once configured you can begin adding customers to the segment.
Number of Customers in a Segment should not exceed 10,000
When you add customers to a segment, remember that these are lists that then need to be fully downloaded down to all of our Backend SDKs. This will make it so that your SDKs take longer to get ready. Do not add more than 10,000 members to any one segment to avoid this.
The segments you create can be used in your split targeting rules to target a particular set of customers or a percentage of a particular set of customers.