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.
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?
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.
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.
