Hey everyone 👋 we’re encountering an issue where an experiment remains active even when the targeting attribute value we send doesn’t match the one defined in the experiment’s conditions. In practice, the user keeps being assigned to the experiment even though the attribute value should exclude them. We verified this using the GrowthBook browser extension, and it looks like the IF condition based on that attribute is being ignored — the experiment is still triggered no matter what. We’ve already shared the SDK payload with the support team, and from their side the configuration looks correct, but the behavior persists. Has anyone else experienced something similar or found a reason why attribute-based targeting might not be applied as expected? We’re using the JS SDK client-side and setting attributes via growthbook.setAttributes(). Any insights or debugging tips would be really appreciated 🙏

We had same problem with sticky bucketing enabled.

@fierce-afternoon-26443 thank you man, it worked by disabling the sticky bucketing on the experiment level 🙏

I came here to report an issue with attribute targeting too. This is our first live experiment, so I'm new at this, but I think we have the same issue. We don't have sticky bucketing enabled