Hello, I am wondering is there a way to check if feature is on for user without enrolling him into the experiment. I thought

useFeatureIsOn

does that but from what I can see it just calls evalFeature under the hood which per docs calls tracking. Our use case is that we have specific conditions on when user needs to be enrolled in the experiment so we can't enroll him just to check if feature is on. For example we have 3 CTAs which change based on the experiment. All of those need to check if feature is on but only one of them should actually trigger enrollment.

Hey, Ante - what sort of conditions will need to be checked. When building an experiment rule, you can add targeting conditions so you can limit who is included in an experiment. E.G. You can pass in attributes for country, and you can add targeting conditions to so only users in certain countries are included in the experiment. From there, you can have the 3 CTA variations in the experiment.

It's not a matter of variations. It's just a matter checking if feature is enabled without enabling it. Code example (it might be easier to grasp)

const isFeatureEnabled = useIsFeatureEnabled('feature')

{isFeatureEnabled && <ButtonA />}
{isFeatureEnabled && <ButtonB />}
<ButtonC onClick={() => {
    growthbook.feature('feature')
} />

In the above feature will be enabled as soon as

useIsFeatureEnabled

is called. We want it to get enabled only on

ButtonC

click.

So, if I'm understanding correctly, you only want someone to enter the experiment when they click

<ButtonC />

. But, for the conditional rendering, you need to know if they're in the experiment to know whether to show the buttons. Is that correct?