Skip to content

Commit c7d1fd1

Browse files
committed
sensitive example
1 parent c90870e commit c7d1fd1

File tree

2 files changed

+7
-3
lines changed

2 files changed

+7
-3
lines changed

docs/advanced/targeting.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,11 +58,15 @@ In this case the feature flag evaluation is based on the secure hashes of the co
5858
| IS ONE OF (Sensitive) | Checks if the *Attribute* is listed in the *Comparison value*. *Comparison value* should be a comma separated list. |
5959
| IS NOT ONE OF (Sensitive) | True if the *Attribute* is not listed in the *Comparison value*. |
6060

61-
Since sensitive text comparators don't support CONTAINS or DOES NOT CONTAIN comparisons, here is an example how to target users from the same company.
62-
Adding a `domain` custom attribute and using only sensitive comparators to target them.
61+
Since sensitive text comparators don't support CONTAINS or DOES NOT CONTAIN comparisons, here is an example how to target users from the same company. Which used to be handled by a rule like:
62+
63+
![Sensitive](assets/sensitive2.png)
64+
65+
66+
You can add a custom attribute called `domain` and use only sensitive comparators in the targeting rule.
6367

6468
On the Dashboard:
65-
![targeting-1](assets/sensitive1.png)
69+
![Sensitive](assets/sensitive1.png)
6670

6771
In your code:
6872
```js

docs/assets/sensitive2.png

8.78 KB
Loading

0 commit comments

Comments
 (0)