Expand my Community achievements bar.

Applications for the 2024 Adobe Target Community Mentorship Program are open! Click to the right to learn more about participating as either an Aspirant, to professionally level up with a new Certification, or as a Mentor, to share your Adobe Target expertise and inspire through your leadership! Submit your application today.
SOLVED

User bucketing for native app

Avatar

Level 4

Can anyone here explain how bucketing works for A/B testing with native app (SDK)?

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@rrrrrraul 

If your question is regarding feature rollouts and Adobe Target's 'on-device decisioning' capabilites, see below on user bucketing: 

The decision making process is deterministic — murmurhash3 is used to work out which bucket the user should belong to. The 3 main IDs that are used in the context of Target — ECID, mbox3rdpartyid, Target ID — are used for bucketing, so as long as the same ID exists the Target experiences a user sees will be consistent.

More details can be found here:
https://adobetarget-sdks.gitbook.io/docs/on-device-decisioning/introduction-to-on-device-decisioning

https://experienceleaguecommunities.adobe.com/t5/adobe-target-blogs/adobe-target-on-device-decisioni...



View solution in original post

3 Replies

Avatar

Employee

Hi @rrrrrraul , can you elaborate on what you mean by user bucketing? Do you mean assigning users to discrete groups or swim lanes for different experiences in a test?

Avatar

Correct answer by
Employee Advisor

@rrrrrraul 

If your question is regarding feature rollouts and Adobe Target's 'on-device decisioning' capabilites, see below on user bucketing: 

The decision making process is deterministic — murmurhash3 is used to work out which bucket the user should belong to. The 3 main IDs that are used in the context of Target — ECID, mbox3rdpartyid, Target ID — are used for bucketing, so as long as the same ID exists the Target experiences a user sees will be consistent.

More details can be found here:
https://adobetarget-sdks.gitbook.io/docs/on-device-decisioning/introduction-to-on-device-decisioning

https://experienceleaguecommunities.adobe.com/t5/adobe-target-blogs/adobe-target-on-device-decisioni...



Avatar

Level 4

so for client side the Adobe CDN maps an experience delivered to VisitorID and TntID (taken from AMVC_*** cookie and mbox cookie).  I'm wondering what the mapping mechanism in app is.  In other word, how does Target for app know when a user previously entered into an A, B, C, etc.