The 'scope' of a Segment is no longer relevant as the introduction of a new scope of Customer is no longer planned. Instead all Segments will be treated as Session scoped (though the value is highly redundant). Either way, the scope field is no longer needed as a default value of Session will be used in the backend service.
Change Category
API
Change Context
We previously planned to scope Journey Segments based on whether they were assigned during a user's web or app session, or assigned via an API directly to the user. This differentiation is no longer planned. Scope is being removed from everywhere possible, and where not possible to remove it, the field will be defaulted to a value of Session and be considered a redundant value.
Change Impact
There should be no impact as our logs indicate no customer usage of this value. There is technically no change from how Segmentation functions today.
Woah, lets take a step back. This will have impact. A session and segment are not redundant in nature but are related as sessions can contain segments; in fact they provided much needed and desired informational hierarchy to conversational data. To say it is redundant would be drastically oversimplifying the complexity of a conversation.
I will illustrate with a photo (all rights reserve by Genesys the vendor and so on. . . ) from an interaction timeline view:
The horizontal swim lane (red outline) represent the distinct Sessions, the individual horizontal bars encircled in purple are the segment
They definitely are not functionally redundant and elimination thereof would be a reduction of transparency of the segmental components that make up a conversation.
I beg you, please reconsider deprecation this will break the underlying understanding and explanability of the moving dynamic construct of a conversation .
What you're talking about seems to be Conversation Segments. The post is referring to Journey Segments, which are unrelated
What's more, the post is not talking about removing Journey Segments. It's talking about removing a field from Journey Segments. The Scope field being removed from Journey Segment only has 1 possible value available to customers right now; a second value was planned but we are no longer proceeding with that. Since all Segments have the same scope currently, and always will, the field is redundant. So, we're removing it. That removal will have no functional impact.
Thank you Matthew, that makes a whole a lot more sense, sorry for the miscontextualization, I read the email to quickly I supposed. Thanks for the clarification, then I withdraw my object as we have not ventured deep within the journey data just yet in our cloud transition but I hope we get there in the near future because it's loaded with value.
