A user can be forced into a variation for a given experiment for the lifetime of the Optimizely client. This method gets the variation that the user has been forced into. The forced variation value is runtime only and does not persist across application launches.
SDK v3.0 and higher
Forced bucketing variations take precedence over whitelisted variations, variations saved in a User Profile Service (if one exists), and the normal bucketed variation. Variations are overwritten when Set Forced Variation is invoked.
A forced variation only persists for the lifetime of an Optimizely client.
Required and optional parameters for Android are listed below.
The key of the experiment to retrieve the forced variation.
The ID of the user in the forced variation.
The variation the user was bucketed into, or
setForcedVariation failed to force the user into the variation.
import com.optimizely.ab.config.Variation; Variation variation = optimizelyClient.getForcedVariation(“my_experiment_key”, “user_123”);
The language/platform source files containing the implementation for Android is OptimizelyClient.java.
Updated 4 months ago