Segment your customers and directly target these segments in your deployment process
To understand the idea of custom target groups, you need to think of your user base and how you would like to deploy or open features differently to different user groups.
Customized Target Groups
With Rollout, you can leverage your user base data and use it to segment users into what are known as target groups. You can create groups around the aforementioned properties: location, device type, and language. You can also capture additional properties, like screen size, OS type, and version number.
But you can go well beyond that, too. You can actually create dynamic target groups using custom attributes evaluated on the fly. For example, you can create groups like “paying account” or “company employee” depending on data within your application.
Custom Targeting Rules
Okay, great. You can segment your user base by various parameters, but what do you do with this ability? Simple. You create custom targeting rules and use your feature flag management capabilities to deploy features to specific groups of users.
Create a group likely to be early adopters and roll new feature out to them first. Or turn a new feature on, but only for internal employees or a specific type of customer.
There’s no doubt that your development and production team will benefit from having a feature flag system. You have two options: build or buy. You have to decide what option is best for you depending on your resources, organizational structure, and development process.
