Chapter 4. Best Practice #2: Bridge the “Anonymous” to “Logged-In” Transition
When the same user crosses from an “anonymous” to a “logged-in” user, deciding whether to maintain a consistent feature treatment can be a challenge. The need to maintain the same feature set as a user switches from anonymous to logged in is encountered more often in organizations that serve consumers (B2C) than in enterprise organizations. In B2C software, consumers generally start as visitor or anonymous, perform some actions like adding elements to a shopping cart, and then later log in to complete the purchase. There are several strategy options, and you will need to choose what is right for your user’s experience.
Our sample company, acmeshopping.com, will have this problem as well. An acmeshopping.com customer generally enters the site as an anonymous user and is assigned a visitor ID as a cookie. The user might later complete a login sequence.
When dealing with an anonymous user, you first need to decide whether it’s important to maintain feature-flag consistency during the transition from visitor ID to user ID.
For example, if your application is more transactional in nature, such as a collaboration or networking site, perhaps maintaining feature-flag consistency from session to session will not be as important. However, if your test involves different pricing options, maintaining consistency will be important because you’ll want to show the same price at every session.
If you decide that maintaining ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access