This message was deleted.

Based on user attributes passed to your GrowthBook SDK, if the attributes are the same, the FF values should evaluate to the same

I tried hardcoding the user attributes in both initializations the react and js ones, I got different FF values

That's strange. To be clear, you're using

setAttribute

method to accomplish this in either context? And what are the targeting rules of the experiment?

Yes this was using setAttribute, the targeting rules were the country code and I also hardcoded it, I found a way to avoid this from happening, I used the javascript SDK also in the client side instead of the react one and the feature flag was consistent in both sides after I implemented this change