Hi All,
I copied one of my audience which was created by build rule method and the lifecycle status of the cloned audience shows up as Draft. How can i change the lifecycle status from Draft to Published?
Thanks,
Swastika
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hello @swastika_lal,
To update the state , call the following API call:
GET https://platform.adobe.io/data/core/ups/segment/definitions/:SEGMENT_ID
This request will return information about the segment in question. Please copy the entire response.
Next, Update the segment's status, make the following API request:
PATCH https://platform.adobe.io/data/core/ups/segment/definitions/:SEGMENT_ID
In the body of this request, paste the previously copied response, but modify the `"lifecycleState"` from `"draft"` to `"published"`.
For additional details, please refer to the documentation here:
[https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/api/segment-definitions#...)
Best regards,
Arpan
Hello @swastika_lal,
To update the state , call the following API call:
GET https://platform.adobe.io/data/core/ups/segment/definitions/:SEGMENT_ID
This request will return information about the segment in question. Please copy the entire response.
Next, Update the segment's status, make the following API request:
PATCH https://platform.adobe.io/data/core/ups/segment/definitions/:SEGMENT_ID
In the body of this request, paste the previously copied response, but modify the `"lifecycleState"` from `"draft"` to `"published"`.
For additional details, please refer to the documentation here:
[https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/api/segment-definitions#...)
Best regards,
Arpan
Thanks @arpan-garg ! I tried this out and it works as expected.
Is there a way to do this via the front-end UI?
Other users may not have access to the API or feel comfortable to use it so doing it on the UI will be preferred.
I hope that it will be released soon with UI as well. With an API-first approach, we can at least deal with the situation quickly.
We ran into the same situation and this post helped. Thanks @arpan-garg !
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies