Question: Ensuring persistent feature assignment
meirroth opened this issue · comments
One aspect isn't entirely clear to me after reading the docs: How does Featurevisor ensure consistency in assigning the same feature variant to a user across different devices or sessions? For example, if a user is assigned Variant A on desktop, will they also receive Variant A when accessing the app from their mobile?
Do I need to handle storing the assignment on my end, or is this managed within Featurevisor?
Just for context, I'm currently looking into implementing Featurevisor into our Nuxt project.
Any insights or explanations would be awesome!
Thanks
Sorry, I missed this explanation! https://featurevisor.com/docs/bucketing/#consistent-bucketing
@meirroth: glad you found out more about bucketing :)
you can find Nuxt example here if it helps: https://github.com/featurevisor/featurevisor-example-nuxt
In case people come to this page from search engines, consistent bucketing is achieved by a combination of:
- Hashing at SDK level: https://featurevisor.com/docs/bucketing/#consistent-bucketing (like you already discovered)
- State files at build levels: https://featurevisor.com/docs/state-files/ (which maintains old bucketing info, and keeps adding new cohorts as
percentagegrows gradually over time) - Deployments taking care of pushing state files back to repo for future builds to honour: https://featurevisor.com/docs/deployment/