Taplytics offers two ways to segment users into Experiments:
- Device Based Bucketing
- User Based Bucketing
Device Based Bucketing
Device based bucketing ensures consistent experiment and feature flag behaviour across pre and post logged in user states where userID’s are not required or necessary.
- Users are targeted based on their device
- For mobile devices, Taplytics sets a device id
- For web applications, Taplytics sets a device id associated with the browser cookie
- This requires a standard, out-of-box implementation
- Users always see the same experience on the same device
- Depending on how your users use and interact with your product, this implementation method does not guarantee consistent experience across multiple devices.
- For example, if the expected user behaviour is to access the platform on their mobile device as well as through their desktop, a consistent experience is not guaranteed because the bucketing and distribution is on a device level.
User Based Bucketing
User Based Bucketing ensures consistent experiment and feature flag behaviour across devices with pre and post logged in user states where users are identified with a userID.
- Users are targeted based on a unique userID
- Users always see the same experience across devices in a logged in state
- User Based bucketing is the best option for true cross-platform optimization and attribution
- Applications must pass a unique userID for each user to Taplytics to ensure a consistent user experience
- Slightly modified Taplytics implementation
- The main consideration affects anonymous users who never log in and use multiple devices. It is possible these users will receive different pre-logged in experiences. In this use case, an anonymous user will have two unique IDs on different devices until they log in at least once on both devices. The pre-logged in anonymous data will not be included in the logged in user model.