Hello everyone,
In Adobe Target, the Priority (0-999) setting determines which activity gets executed first. From my understanding, a higher number means higher priority, so the activity with the highest number is displayed first.
Thank you for your support.
Thanks,
Vishnupriya R
Hi Vishnupriya,
It is true in Adobe Target that the Priority (0-999) setting determines which activity is executed first, with a higher number indicating higher priority. However, Adobe Target does not always execute activities strictly by priority alone.
Here’s how it works:
1) Audience Qualification v/s Priority
Adobe Target first checks which activities a user qualifies for based on audience rules. Then, priority is considered among the activities the user qualifies for, the one with the highest priority number is executed first.
2) Can a lower priority activity be executed first?
No, Adobe Target does not have a built-in option to execute a lower-priority activity first.
3) What happens if different audiences are assigned to different activities?
Adobe Target will first check the audience conditions. Among the activities a user qualifies for, the highest-priority activity will be shown to the user.
Views
Replies
Total Likes
No, Adobe Target does not have an option where a lower-priority activity gets executed before a higher-priority one .
2.If I have different audiences assigned to different activities and set priorities for them, will Adobe Target execute the activities based on priority or based on audience qualification?
Audience qualification comes first , adobe target will first check audience qualification and among the qualified activities it will check for the priority numbers to execute first .
Let me know if you find these answers useful!
Also follow below documentation https://experienceleague.adobe.com/en/docs/target/using/activities/priority
Views
Replies
Total Likes
We've used Priority for our personalisation's in Target normally setting 999 to give it the highest priority. When you have a situation in which the priority levels are not ideal for your circumstances, I tend to use JS to run a PromiseAll on the activity I want to run later by not executing it until the first activity has run which drops a unique element in the DOM that the second activity needs to see before it's executed. Seems to run quite well. Or you can use a timeout, but that's not always reliable as sometimes the page loads quicker so you see a flicker, or it runs slowly and then the JS fails. Mutuation Observer with PriomiseAll is the best solution I've found.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies