SDS2.3 UAT discovered some interesting findings and friction points in the GB configuration experience.
- Documentation should explicitly note that tracking key has to match code.
- Documentation should guide users how to check allotted traffic after configuring (e.g. check API response)
- Change RegEx guidance text in the checklist -- it is not understandable. /^[A-Za-z0-9][-_.A-Za-z0-9]{7,62}$/ Change to regular language: "Must start with a letter or number, containing only letters, numbers, hyphens, underscores, or periods. Must be 8-23 characters long." This needs to be updated in the UI and in the code which checks whether items are complete.
Open Questions:
- Do we control tool tips in the GB UI or do they?
- If yes, then: for traffic allotment %, explain that "100% reflects your full allotted traffic, not 100% of all site traffic."