bitter-exabyte-77986
04/17/2024, 12:14 PMfeature-name
. Then use this value on backend to control execution flow based on that value.
If not, is there an alternative approach for my use case?future-teacher-7046
bitter-exabyte-77986
04/17/2024, 2:19 PMuserId
sufficient? And is this using Growthbook.setAttributes
?
Not all the fields are available on backendfuture-teacher-7046
browser = "chrome"
, you need to make sure that browser
attribute is available on the back-end. Otherwise, you could get a different feature value in the front-end and back-end.
So there's definitely risk going with this approach since if you forget to set a specific attribute or there's some other mismatch going on, you could get into a conflicted state. Explicitly passing feature flag values in the API requests is safer, but requires more work during implementation.