I'll start by getting off topic for a bit: Are you using Adobe Analytics or Customer Journey Analytics in addition to Target?Related to the actual question:Once the visitor is included in the Activity, Target collects data and matches them to URLs outside of the delivery URLs as well, this applies t...

A lot of the issues with segments boils down to scope. As an example, your goal is to segment visitors (or browsers) that viewed a product of a certain category, then added a product of that category to their card and finally, purchased product of said category. The issue comes when segmenting event...

There is a specific process to set that up. I haven't done it myself, but instructions for it can be found here: Experimentation panel | Adobe Customer Journey Analytics

It may seem counter intuitive, but this is how the Github page actually also shows it in the responses, which I found odd. After looking at this for a bit, this is my hypothesis: When you set "segmentable" filter on, it will only return items that match that. When it filter is left as default or set...

If the SDK's do not share the method/location of storing visitor ID, it is likely that without any custom actions it would cause all visitors to show up as new when switching. I'm not familiar in how you can read or store this value in mobile, but one alternative would be to store the mcvisid in the...