This message was deleted.

⭐ Our official support hours are 6:30am - 5pm Pacific Time, Monday through Friday. You may occasionally hear from us outside of these hours. Your support request has been logged in our system. Our support team will get back to you very soon!

Hi @witty-finland-62471 It's harder to share your experiments/feature flag definitions across a team when not using the UI. To evaluate features, you'll probably want to use

evalFeature

? We also supply a method to evaluate conditions called

evalCondition

if you want to figure out if a user is targeted given their attributes

thanks @swift-helmet-3648 any clarification on: "when an experiment is defined as per above, does this mean you don't need to setup a feature flag or experiment in the GrowthBook UI?"

Inline experiments are ones that are configured entirely in code. You specify the targeting rules, traffic split, etc. all entirely in code and not in the GrowthBook UI. If you want to make a change to an inline experiment, you need to change and deploy your code. They can't be controlled from within the UI.