Webtrends Optimize

As described in the <a href="https://intercom.help/webtrends-optimize/en/articles/10366923-feature-flags-overview" rel="nofollow noopener noreferrer" target="_blank">Feature Flags Overview</a>, in Webtrends Optimize we view Feature Flags more as a use-case than a feature.

Building a new feature flag is therefore very similar to building any experiment, just with a few small differences.

Pick your experiment type - ABn, Target or MVT. Functionally, these should work as you expect, and so the reason to select any one of these should be a familiar decision. Tests are sticky and have % based splits, targets aren't sticky and have rules-based splits.

Create your project and test Include the usual decisions around names, throttling and segmentation.

Create a virtual location We recommend using Virtual/Fake locations instead of real URLs for your feature flags. This will help you separate "web" tests from "feature" tests, and ensure that you don't accidently fetch and count users from web tests when accessing your flags. Example - if you wish to access all flags at once. A single path is fine. flags.com/ Example - if you wish to access flags on a per-page basis. You can then rewrite the current URL when hitting the OTS API. flags.com/page-path

Note: If using the global option, you should make 1 Location and reuse it in every flags project. Once created, simply select this Location when building your experiment.

In the "code" section for your variations, supply the values that you wish to receieve through the API call. Don't worry about terminology of JS or CSS containers, use the JS option regardless of what type of value you wish to send back. The UI will allow any values to be saved and retrieved through the API.

1. Pick your experiment type - ABn, Target or MVT. Functionally, these should work as you expect, and so the reason to select any one of these should be a familiar decision. Tests are sticky and have % based splits, targets aren't sticky and have rules-based splits. 
2. Create your project and test Include the usual decisions around names, throttling and segmentation. 
3. Create a virtual location We recommend using Virtual/Fake locations instead of real URLs for your feature flags. This will help you separate "web" tests from "feature" tests, and ensure that you don't accidently fetch and count users from web tests when accessing your flags. Example - if you wish to access all flags at once. A single path is fine. flags.com/ Example - if you wish to access flags on a per-page basis. You can then rewrite the current URL when hitting the OTS API. flags.com/page-path 
 
 Note: If using the global option, you should make 1 Location and reuse it in every flags project. Once created, simply select this Location when building your experiment. 
 
 
4. In the "code" section for your variations, supply the values that you wish to receieve through the API call. Don't worry about terminology of JS or CSS containers, use the JS option regardless of what type of value you wish to send back. The UI will allow any values to be saved and retrieved through the API.