Adobe Target

Hello @jsvasu, good to hear from you. As far as where to start doing personalization, much like the considerations when you are trying to determine where to start with optimization/testing considerations of where you have significant opportunity for impact, based on both traffic and high leverage points in the user experience, are usually the places to start. So entry pages, product comparison or review portions of the site, and similar area's are usually the most common and impactful places to begin.

Awesome @kjemison this is helpful info. In addition to that, I also want to check What milestones can we achieve with Target & how we can mature it with time?

Maturity is really a process of moving the considerations of optimization & personalization higher up in strategic priority for the organization. Often you'll start out with just a test here and there, and mature to testing most of the time and taking some of those results forward and doing personalization. Eventually you want to get to the point that initative the organization does has some testing component and that the overall user experience has multiple personalized aspects to it.

Of course its a process that you have to incrementally work towards piece by piece.

Hi @Diego5, good question! I would say that is not the intended behavior if the person is qualified. As long as somebody qualifies for the audience, they should see the content initially. 

Is it for all visitors or a specific audience segment?

if it is an audience segment are they loggedin/cookie based?

sometimes we see cookie based user states require a refresh

Hello @neerspinner , It really depends on the audience definition and how the site/experience is set up. To answer broadly, as long as the information to qualify the visitor as being in the audience is available at the time of the request, they should qualify and receive the experience.

For your specific example, if that audience is login/cookie based then it would depend on if they were cookie'd at the time of the initial request or if the cookie was only applied after the initial request during the page-load cycle or some time thereafter.

Users should be in Ireland/UK and there's also user from the rest of Europe that would see a different personalised page.

Great question @neerspinner! My understanding is you're looking to better learn how to go up the maturity curve for your organization. Generally, the goal behind this is to develop a personalization strategy when launching activities. You start with basic testing of optimization working by itself, but to get broader buy in, then the framework / thought process should be more focused on the personalized aspects in activities.

Getting the personalization higher up in the strategic process means it becomes the normal way orgs would approach rolling out everything. When designing business goals to have a component of personalized experience in them, that matures the strategic mindset so that companies are able to reach the "test anything/test everything" approach.

Thanks for this Question @renatoz28! Based on your description, you would want to have both of those experiences in one single XT activity, but have the two different audiences applied with the more restrictive analytics audience being the first experience. That should result in only one or the other of the banners being shown.

To add onto Kevin's comment, here's a link to Adobe documentation that goes into more detail on the priority of XT activity's experiences and how to control what audiences see: https://experienceleague.adobe.com/docs/target/using/activities/experience-targeting/create-targetin... 

Thanks for asking @RcBT ! This could be due to a variety of potential causes, so some additional information would be needed. For example, is this behavior limited to a certain kind of activity, such as an Automated Personalization (AP) activity? Or is it also impacting other types like A/B, XT, etc.?

Another helpful detail would be to know what the issue accessing preview links exactly is. When loading the QA link, is the problem that the expected content would not load? Or are you unable to generate the preview links themselves in the Target UI?

hey @magnusflaaten2, I think you are generally correct, this type of use case is more directly in the area of something like Journey Optimizer to manage both the timing and the activation across the channels, but there are a couple of approaches for defining the audience either with Target or Target+Analytics. 

If you only have access to Target you are correct in that something like a recency trait is probably your best option. If you have Analytics as well you could define a sequential segment in analytics that takes your time lag into account or requires multiple sequential events to qualify in the the audience. Depending on your product mix it will be more or less convenient to fulfil that specific use case.