You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+30Lines changed: 30 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,33 @@
1
+
## 1.3.0
2
+
- Added the forced bucketing feature allows customers to force users into variations in real time for QA purposes without requiring datafile downloads from the network. The following APIs are introduced:
3
+
```
4
+
/**
5
+
* Force a user into a variation for a given experiment.
6
+
*
7
+
* @param $experimentKey string Key identifying the experiment.
8
+
* @param $userId string The user ID to be used for bucketing.
9
+
* @param $variationKey string The variation key specifies the variation which the user
10
+
* will be forced into. If null, then clear the existing experiment-to-variation mapping.
11
+
*
12
+
* @return boolean A boolean value that indicates if the set completed successfully.
13
+
*/
14
+
```
15
+
```
16
+
public function setForcedVariation($experimentKey, $userId, $variationKey);
17
+
18
+
/**
19
+
* Gets the forced variation for a given user and experiment.
20
+
*
21
+
* @param $experimentKey string Key identifying the experiment.
22
+
* @param $userId string The user ID to be used for bucketing.
23
+
*
24
+
* @return string|null The forced variation key.
25
+
*/
26
+
public function getForcedVariation($experimentKey, $userId);
27
+
```
28
+
29
+
- Added the bucketing ID feature allows decoupling bucketing from user identification so that a group of users that have the same bucketing ID are put into the same variation.
0 commit comments