Issue with Adobe Target Activity Prioritization Affecting Audience Capture

[priyankagupta20]

Dear All, 
Please guide.

We are currently running a few A/B tests and personalization activities using Adobe Target.
For some of these, We faced challenges in retrieving real-time data from the page, such as selected products in a shopping cart, to use for audience targeting.
Due to suboptimal Adobe Target setup, they implemented a two-activity approach:

- Activity #1: Captures the selected product ID and sets a flag on the website as an XT (experience targeting) activity. This activity displays custom HTML to all users but only sets the flag for relevant users.
- Activity #2: This is the main A/B test, targeting users who were flagged in Activity #1.

The issue we’re seeing is that not all relevant users are being captured, and the cause is unclear.

In the current setup, Activity #2 has a priority of 999 and is configured to target users with the flag from Activity #1 set to "true."

I suspect the low user count in Activity #2 could be due to either activity collisions or incorrect priority settings. Currently, Activity #2 has a higher priority than Activity #1, which may cause Adobe Target to evaluate Activity #2 first (before Activity #1 can set the flag). This would mean that when Activity #2 is evaluated, the flag from Activity #1 hasn’t been set yet.

[kandersen · Accepted solution]

Hi @priyankagupta20 

I'm assuming that both activities are running on the same page and that both are created using the VEC?

Target returns the content for all activities on the page, beginning with the lowest-priority content, which is then overwritten by each activity, from lowest to highest priority. Usually, this results in the highest-priority content being displayed.

So having activity #2 set to the highest priority should be fine and also be correct, based on that it is depending on a flag from activity #1.

I'm not sure what could cause that activity #2 would have a low number of entries/visitors. My best guess would be that it could be a timing issue. Meaning that activity#2 is executed before flag has been fully set, resulting in low visitors in activity #2.

Could it be an option to test it out by including getOffer and applyOffer in your activity #1 AFTER the flag has been set?