What is this about?

• Right now, only the ID is used as a seed to determine what bucket the user falls into in an a/b test
• This means that, if there’s more than 1 a/b test configured - they will never be independent of each other
• To solve this, we need to:
  • Define the distribution using profile/metametrics ID + a/b test ID as a seed instead of just profile/metametrics ID

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response