This message was deleted.
# ask-questions
w
This message was deleted.
s
It sounds like you're on the right track. Can you say more about what kind of rollout you're doing (so I can have all the details)? Sticky bucketing may also be useful to you.
e
We basically want a cross-frontend "Percentage Rollout" https://docs.growthbook.io/features/rules#percentage-rollout We want a defined subset of users (which have certain pre-conditions met, e.g. at least one sale in the last 3 months). This additional attribution could be set as another attribute (together with
id
and
deviceId
). Then we want to rollout the new feature to 10% of that eligible user set.
It should be noted that the
deviceId
would be stable across those frontends as they all run under the main domain. Only the
id
can differ: empty ("") for anonymous users, the user's account id for logged-in ones.
s
Gotcha. Sounds like you're on the right track, where you'd set the percentage rollout based on the more stable user ID and then set up targeting on the rollout rule (like "one sale in last 3 months").
e
Great! I did a small test this morning and it worked as expected 🙂